Sandbox & limits
What the free sandbox includes, how it is limited, and when production billing starts.
Every AnyBio organization starts with a free sandbox environment. It is a real environment on real infrastructure - the same APIs, SDKs, and widgets as production - scoped for building and testing. Sign in to create yours; the first sign-in sets up your organization automatically.
What the sandbox is for
Build your integration end to end without a contract or a card: render widgets, mint tokens, stream data, run scenario data through the pipeline. The sandbox is where you develop; production is where real users and real health data live.
How the sandbox is limited
The sandbox is capped, not metered for billing:
- Rate limits - API throughput is capped per organization. Hitting a cap throttles or rejects requests; it never generates a charge.
- Retention - sandbox data is for development and is retained on a shorter window than production.
- No real patient data - the sandbox is for synthetic and test data only. Use Synthetics scenarios to generate realistic streams without hardware.
If you hit a sandbox cap while building something real, that is the signal to talk to us about production access.
When billing starts
You are never invoiced for sandbox usage. Billing begins when your organization moves to a production environment and live transactions flow - production is metered on usage, not seats. For current production terms, contact us.
Environment model
| Environment | Purpose | Billed? |
|---|---|---|
| Sandbox | Build, test, integrate - synthetic data only | Never - capped instead |
| Production | Live users, real health data | Usage-based |
Your API keys and project keys are scoped per environment, so a sandbox key can never write into production.