Pricing starts with the first system and the scope around it.
We scope pricing around the first system or package you want to put into use, the operational load around it, and the rollout support required to run it well.
Plans
Starter
Perfect for individuals getting started with AI
- 1 user
- 2 apps
- 5 GB storage
- ~400K tokens
- Standard support
Pro
Best for growing teams and small businesses
- 1 user
- 5 apps
- 20 GB storage
- ~2M tokens
- Priority support
Business
For established businesses with advanced needs
- 3 users
- 10 apps
- 100 GB storage
- ~8M tokens
- Priority support
Enterprise
Custom solutions for large organizations
- 10 users
- 30 apps
- 500 GB storage
- ~80M tokens
- Standard support
What shapes the initial scope
System or package scope
Pricing starts with the first operational system or package you want to put into use, whether that is vendor operations, service exceptions, qualification work, or another governed process.
Operational load
Volume, document mix, operator flow, and the amount of branching or follow-through affect the scope of the deployment.
Governance depth
Authorization, approvals, audit posture, and the level of control your team requires before wider rollout.
Deployment scope
Scope depends on what the deployment should own, how work moves through the system, and how much rollout support your team needs.
Start with one system and a clear rollout boundary.
Deployment scope depends on the first system or package, the operating pattern around it, the volume involved, and the level of governance the team needs in production.
- Start with one production system or package and the operator experience around it.
- Match the rollout to the governance depth, volume, and support the team actually needs.
- Add more packages and operating paths later if the first deployment is delivering value.
Start with a clear operational boundary, then expand only after the first system is working well.
Pricing questions
How is pricing scoped?
Pricing is scoped around the system or package, the operational complexity, the governance depth, and the rollout support required to put it into production.
Can we add more packages or operating paths over time?
Yes. Many teams begin with one operational system or package, put it into production, then extend the same model into adjacent governed work.
Why is pricing conversation-led?
Because system scope, operational volume, governance depth, and rollout needs vary materially. A fixed table would hide the differences that shape a successful deployment.