Billing
Plans, usage, credits and the spend budget.
Billing is set per workspace under Settings → Billing. Only admins can change it.
Plans
Deploying needs a Compute plan: Starter, Pro or Business. If your workspace doesn't have one yet, the dashboard asks you to choose one when you deploy. The plans differ in their fee, in how large instances can be, and in what's included, such as team members and custom domains. teral.dev/pricing has the current prices.
Each plan's fee comes back to you as usage credit for the same amount. Usage is paid from the credit first. What you use beyond it is billed on top.
Changing plans takes effect right away. On an upgrade you pay the difference now and receive it as extra credit. On a downgrade you keep this period's credit, and the lower fee starts with the next period.
What counts as usage
| Item | Measured as |
|---|---|
| CPU | CPU time your instances actually use, in vCPU-hours |
| Memory | Memory set aside for your instances, in GiB-hours. 1 GiB for one hour is one GiB-hour. |
| Storage | Disks you added, by size and time, in GiB-hours |
| Egress | Data your apps send to the internet, in GiB |
Settings → Usage shows the current period per project, app and environment.
Spend budget
A spend budget is a monthly amount for usage. Teral emails you when spending reaches 50%, 75% and 100% of it.
You can also choose to stop workloads at the budget. When spending reaches it, Teral pauses all deployments in the workspace for the rest of the month. Visitors then get a spend_limit_reached error.
While compute is paused
To start again before the month ends, raise or remove the budget. Your deployments resume on their own, without new deployments.
Cancel
Turn off Compute for this workspace in the billing settings ends the plan. Running apps stop.