Plans
A plan for how
your team ships.
Clear service scope, visible usage, and defined retention.
Explore
A sandbox for learning
Sandbox access
- Example workspace
- Core SDK behavior
- Saved sample scenarios
Team
A shared workflow for shipping
Contact for pricing
- Projects and environments
- Review and scenario evidence
- Team roles and audit history
Scale
Operational service for growing teams
Contact for pricing
- Higher service limits
- Retention and support options
- Usage visibility
Compare the service scope.
| Capability | Explore | Team | Scale |
|---|---|---|---|
| Local SDK behavior | Included | Included | Included |
| Projects & collaboration | Sandbox | Shared workspace | Extended scope |
| Evidence retention | Sample data | Defined by plan | Defined by plan |
| Usage visibility | Sample | Included | Included |
| Support | Documentation | Defined by plan | Defined by agreement |
What happens at a usage limit?
Management and service limits follow a published policy. Billing limits do not hard-block critical configuration reads.
Which usage is counted?
The plan defines distribution, retention and operational scope. Local flag evaluations are not individually network-billed calls.