Usage and credits
Understand compute credits, VM-hour estimates, and concurrency.
Your monthly subscription includes the same dollar amount of compute credits. Credits pay for running computers; concurrency is how many VMs you can run at once. More terminals on the same computer do not use another VM.
Plans and compute credits
| Plan | Monthly price and included credits | Concurrent VMs |
|---|---|---|
| Individual | $20 | 10 |
| Team | $199 | 100 |
| Scale | $499 | 300 |
| Enterprise | Custom | Custom |
A standard VM has 4 vCPU and 8 GB RAM and costs $0.25/hour. For example, $20 in credits covers about 80 standard VM-hours: one VM for 80 hours, or two for 40 hours each. Other configurations use credits at their own hourly rates.
Unused monthly credits expire. Purchased credits roll over. Add credits when you need more compute, or upgrade when you need more concurrent VMs. Coding-agent subscriptions and model-provider usage are separate.
Check running time
cube usage
cube usage --detailedThe CLI shows VM runtime for the current UTC calendar month; --detailed adds
a breakdown by Session. Its current cost estimate uses the standard $0.25/hour
rate. It is not a credit balance or a final bill for different VM sizes.
Stop idle compute
Leaving a terminal does not pause the VM. Run locally when you are done:
cube pause feature/payments
cube sessionsThe pause command confirms the request before shutdown finishes. Check the
listing for stopped. Pause keeps your files but stops agents and services.
Resume with cube connect feature/payments, then restart those processes.
Use cube kill <session> only when you no longer need the computer or its disk.
Push your code and copy out any files first: deletion is permanent.
See lifecycle.