Use-first. Claim later. Pay only when running.
There’s no signup to start — hand an agent the skill or install the CLI and build. Each service meters its own usage, so you pay for what you actually run, nothing for what sits idle. Attach an account when you’re ready to keep your work.
Use-first
No signup, no card to begin. Services auto-create on first use — start building immediately.
Pay only when running
run9 sandboxes sleep on idle and wake on call. Idle work doesn’t show up on the bill.
Per-product usage
Each atomic service meters its own unit. Compose only what you need and pay only for that.
Claim later
Begin anonymously; attach an account when you want to keep, share, or scale what you built.
No signup to start. Build on the live services right away.
- No signup, no card
- Hand an agent the skill
- All live services to build on
- Generous starter usage
- Hibernates, never deletes
- Community support
Claim your account and pay for what you run, per product.
- Pay only when running
- Per-product metering
- Every live service, no gating
- Claim an account anytime
- Branch & fork without limits
- Email support
Predictable cost and headroom for production workloads.
- Committed-use pricing
- Higher per-service limits
- Usage dashboards
- Priority support
- Onboarding help
For larger or regulated deployments.
- Custom terms & invoicing
- Deployment options
- Security & procurement review
- Dedicated support
- Roadmap input
No tier gates a service. Every live product is available on the free tier — usage is what differs.
What each service meters.
Atomic services, atomic bills. You pay for the unit each product is actually about — and nothing for the ones you don’t compose.
| Service | Status | You pay for |
|---|---|---|
| run9 | live | Active sandbox time. Sleeps on idle, wakes on call — you pay only while it runs. |
| db9 | live | Database compute and stored data, with file storage built in. Branches included. |
| drive9 | live | Stored data and retrieval across the shared filesystem; the secrets vault is included. |
| mem9 | live | Memory stored and recalled across your agents and sessions. |
| owl9 | live | Captured sessions and how long you keep them. |
| task9 · tape9 · inbox9 · pulse9 | live | Usage-based across the primitives. Free to start, auto-created on first use. |
| smith9 | coming soon | Active agent moments — built on run9, so you pay for active time only. |
| auth9 · chord9 | coming soon | Pricing announced at launch. |
Exact rates are shown when you claim an account. Coming-soon services price at launch.
The questions engineers ask first.
Do I really not need to sign up?
Right. Services auto-create on first use, so an agent or a CLI can start working immediately. You claim an account later to keep and scale what you built.
What does “pay only when running” mean?
run9 sandboxes wake on call and sleep on idle. You’re billed for active time, not for a sandbox that’s sitting idle waiting for the next message.
Can I use just one service?
Yes. Each service is atomic and meters independently — take db9 on its own, or compose the whole stack. You only pay for what you use.
What happens to free-tier work I leave alone?
It hibernates rather than deletes. Come back and wake it; nothing is thrown away when you go quiet.
How are the coming-soon services priced?
smith9, auth9, and chord9 price at launch. smith9 is built on run9, so it follows the same pay-for-active-time model.
Where do I see exact rates?
Per-service rates appear when you claim an account, so you can see them against your real usage rather than a generic table.
Start building before you pay anything.
Hand an agent the sys9 skill, or install the CLI and create your first database in seconds. Claim an account when you’re ready.