Usage and Pricing
Your team’s resource charges are calculated from your apps’ usage at the rates below. Each resource has its own unit and price, with included usage shared across all of the team’s apps.
Resource charges are separate from your Pro subscription.
Prices and Included Usage
Section titled “Prices and Included Usage”Your plan includes the following usage each billing period:
| Resource | Hobby Includes | Pro Includes | Additional Usage on Pro |
|---|---|---|---|
| Compute | 180 Nano replica-hours | 720 Nano replica-hours | By instance size |
| Outbound data | 5 GB | 25 GB | $0.15/GB |
| Build minutes | 500 minutes | 1,000 minutes | $0.005/minute |
Included usage is shared across your team’s apps and replicas, resets each billing period, and doesn’t roll over. Adding apps or team members doesn’t increase the included amounts. Compute is measured in replica-hours.
Hobby teams can use Nano instances. You can upgrade to Pro if you need more than the included amounts.
Pro teams can use Nano and larger instance sizes, subject to availability. Compute, outbound data, and build usage above the included amounts are charged at the rates shown.
All prices are in USD, before taxes.
Resource Pricing
Section titled “Resource Pricing”Compute
Section titled “Compute”Compute is measured in replica-hours: one replica of your app running for one hour. Charges depend on each replica’s instance size and running time, even when it is idle.
Compute Prices
Section titled “Compute Prices”| Instance Size | Price for 720 Replica-Hours |
|---|---|
| Nano | $5 |
| Micro | $10 |
| Small | $25 |
| Medium | $70 |
| Large | $140 |
| XLarge | $280 |
| 2XLarge | $560 |
These prices represent one replica running continuously for 30 days. Charges are prorated by running time, so shorter periods cost less and a full 31-day month costs more.
Included compute applies only to Nano instances. Micro and larger sizes are billed at the rates above.
Micro and larger sizes require Pro. See Instance Sizes for CPU, memory, and availability.
Scaling and Changing Sizes
Section titled “Scaling and Changing Sizes”- Scale to zero: When no replicas are running, your app has no compute charge.
- Keep an app running: A minimum of one or more replicas uses compute even when there are no requests.
- Run multiple replicas: Each replica adds running time. Two replicas running for an hour use two replica-hours.
- Change sizes: Each replica is charged at its own size for the time it runs. During a deployment, old and new replicas can overlap; both count while running.
Use Autoscaling to set replica bounds. A maximum replica count limits how far an app scales; it doesn’t set a dollar spending limit.
Outbound Data
Section titled “Outbound Data”Outbound data includes responses sent to your users and data your apps send to public destinations, such as external APIs, databases, or storage services. Both share your team’s outbound allowance. Usage beyond your plan’s included amount costs $0.15/GB.
| Traffic | Counts Toward Outbound Data? |
|---|---|
| Responses sent through your app’s public endpoint | Yes |
| Data sent to external APIs, databases, or storage services | Yes |
| Incoming requests and uploads received by your app | No |
| Data received from external APIs or databases | No |
| Traffic to private IP addresses within the platform | No |
Receiving an upload doesn’t use outbound data. Sending it on to an external service does.
Build Minutes
Section titled “Build Minutes”Build minutes measure the time spent building your app’s container image. Usage beyond your plan’s included amount costs $0.005/minute.
Build time includes successful builds, failed attempts, and retries. Each attempt counts only for the time it runs. Waiting in the build queue, attempts that fail to launch, and deploying the finished image don’t count.
Build time is billed proportionally, including partial minutes.
Redeployments that reuse an existing image, such as applying environment variable changes, don’t add build minutes. Rollbacks don’t rebuild the image either. Running replicas still use compute.
Example Usage Charges
Section titled “Example Usage Charges”A Pro team runs one Nano replica and one Small replica for 720 hours each, sends 40 GB of outbound data, and uses 1,200 build minutes in a billing period:
| Resource | Calculation | Charge |
|---|---|---|
| Nano compute | 720 Nano replica-hours − 720 included = 0 | $0.00 |
| Small compute | 720 Small replica-hours | $25.00 |
| Outbound data | 40 GB − 25 GB included = 15 GB × $0.15 | $2.25 |
| Build minutes | 1,200 − 1,000 included = 200 minutes × $0.005 | $1.00 |
| Resource total | $28.25 |
Your Pro subscription and applicable taxes are added separately.
Billing Periods and Invoices
Section titled “Billing Periods and Invoices”Once usage billing is enabled for your team, resource usage is billed at the end of your subscription period.
Usage totals may take time to update. If a measurement can’t be recovered and verified, we waive that usage rather than estimate a charge.
The dashboard doesn’t yet show metered resource totals. For invoices and payment details, see Managing Your Subscription.
If a charge looks wrong, contact us with your team name, invoice, and the dates you’d like us to check.