Context LayerSeats match the value
Provider identities and MCP credentials belong to people, so paid value grows with the members receiving secure context.
Proposed pricing
Pricing that scales with the team.
Start with your own workflow, then bring the whole engineering team into one permission-aware context layer.
Individual
R0
forever
For developers proving the workflow with their own tools.
- 1 workspace member
- 2 connected providers
- 1,000 MCP tool calls per month
- 7-day activity history
- Personal tokens and agent connections
Team
RecommendedR299
per member / month
For teams turning shared context into daily infrastructure.
- Unlimited workspace members
- All available provider integrations
- 10,000 MCP tool calls per member, per month
- 90-day activity history
- Integration bundles, notifications, and daily digests
- Owner controls and email support
Enterprise
Custom
designed around your organisation
For organisations with tailored governance and support needs.
- Everything in Team
- Custom tool-call limits and data retention
- SAML SSO and automated provisioning
- Audit exports and governance review
- Guided rollout and priority support
- Service-level agreement
Why this model
Built around how context is actually consumed.
Usage stays predictable
Clear monthly call allowances make spend understandable while keeping normal provider access broad and useful.
Complexity is priced honestly
Advanced governance, retention, and rollout support vary by organisation and are scoped together at Enterprise level.
What is a tool call?
One request from an MCP client to a Context Layer provider tool, whether it reads context or performs an enabled action.
Are provider subscriptions included?
No. Jira, Confluence, GitHub, Bitbucket, Teams, and other upstream subscriptions remain with the customer.
Is billing live?
Not yet. This page describes the proposed commercial model; no plan is currently charged or enforced.