SAILLENTBook a DemoControl what your AI agents are allowed to do — before those actions reach your systems. SAILLENT intercepts, inspects, and enforces policy on covered AI actions before execution. Pricing scales with the enforcement capacity, protected deployments, and governance controls your organization requires.
No per-seat pricing. No surprise overages. No pricing based on how many people log in.
AGENT ACTION POLICY DECISION
coding-agent-prod
│
├── deployment.promote_release
│
├── target: production
│
▼
┌────────────────────────────────────────────┐
│ SAILLENT RUNTIME ENFORCEMENT │
│ │
│ POLICY coding-agent-production-v5 │
│ DECISION DENY │
│ REASON Production deployment prohibited │
└────────────────────────────────────────────┘
│
✕
│
DOWNSTREAM API NOT CALLEDDeploy SAILLENT around the agents, tools, and systems that matter most. Expand your enforcement boundary as autonomous AI moves deeper into the business.
Establish your first runtime enforcement boundary. For teams putting production AI agents under explicit control for the first time.
1M protected actions / month · Up to 10 nodes
Extend execution control across your growing agent estate. For organizations scaling autonomous agents, MCP, and tool-connected workflows across teams.
10M protected actions / month · Up to 50 nodes
Make AI enforcement an organizational control. For enterprises that need centralized policy, audit evidence, and governance across a growing AI estate.
50M protected actions / month · Up to 250 nodes
Custom enforcement for security, residency, procurement, and scale. For organizations deploying autonomous AI in regulated, high-security, or complex environments.
Tailored annual agreement · $150,000+/yr
Your SAILLENT plan is based on the enforcement boundary you need, not the number of employees using the platform.
The volume of AI actions SAILLENT evaluates each month. From initial agent deployments to organization-wide autonomous workloads.
The number of SAILLENT deployment points enforcing policy. A node is an enforcement deployment — not a user, seat, model, or individual agent.
The agent interfaces, MCP environments, APIs, and downstream systems that need to be covered.
The level of policy management, audit evidence, identity controls, compliance support, deployment architecture, and security requirements your organization needs.
Standard self-hosted deployment, customer VPC, on-premises, or more restrictive environments can be scoped according to enterprise requirements.
Standard support through dedicated engineering and strategic engagement for larger deployments.
Your quote reflects the systems you protect and the controls you require.
Every plan includes defined protected-action and node capacity. Expansion is deliberate and approved — not an unexpected usage bill.
Security coverage doesn't become more expensive because more engineers, security analysts, or administrators need access.
Your commercial agreement defines the enforcement capacity available to your deployment.
Enforcement decisions are recorded so security teams can investigate what was allowed, what was denied, and why.
Start with the highest-value enforcement boundary. Add capacity, nodes, integrations, and governance controls as autonomous AI expands.
Prove the control before you scale it. Your security team should not have to buy a promise. We can scope a Proof of Value around your real agent workflows, selected tools, defined policies, and adversarial test cases. Together, we establish measurable acceptance criteria before the evaluation begins.
Run representative and adversarial agent actions through the enforcement boundary.
Verify that covered actions are allowed or denied according to the policies you define.
Review the resulting enforcement decisions and audit records.
Use the results to determine whether SAILLENT should expand into production.
The objective isn't a demo. It's evidence that the enforcement boundary works for your environment.
| Capability | Enforcement | Zero-Trust | Governance | Enterprise |
|---|---|---|---|---|
| Annual contract | $12,000 | $30,000 | $60,000 | $150,000+ |
| Protected actions / month | 1M | 10M | 50M | Custom |
| Protected nodes | Up to 10 | Up to 50 | Up to 250 | Custom |
| PII Shield & redaction | ✓ | ✓ | ✓ | ✓ |
| Prompt injection protection | ✓ | ✓ | ✓ | ✓ |
| Zero-trust tool enforcement | ✓ | ✓ | ✓ | ✓ |
| GitOps policy engine | — | — | ✓ | ✓ |
| Audit trail retention | 30 days | 1 year | Unlimited | Unlimited |
| SIEM export | — | — | ✓ | ✓ |
| SSO / RBAC | — | — | ✓ | ✓ |
| SR 11-7 / OSFI E-23 reporting | — | — | ✓ | ✓ |
| Deployment | Self-hosted + SaaS console | Self-hosted + SaaS console | Self-hosted / VPC | VPC / on-prem / air-gapped |
| Support | Standard | Priority | Dedicated CSM | Dedicated engineer |
| Strategic reviews | — | — | Quarterly | Monthly |
Pricing is based on protected-action capacity, protected deployment nodes, integration scope, deployment requirements, and governance controls. Users and seats are not the primary pricing metric.
A protected action is an AI action evaluated by SAILLENT at a covered enforcement boundary. The precise commercial definition and treatment of retries or other edge cases are defined in your agreement.
A protected node represents a SAILLENT enforcement deployment. It is not a seat, user, model, or individual agent.
Yes. SAILLENT does not charge per seat.
You can expand your protected-action capacity or node count through an agreed plan upgrade or enterprise expansion. SAILLENT is designed around predictable capacity rather than surprise overage billing.
No. SAILLENT is an additional runtime enforcement layer. IAM, identity, network controls, model safeguards, secrets management, and infrastructure security remain important defense-in-depth controls.
SAILLENT supports covered MCP interactions as part of its supported integration surface. Specific MCP architectures and deployment requirements should be validated during technical discovery.
Deployment options depend on the plan and environment. Enterprise deployments can be scoped for customer-controlled infrastructure, including VPC and on-premises requirements where supported.
Yes. A Proof of Value can be scoped around selected workflows, policies, and adversarial scenarios with defined acceptance criteria.
Proof-of-Value scope and commercial terms are agreed in advance. Where applicable, the fee can be credited toward the first annual agreement.
Enterprise is designed for organizations requiring custom capacity, deployment architecture, data residency, support SLAs, security reviews, and other requirements that cannot be represented by a standard plan.
Your agents can decide what they want to do.
Your policies decide whether they are allowed to do it.
Start with a defined enforcement boundary. Prove it. Expand it.
We've optimized our data for AI assistants. Copy this prompt to get instant insights about enterprise AI security.
SAILLENT produces the cryptographic, exportable evidence regulated teams need — across the US, Canada, and Europe. Explore compliance tooling →
Capability claims only — formal certifications & attestations in progress · Technical evidence available under NDA
Request a Technical Briefing →