// Model
How TrigGuard pricing works
Infra buyers scope pricing from control architecture, not a generic seat ladder. Commercial shape is typically set by four dimensions:
Execution surfaces
Which actions require authorization before side effects (APIs, tools, payments, OT, agents).
Deployment model
Inline gateway, sidecar, policy engine integration, dedicated or sovereign clusters.
Assurance level
Verification and receipt depth, audit retention, support tier, compliance and SLA needs.
Verification scope
Receipt retention, verification API usage, reporting windows, and evidence expectations by environment.
// Primary tiers
Deployment maturity ladder
Developer / Starter
Best for: evaluation teams and internal automation pilots.
- Pre-execution authorization gateway
- SDK and local integration path
- Basic execution receipts
- Single-project governance baseline
Recommended for live systems
Production
Best for: live execution paths requiring deterministic enforcement.
- Deterministic authorization engine
- Fail-closed execution control
- Policy enforcement across multiple surfaces
- Cryptographic decision receipts
- CI/CD and runtime integration support
Enterprise
Best for: regulated, sovereign, and multi-region operating footprints.
- Multi-environment policy deployment
- Advanced receipt verification
- Dedicated support path
- Audit and compliance integrations
- Custom SLA options
// Critical infrastructure
Critical infrastructure deployments
Not a fourth standard card. This is a separate procurement motion for energy, transport, defence, regulated OT, and air-gapped operational environments.
Sovereign and air-gapped patterns
Isolated execution control and deployment topologies matched to site constraints.
Higher-assurance operational support
Mission assurance, incident playbooks, and engineering depth for regulated runtimes.
Regulatory mapping and integration
Alignment to supervisory and safety narratives, with dedicated solutions engineering.
Procurement path
- Joint architecture and assurance scoping
- Control boundary and deployment model mapping
- Commercial proposal with engineering engagement plan
// Matrix
Capability comparison
Grouped by governance, verification, deployment, and support/compliance. Crit. infra = critical infrastructure procurement path.
| Capability | Dev / Starter | Production | Enterprise | Crit. infra |
|---|---|---|---|---|
| Governance controls | ||||
| Pre-execution authorization | Yes | Yes | Yes | Yes |
| Deterministic authorization | - | Yes | Yes | Yes |
| Fail-closed control | - | Yes | Yes | Yes |
| Policy enforcement engine | Yes | Yes | Yes | Yes |
| Verification and evidence | ||||
| Cryptographic receipts | Yes | Yes | Yes | Yes |
| Verification API | Yes | Yes | Yes | Yes |
| Deployment scope | ||||
| Multiple execution surfaces | - | Yes | Yes | Yes |
| CI/CD enforcement | - | Yes | Yes | Yes |
| Runtime integrations | Limited | Yes | Yes | Yes |
| Sovereign deployment | - | - | Yes | Yes |
| Air-gapped patterns | - | - | Optional | Yes |
| Support and compliance | ||||
| Compliance support | - | Yes | Yes | Yes |
| Dedicated support | - | Yes | Yes | Yes |
| Custom SLAs | - | Optional | Yes | Yes |
// Deployment
Deployment modes
TrigGuard can attach at different control points depending on architecture and assurance requirements. Canonical detail: Architecture and Runtime.
Inline Execution Gateway
Authorization evaluated on the application hot path before irreversible work.
Sidecar Enforcement Service
Co-located enforcement with fail-closed defaults at the edge.
Policy Engine Integration
Bind PERMIT / DENY / SILENCE to policy-as-code and governance workflows.
Cryptographic Receipt Log
Tamper-evident decision records verified through Verify.
// Placement
Where TrigGuard sits in the execution path
TrigGuard remains the deterministic control boundary between intent and side effect.
AI system or agent
|
TrigGuard authorization layer
|
PERMIT | DENY | SILENCE
|
Execution surface (API, tool, payment, OT)
|
Verification receipt (audit trail)
Intent in: execution request plus policy context.
Decision out: PERMIT, DENY, or SILENCE before irreversible actions.
Evidence: signed receipts for verification and audit operations.
// FAQ
Pricing and deployment FAQ
What counts as an execution surface?
Any protected path where an AI or automation could cause side effects: APIs, tools, payments, data export, infrastructure control, or OT. Each surface can be governed with explicit PERMIT / DENY / SILENCE.
How is TrigGuard priced for production systems?
By authorization volume, enforcement footprint (gateways and clusters), verification and receipt retention, and support tier. Production and enterprise deals align to runtime scope, not seat count alone.
Can TrigGuard run in sovereign or air-gapped environments?
Yes. Enterprise and critical-infrastructure programs support customer-controlled networks, isolated clusters, and air-gapped patterns; scoping is done with engineering.
What is included in enterprise support?
Production-oriented response targets, escalation into engineering, and help with policy rollout, verification, and audit integrations as defined in the order.
How do receipts and verification affect deployment tiers?
Higher tiers add retention, verification API usage, hardware-backed signing options, and audit integrations. All tiers use cryptographic receipts; depth scales with tier.
Can TrigGuard integrate with existing policy engines and CI/CD systems?
Yes. Policy engine integration is a first-class deployment mode; CI/CD and release gates can call the same execution API. See Runtime, Policy enforcement engine, and Examples.
// Procurement
Talk to engineering
Product and engineering join procurement conversations, not a generic handoff queue.
Pick the entry point that matches deployment maturity, assurance posture, and environment constraints.
- First call maps execution surfaces, deployment model, and verification depth against your constraints.
- You leave with a written scope note or a clear path to a formal quote.
Same routes as the rest of this page: demo for evaluation, quote for production and regulated programs.
Quote requests are triaged to solutions engineering; demos stay on the evaluation track.