Downloadable assets (stubs)
View all assetsWhitepaper (coming soon)
Runtime authorization for agentic AI. Outlines PERMIT / DENY / SILENCE semantics and enterprise buyer considerations.
EU AI Act readiness checklist (coming soon)
Maps TrigGuard controls to EU AI Act Article requirements for execution surfaces.
Runtime governance guide
Operational reference for deployment modes, authorization boundaries, and fail-closed execution controls.
Verification architecture overview
How receipt signatures, retention paths, and verification APIs support audit workflows.
Banking / GenAI FAQ
Key guidance on model risk management, execution controls, and generative AI in financial services.
Policies & trust
FAQ (common questions)
View all FAQsWhat counts as an execution surface?
Any path where automation can trigger side effects: APIs, tools, payments, data export, infrastructure operations, and OT actions.
How is production pricing typically shaped?
By authorization volume, deployment model, verification profile, and assurance depth rather than seat-count logic.
Can TrigGuard run in sovereign or air-gapped environments?
Yes. Enterprise and critical infrastructure programs support isolated clusters and customer-controlled environments.
How do receipts affect tier selection?
Higher tiers increase retention profiles, verification depth, and audit integration options while preserving deterministic decision semantics.
Where can I see system status and operational updates?
Visit /status for operational updates and current runtime health.
Talk to engineering
Product and engineering can map execution surfaces, deployment model, and verification depth against your constraints.