Contextus pricing
Start free, then add shared control as your workflows grow.
Explore one governed workflow at no cost. Upgrade when you need personal policies, shared approvals, longer proof history, team visibility, or enterprise identity controls.
Pricing is public. Billing lives in the product.
Use this page to compare plans. Once you are a customer, plan changes, invoices, and payment details are managed inside the Contextus dashboard.
Open dashboard billingFree
For exploring your first governed agent workflow.
- Documentation and starter templates
- Semantic search
- Limited IDE and MCP tooling
- 1 API key
- 7-day results retention
- Community support
Builder
For individual developers running governed workflows.
- API access
- Full IDE and MCP tooling
- Policy Editor
- Personal audit history
- Eval reports
- 5 API keys
- 30-day results retention
Team
For teams sharing policies, approvals, and evidence.
- Shared approval workflows
- Audit export
- Role-based access
- Shared dashboards
- Document indexing
- 20 API keys
- 90-day results retention
- 5 seats included
Enterprise
For organizations with advanced identity, deployment, security, and procurement requirements.
- SSO and SAML
- Custom deployment
- Compliance workflows
- Custom data retention
- Dedicated support
- Procurement support
- Custom API key policy
Pricing FAQ
Questions buyers ask before signup.
Does Builder include governed routing?
Builder includes API access, policy controls, and the personal routing and proof surfaces needed to test a governed workflow before moving into shared team operations.
What is personal audit history?
Builder includes a personal view of approvals, policy outcomes, and recent workflow activity so individual developers can review what happened without a shared team workspace.
How do Team approvals work?
Team adds shared approval workflows for risky tool actions, plus audit export and role-based access so reviews and escalations belong to the team workflow.
Can I change plans anytime?
Yes. You can upgrade or downgrade as your rollout changes. In-app billing handles plan updates, and pricing changes are prorated when applicable.
When should I move from Builder to Team?
Move to Team when governance becomes shared: multiple people need approval workflows, audit export, role-based access, shared dashboards, or a common workspace.