Getting Started
Billing
How Iris billing works
Detailed billing documentation is coming soon. In the meantime, reach out via Discord or email for pricing questions.
Overview
Iris bills based on sandbox compute time. Suspended sandboxes do not accrue compute charges.
Key Points
- Running sandboxes — billed per second of CPU and memory usage
- Suspended sandboxes — storage only, no compute charges
- Deleted sandboxes — no charges
- Checkpoints — billed for storage consumed (copy-on-write means only changed pages count)
- Forks — billed the same as a new sandbox from the moment of creation
Cost-Saving Tips
- Suspend idle sandboxes — call
sandbox.suspend()when your agent is not actively running. Resume withsandbox.resume()when needed. - Kill sandboxes you're done with —
sandbox.kill()stops all charges immediately. - Delete old checkpoints —
sandbox.checkpoint.delete(id)removes stored state you no longer need. - Fork, don't keep long-lived branches — kill experiment branches after use.
Usage Dashboard
View your current usage and billing history in the Iris Dashboard.