Evaluation
Observe
Free
Evaluate Sevra before routing a production money workflow through it.
- 1 evaluation workflow
- 5,000 evaluation actions/month
- 1 included seat
Pricing
Start with one money workflow. Expand when the evidence earns it.
Sevra is priced by the production workflows it protects, the decisions it evaluates, and the team operating the control.
01 · Define the workflow
02 · Route each action
03 · Keep the evidence
Plans
A clear boundary for each stage.
Autonomy remains a safety setting. It is not a pricing meter and paying more never makes an unsafe action acceptable.
Production
RecommendedGate
$750/month
Protect the first production money workflow.
- 1 protected production workflow
- 100,000 guarded actions/month
- 5 included seats · $50/additional seat/month
Production
Scale
$2,500/month
Standardize Sevra across several money operations.
- 5 protected production workflows
- 1,000,000 guarded actions/month
- 15 included seats · $50/additional seat/month
- Advanced organizational governance
Organizational
Enterprise
Custom
Make Sevra an organizational control across a larger deployment.
- Custom workflows, actions, and seats
- Negotiated governance and evidence scope
- Contractual deployment and support terms
How billing works
The meter follows the control boundary.
A Stripe refund in production can be one protected workflow. Every unique canonical refund request counts once. Agents and policies can share that boundary; active human operators use the plan's included and additional seats.
01
Protected workflows
One action family, through one integration, in one production environment. Stripe refunds and Stripe payouts are separate workflows. Several agents and policies can share one workflow.
02
Guarded actions
One unique authenticated canonical request counts once when Sevra reaches Allow, Require approval, or Block. Idempotent retries and later approval or review events do not add another action.
03
Included and additional seats
One active, accepted human workspace member counts as one seat. Gate and Scale include seats and price each additional seat at $50 / additional seat / month. Paid-seat admission requires verified workspace billing authority and fails closed until Stripe confirms provider state. Agents and service identities do not count as seats.
Compare
What changes as protection expands.
The core judgment stays deterministic. Plans change deployment scope, included action volume and seats, governance, evidence breadth, and support.
Swipe horizontally from the capability names to compare every plan.
| Capability | Observe | Gate | Scale | Enterprise |
|---|---|---|---|---|
| Protected production workflows | None | 1 | 5 | Custom |
| Production guarded actions | None | 100,000 / month | 1,000,000 / month | Custom commitment |
| Evaluation access | 1 workflow · 5,000 actions | 1 workflow · usage tracked separately | 5 workflows · usage tracked separately | Negotiated |
| Agents and policies | Evaluation scope | Unlimited | Unlimited | Unlimited |
| Included human seats | 1 included | 5 included · $50 / additional seat / month | 15 included · $50 / additional seat / month | Custom terms |
| Human approval | — | Configurable | Configurable | Negotiated governance |
| Dual approval | — | Configurable | Dual approval and separation of duties | Negotiated governance |
| Proof Loop reviews | — | Included | Included | Negotiated scope |
| Case files | — | Conditional supported paths | Conditional supported paths | Negotiated scope |
| Evidence reports and exports | Basic evaluation reporting | Evidence-linked | Broader | Contractual requirements |
| Support | Evaluation | Standard | Priority | Contractual |
Questions
Predictable at the request boundary.
What is a protected workflow?
One action family, through one integration, in one production environment. Stripe refunds in production are one workflow; Stripe payouts in production are another. An explicitly identified test or staging mirror does not consume a production-workflow allowance.
What counts as a guarded action?
One unique authenticated canonical request counts when it reaches a durable Allow, Require approval, or Block verdict. The amount, currency, risk score, and verdict do not change the unit.
Are retries counted twice?
No. Retries that resolve to the same canonical request and idempotency identity count once.
Do Allow, Require approval, and Block all count?
Yes. Allow, Require approval, and Block count equally. A later approval, denial, timeout, review, or case-file event does not count again.
Do test, demo, or seeded requests count?
Demo and seeded traffic do not count. Server-attested evaluation traffic is tracked separately. A freeform label or request name is not enough to classify production traffic as evaluation.
How many seats are included?
Observe includes 1 active human seat. Gate includes 5, and Scale includes 15. Gate and Scale price each additional active-human seat at $50 / additional seat / month, subject to verified workspace billing authority and provider confirmation. Enterprise seat terms are custom.
Who counts as a seat?
One active, accepted human workspace member counts as one seat, including the owner. Pending, expired, revoked, removed, suspended, and unaccepted invitations do not count. Agents, API keys, service identities, Telegram identities, and automation principals do not count.
What happens when another paid seat is added?
The approved Gate and Scale catalog rate is $50 / additional seat / month. A billing-authorized administrator can request the seat, but admission fails closed if the workspace billing contract, exact Price, or provider state is unavailable. Sevra keeps the requested quantity separate from the provider-confirmed quantity, and the change is confirmed only after Stripe confirms it.
What happens when action usage exceeds the included amount?
During early access, Sevra does not stop the gate or automatically charge an overage. The authorized Billing console flags 80%, 100%, and above-plan usage so we can resize the plan with you. Policy judgment and evidence recording continue without a quota-induced bypass.
Can multiple agents share a workflow?
Yes. Multiple agents and policies can share one protected workflow when they operate the same action family through the same integration and production environment.
Can another workflow be added later?
Yes. Gate includes one and Scale includes five. Existing protection is preserved after a downgrade; Sevra blocks activation of additional workflows until the allowance is resolved.
Does Sevra hold or move funds?
No. Sevra decides and audits. It does not hold, receive, or move funds. Execution stays in your systems with credentials and scopes you control.
Are case files available for every action?
No. Case-file investigation and reproduction are conditional on safe supported paths and may be skipped, unsupported, inconclusive, or failed.
What happens after a downgrade?
Sevra never deletes workflows, agents, policies, members, approvals, reviews, case files, or audit evidence. Existing people remain, existing workflows stay gated, and an over-entitled account cannot activate another production workflow until the allowance is resolved.
First production boundary
Protect the workflow before the agent executes.
Start in evaluation, or put the Gate plan around your first production money workflow.