Start with the services you need.
Choose the compute, data and coordination services that fit your workload. Access, allowances and commercial terms differ by product. Contact us for current rates and limits before committing production workloads.
Choose a product
Use one service on its own or compose several. Follow that product’s setup and authentication requirements.
Understand retained resources
Compute activity, reserved capacity and stored data are different usage dimensions. An idle process does not mean every resource has stopped accumulating usage.
Confirm your terms
Ask about rates, included allowances, quotas, support and retention for the services you plan to use.
Evaluate
Open the setup guide for your chosen product. Free allowances and anonymous access, where offered, are specific to that service.
Find a setup guide →Plan production usage
Share expected compute, storage, concurrency and data retention needs so we can discuss the applicable plan and limits.
Discuss your workload →Review enterprise needs
Tell us about your security review, procurement, deployment and support requirements.
Talk to the team →Know what your workload needs.
This is a guide to access and usage boundaries. Obtain the current product terms and rates for a quote.
| Service | Usage & terms | Getting started |
|---|---|---|
| run9 | Host compute and retained storage. Reserved hosts accumulate usage while idle as well as while working. | Sign in with organization-scoped credentials. |
| db9 | Check the current database plan, compute and storage allowances with db9. | Anonymous database creation is available; account claiming has its own authorization flow. |
| drive9 | Confirm workspace storage, access and retention terms for your deployment. | Anonymous workspaces are for evaluation; review the production setup guide. |
| mem9 | Check current memory storage and API allowances with mem9. | Follow the mem9 setup guide for your agent or application. |
| owl9 | Confirm transcript storage and retention limits for your deployment. | Install the CLI, configure a space and set up your runtime integration. |
| task9 · tape9 · inbox9 · pulse9 | Confirm service-specific quotas, storage and message retention limits. | Configure each service endpoint and space before use. |
| smith9 | Contact us for current hosted access and commercial terms. | Authenticate, then create an environment and session. |
| chord9 | Contact us for current access and commercial terms. The Usage view is informational, not an invoice. | Sign in and connect a local Host or configure a cloud session. |
The questions engineers ask first.
Do I need to sign up?
Installing the CLI does not require an account. Using a service can: run9 and smith9 require authentication, and chord9 requires sign-in. Some services offer anonymous evaluation; follow their individual setup guides.
Does idle always mean free?
No. run9 measures host compute and retained storage. Reserved hosts accumulate usage while idle as well as while working, and retained data has a storage footprint. Confirm the applicable rates and allowances for your plan.
Can I use just one service?
Yes. You can adopt services independently. Check each service’s access requirements, plan and limits.
Is inactive data kept forever?
No. Retention depends on the service and data type. For example, chord9 artifacts normally expire after one year and may expire sooner after a session is archived or a Host is unlinked. Keep exports of data you need to retain. See the retention overview.
Are branching and concurrency unlimited?
No. Product quotas and eligibility rules apply. Ask us to confirm the limits for your workload before scaling it.
Where do I get exact rates?
Email x@db9.ai with the products and usage you expect. We can discuss current pricing and access for that workload.
Tell us what you want to run.
Share your product choices and expected usage. We can help you identify the setup, limits and commercial terms to review.