Free tier limits
Everything below is available on a Hostless account with no payment method attached. These are the limits the platform enforces today.
What you get
Your account has one free allowance, shared across everything you run:
| Resource | Free allowance |
|---|---|
| vCPU | 1 in total, shared across all apps, workers, cron jobs, and databases |
| Memory | 1 GB in total, shared the same way |
| Disk per app or worker | 5 GB, per resource, never shared |
| Storage per database | 1 GB, per resource, never shared |
| Apps, workers, databases | Unlimited in number |
| Cron jobs | Unlimited, and their runtime is never billed |
| Builds | Free and never metered |
| Static sites | Included |
| Custom domains with automatic SSL | Included |
| Deployments | Unlimited, with automatic deploys from your Git provider |
| Review apps, logs, metrics, health checks, web terminal | Included |
| Collaborators | Unlimited, with no per-seat fee |
The count is not what runs out, the total is. CPU and memory come out of one pool, so the question is never "how many apps do I get" but "how much am I asking for at once".
A default app is provisioned at 0.5 vCPU and 512 MB, and a default database at 0.1 vCPU and 512 MB. An app plus a database therefore sits inside the allowance with vCPU to spare. A third resource means shrinking something or adding a card, and that is the point at which we ask.
Storage sits outside the pool on purpose. Ephemeral scratch space on an app and persistent disk on a database are different costs, and a build filling temporary space should not be a pricing event.
When you need more
Add a payment method once and you can scale past the allowance. You are billed only for the usage above it:
| Axis | Rate above the allowance |
|---|---|
| vCPU | $0.03 per vCPU-hour |
| Memory | $0.003 per GB-hour |
| Database storage | $0.003 per GB-day |
There is no flat fee and no per-app fee, and nothing inside the allowance is ever charged. Scaling back down is always allowed, including from above the allowance.
Set a spending limit and we alert you at 50, 80, and 100 percent of it. At the limit, new paid changes are refused and everything already running stays up. See Cost Breakdown for the billing math, Rates and allowances for the current figures, and Payment Methods to add a card.
Accounts created before pay-as-you-go
Accounts that predate the pay-as-you-go rollout stay on the earlier tier model until they are moved, and nothing about what they are charged has changed. On those accounts the free tier is capped by count rather than by a shared allowance:
| Resource | Free allowance |
|---|---|
| Apps | Create up to 2. One running at a time. |
| Databases | 1 database at 0.1 vCPU, 512 MB memory, 256 MB storage |
| Workers | Up to 2 |
The app limit has two separate parts, and they catch people out. You may create two free apps, but only one free app may be running at any moment. Starting a second free app returns Upgrade to UNLEASHED plan. Scale the first one down to start the other.
Also unavailable on those accounts: custom domains, build resource configuration, scaling configuration, and a third app, a second database, or a third worker.
Attaching a card, or holding a credit balance, moves such an account to the Unleashed plan, which lifts the free count limits. Unleashed apps cost $15 per month per app, plus usage above the included limits, and unleashing an app cannot be undone. See Scaling and pay-as-you-go and Plans.
Overdue invoices
While an invoice is overdue, creating new resources and scaling existing ones are both blocked. Running workloads are left alone. Settle the invoice from Billing to restore normal operation.