Free tier limits
The upcoming shared allowance policy lets you start within a bounded free entitlement. Existing billing cycles retain their current terms until the new policy applies.
What you get
An account-wide maximum of 0.5 vCPU, 1 GiB RAM, and 256 MiB database storage, shared across all projects owned by the account. Each web or worker process has an individual maximum deduction of 0.5 vCPU and 256 MiB RAM. Each database has an individual maximum deduction of 0.5 vCPU, 1 GiB RAM, and 256 MiB storage.
These are maximum deductions, not guaranteed free capacity per resource or deployment defaults. Eligible usage shares the account pool proportionally when combined demand exceeds a limit. Replicas share their process allowance, and unused entitlement does not roll over. Database storage is shared; temporary app disk is separate.
Embedded workers and observed embedded cron runtime appear under their parent app. Standalone workers appear separately. Builds and standalone cron are outside this new billing policy.
Static sites, automatic SSL, Git deployments, and collaboration remain available. Adding a project does not create another free allowance.
When you need more
Above-entitlement capacity requires a payment method or qualifying credit. Standard USD rates are $0.03 per billable vCPU-hour, $0.003 per GiB-hour of memory, and $0.003 per GiB-day of database storage, with no flat PAYG fee or per-app fee.
A spending limit blocks new paid capacity when reached, while existing resources continue running and can incur charges. See Cost Breakdown for calculations and existing-cycle behavior, Limits for capacity checks, 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.