Cost breakdown and per-second billing
The Cost Breakdown shows exactly how your charges are calculated. Hostless is pay-as-you-go: every resource is free within a per-resource free ceiling, and you are billed only for the usage above that ceiling. There is no flat monthly fee and no per-app fee.
View Cost Breakdown
- Navigate to Billing > Cost Breakdown.
- Select a Billing Cycle Period to view the breakdown for that cycle.
Each row corresponds to an app or a database. Use the Expand/Collapse feature to see granular details: Resource, Unit, Usage, Usage Above Limit, Price per unit, and Total for each resource.
How billing works
Every resource is free at or below its free ceiling:
| Resource | vCPU | Memory | Storage |
|---|---|---|---|
| App | 1 | 1024 MB (1 GB) | 5120 MB (5 GB) temporary |
| Worker | 1 | 1024 MB (1 GB) | 5120 MB (5 GB) temporary |
| Cron job | 1 | 1024 MB (1 GB) | not applicable |
| Database | 1 | 1024 MB (1 GB) | 1024 MB (1 GB) |
You are billed only for the amount above the ceiling, at these rates:
| Axis | Rate above ceiling | Unit in the breakdown |
|---|---|---|
| vCPU (app, worker, or database) | $0.03 per vCPU-hour | vCPU-hours |
| Memory (app, worker, or database) | $0.003 per GB-hour | GB-hours |
| Database storage | $0.003 per GB per day | GB per day |
Cron jobs and builds are never billed for runtime. A cron job must still be created and resized within the cron CPU and memory ceiling above; beyond it, the owner needs a card or project credit. Cron jobs declare no storage, so no storage ceiling applies to them. Builds run with 4 GB of memory by default and are never metered.
How usage is measured
Compute is metered as resource-hours: an app process running at 1.5 vCPU for one hour books 1.5 vCPU-hours. The ceiling is an allowance per metered hour, so your free allowance for a cycle is the ceiling multiplied by the hours actually collected. A resource that runs for half the cycle gets half the allowance and is compared against half the usage, so the bill does not change if collection runs more or less often.
Database storage is metered as GB-days: the storage held above the ceiling multiplied by the whole days it was held.
How amounts are rounded
- Quantities round up to a whole unit, so above-ceiling usage never bills as zero. 0.15 vCPU-hours above the ceiling bills as 1 vCPU-hour ($0.03).
- Storage GB-days round up to a whole GB-day.
- Each line item is rounded to cents once. Any strictly positive overage bills at least one cent, so 1 GB-hour of memory ($0.003) appears as $0.01 rather than $0.00.
- Usage within the ceiling nets to zero on every resource and shows no charge.
Which rates apply
A cycle is priced at the rates in force when the cycle started. A published rate change applies from your next cycle, unless it was scheduled to take effect on a date that falls inside the current one. Invoices already issued are never restated.
App charges
Each app web process, embedded worker, and standalone worker is billed independently above its own compute ceiling:
- APP CPU - each process's vCPU usage above 1 vCPU, reported hourly at $0.03 per vCPU-hour.
- APP MEMORY - each process's memory usage above 1 GB, reported hourly at $0.003 per GB-hour.
A process at or below 1 vCPU and 1 GB accumulates $0. One process does not consume another process's free ceiling, and there is no daily base fee.
Database charges
Databases are billed separately, on their own provisioned resources, only above the ceiling:
- DATABASE CPU - $0.03 per vCPU-hour above the 1 vCPU ceiling.
- DATABASE MEMORY - $0.003 per GB-hour above the 1 GB ceiling.
- DATABASE STORAGE - $0.003 per GB per day for storage above the 1 GB ceiling.
A database that stays at or below 1 vCPU, 1 GB RAM, and 1 GB storage accumulates $0 for every resource. There is no per-day base fee.
Worked example
An app process running at 1.5 vCPU and 2 GB RAM for every hour of a 30-day cycle (720 metered hours):
- CPU: 1.5 vCPU x 720 hours = 1080 vCPU-hours metered, against a 1 x 720 = 720 vCPU-hour allowance. 360 vCPU-hours above the allowance x $0.03 = $10.80
- Memory: 2 GB x 720 hours = 1440 GB-hours metered, against a 1 x 720 = 720 GB-hour allowance. 720 GB-hours above the allowance x $0.003 = $2.16
- App total: $12.96
Had the same process run for only half the cycle, both the usage and the allowance would halve, and the bill would be $6.48.
A database holding 6 GB of storage for the same cycle:
- Storage: (6 - 1) GB above the ceiling x 30 days = 150 GB-days x $0.003 = $0.45
If you resize storage mid-cycle, each storage size appears as its own line with the number of days it was held.
Everything within the ceiling on all three axes stays free.
Spending limit
Set a spending limit for the billing cycle to bound pay-as-you-go usage. You get reminders at 50%, 80%, and 100% of the limit. At 100%, new above-ceiling create and scale actions are blocked, but everything already running stays up. Scaling a resource down is never blocked, whether by the limit or by a missing card. Raise or remove the limit to add paid usage again.