Start governing agent actions for free. Scale capacity when the workspace needs it.
Every tier keeps the same safety model: deterministic policy remains authoritative, contextual uncertainty can route to SERV, human review never overrides a hard BLOCK, and decisions produce auditable receipts.
Developer$0 / workspace / month
Individual builders and small agent projects getting governed execution into production.
Projects
3
Members
5
Decisions / month
5,000
SERV-assisted decisions
Metered
Policy Studio, Human Review, Decision Receipts
GitHub and Developer API integration
Real usage visibility and server-enforced capacity
Teams operating multiple governed agents and shared production review workflows.
Projects
20
Members
25
Decisions / month
50,000
SERV-assisted decisions
Metered
Everything in Developer
Higher project, seat, and monthly decision capacity
Shared review, audit, notification, and integration operations
Paid activation is not self-serve yet.Published pricing; paid checkout is not enabled until a real billing provider is connected.
ScaleCustom
Organizations that need negotiated capacity across many agents, projects, and teams.
Projects
Unlimited
Members
Unlimited
Decisions / month
Unlimited
SERV-assisted decisions
Metered
Everything in Team
Custom capacity instead of fixed workspace limits
Commercial terms established before plan activation
Paid activation is not self-serve yet.Sales-assisted activation only; there is no simulated enterprise checkout.
BILLING PRINCIPLE
No fake checkout.
The product publishes its commercial model and enforces assigned plan limits on the server. VetoLayer will not show a card form, success screen, or paid upgrade button until a real billing provider can create and verify the subscription.
What usage is measured?
Projects & members
Active projects, active members, and pending invitations that reserve seats.
Decisions
Decision Receipts created during the current UTC calendar month.
SERV
Receipts containing contextual findings or provider trace metadata. It is visible as cost-relevant usage even where the tier has no hard SERV cap.