Balance and payments
Last updated
There are no subscription plans. Billing is credit-based and pay-as-you-go: you top up a balance, and allocated CPU, RAM, and disk is drawn from it per minute.
How it works
- Top up your balance so your apps can run.
- All allocated resources are billed per minute at $1.90 per vCPU-month, $1.95 per GB RAM-month, and $0.25 per GB disk-month.
- Your balance is reduced as charges accrue.
Current unit prices and worked examples are on the pricing page, which is the authoritative source.
Your first app
On a new account, the first app you deploy gets a short trial run — long enough to watch it build, start and do its job, so you can confirm your code works here before paying for anything. When that run ends, the platform stops the app.
Nothing is deleted. The app, its configuration, its environment variables and its volumes are all still there. Add credit and start it again, and it runs continuously from then on: there is no session limit and no scheduled stop once there is credit on the balance.
Topping up
Add credit from the Balance section of the panel. Payments are handled by the integrated payment providers, and a successful payment produces a notification — in the panel and by email.
Your apps draw resource charges from this balance. Account quotas limit what you can allocate; contact support if you need higher limits.
If your balance runs out
Your applications are stopped. They aren't deleted, and volumes are intact — topping up and starting them again restores everything.
You'll be notified when this happens, in the panel and by email, which is a good reason to make sure your account email is one you read.
Keeping the bill predictable
Because you're billed on allocation rather than usage, cost is something you choose rather than something that happens to you:
- Right-size presets, and lower them again after you've fixed whatever made you raise them.
- Remember that the app count doesn't affect pricing — only total allocated resources do.
- Watch disk, which grows on its own if something writes to a volume without pruning.
There is no per-request charge, no bandwidth metering, and no charge for ports, certificates, logs or the dashboard.
What this doesn't cover
If your application calls a paid third-party API — a language model, an email provider, a payment processor — that spending is between you and that provider. Nothing in your hosting configuration can cap it. Set a spend limit with the provider directly, and limit expensive operations in your own code.