Limits
A resource at or below every listed ceiling is free and needs no card or credit.
| Resource | vCPU | Memory | Storage |
|---|---|---|---|
| App web process | 1 | 1 GB | 5 GB temporary |
| Worker process | 1 | 1 GB | 5 GB temporary |
| Cron job | 1 | 1 GB | not applicable |
| Database | 1 | 1 GB | 1 GB persistent |
Apps, workers, databases, and cron jobs are unlimited in count. Each web or worker process receives its own compute ceiling.
Cron-job runtime and builds are never billed. The cron CPU and memory ceiling above is still enforced at create and resize time, so a cron job larger than 1 vCPU or 1 GB requires payment capability even though its runs cost nothing. A job is measured by the larger of its request and its limit, a job created without an explicit size is provisioned at the ceiling and stays free, and cron jobs declare no storage. Builds are provisioned with 4 GB of memory and are never metered.
Rates above the ceiling
| Axis | Rate |
|---|---|
| App, worker, or database CPU | $0.03 per vCPU-hour |
| App, worker, or database memory | $0.003 per GB-hour |
| Database storage | $0.003 per GB-day |
Usage within the ceiling remains free. A request above any ceiling requires a card or positive credit balance in the resource's project. Without one, Hostless blocks the change and identifies the exceeded axis.
Compute is reported hourly and database storage daily. The ceiling is an allowance per metered hour, so a cycle's free allowance is the ceiling multiplied by the hours actually collected. Above-ceiling quantities round up to a whole unit, and any positive overage bills at least one cent. A cycle is priced at the rates in force when it started; a rate change applies from the next cycle unless it was scheduled for a date inside the current one. See Cost Breakdown for examples and invoice behavior.
Spending limit
Reminders are sent at 50%, 80%, and 100% of the billing-cycle spending limit. At 100%, Hostless blocks new above-ceiling create and scale actions. Existing resources stay online, and scaling a resource down is never blocked. Raising or removing the limit permits new paid actions again.