App hosting usage rates and billing

Hobby costs $10 per month and provides $10 of runtime credit. Pro costs $50 per month and provides $50 of runtime credit. The plan fee covers usage up to its credit. You pay separately for usage above that amount.

Plan limits set the number of resources and members an organization can have. Hobby includes 200 build minutes and Pro includes 500. Additional build minutes cost $0.02 each. Enterprise uses custom terms; the numeric examples below describe Hobby and Pro only.

Each billing period keeps the allowance and runtime credit recorded for that period. Updated plan terms apply to periods that start after the change, so an active period can show different amounts from the current plan catalog.

• Compare published plans →

These rates apply across plans except for the database service fee. CPU is measured per vCPU-hour, RAM per billable GB-hour, and persistent disk per GB-day. Database service fees are per database per month, prorated hourly using 720 hours. Object storage is measured separately at $0.035/GiB-month, prorated hourly.

The RAM billing label GB uses 1,024 cubed bytes, so 512 MiB is 0.5 billable GB in this calculation. Persistent disk and object storage use separate meters, with the units and rates shown below.

The per-replica CPU and RAM floor policy is implemented, merged, and deployed, but remains inactive. It does not change current rates or invoices. Enrolling an organization requires separate future authorization after telemetry, billing writers, and migration readiness checks pass.

For an enrolled organization, each measured interval uses the greater of actual usage and the baseline for each dimension. The baseline is 50 millicores (0.05 vCPU) and 128 MiB RAM per running managed application replica. CPU and RAM are calculated independently. The baseline does not add to actual usage.

For two replicas measured for 30 minutes each, CPU coverage is 3,600 replica-seconds. If each uses 0.02 vCPU and 64 MiB RAM, the floor bills 180 CPU core-seconds and 450 GiB-seconds. If each instead uses 0.2 vCPU and 256 MiB RAM, the billable amounts are 720 CPU core-seconds and 900 GiB-seconds. The floor does not add to those actual amounts.

The dimensions stay independent. CPU above its baseline with RAM below its baseline uses actual CPU and the RAM floor. RAM above its baseline with CPU below its baseline uses actual RAM and the CPU floor. A configured CPU or RAM limit can cap only its own baseline. A request does not cap a baseline. The billing constants do not depend on Kubernetes scheduling requests. Changing a request does not change prices.

The policy estimates running time from adjacent measurements. It is not an exact container start or stop clock, so unobserved startup and shutdown time stays unbilled. It does not extend usage across gaps or after the last sample. If an hour has 30 minutes of measured coverage, the floor applies only to those 30 minutes. A stopped replica or a scale-to-zero hour has no replica floor. If evidence or a fresh configured limit is missing for one dimension, that dimension keeps measured actual usage without a floor uplift. The other dimension can still use its floor.

The policy covers managed application replicas only. Database, reserved capacity, connected compute, preview resources, network, storage, build charges, published rates, and runtime credits keep their current rules. Pro remains $50 per month. Its existing runtime credit covers up to $50 of eligible runtime charges. The floor adds no fixed fee. Usage above the credit remains due under the current billing process.

CloudX measures CPU in virtual CPU cores and CPU core-seconds.

Assume a 30-day, 720-hour month. The app averages 0.25 billable vCPU and 512 MiB RAM. PostgreSQL also averages 0.25 billable vCPU and 512 MiB RAM and has 10 GB of provisioned persistent disk. There is one database service fee. The CPU and RAM figures are assumed average usage over the month.

The example covers app and database CPU and RAM, database disk, and one database service fee. It excludes app disk, object storage, egress, build overage, extra services, taxes, and customer infrastructure bills. Calculated costs are rounded to cents.

Each service uses 0.25 vCPU × 720 hours = 180 vCPU-hours, costing $0.74, and 0.5 GB RAM × 720 hours = 360 GB-hours, costing $3.50. App total: $0.74 + $3.50 = $4.24.

Database disk: 10 × 30 × $0.01 = $3.00. Hobby PostgreSQL: $4.24 + $3.00 + $5.00 = $12.24. Pro PostgreSQL: $4.24 + $3.00 + $10.00 = $17.24.

Hobby combined usage: $4.24 + $12.24 = $16.48. Estimated bill: $10.00 plan fee + $6.48 usage above its $10.00 credit = $16.48.

Pro combined usage: $4.24 + $17.24 = $21.48. This fits inside the $50.00 runtime credit. Estimated bill: $50.00, with $28.52 of that month’s credit available for other usage.

At 250 Hobby build minutes, 50 excess minutes × $0.02 = $1.00 in extra build charges. At 550 Pro build minutes, the same 50 excess minutes also add $1.00. Build overage is billed separately from runtime credit.

Ingress is free and egress costs $0.10/GB. For example, 10 GB × $0.10 = $1.00 in egress usage, drawn from runtime credit. Object storage draws from the same credit as compute, persistent disk, and database fees.

Hobby permits 5 object-storage buckets and Pro permits 25. Storage usage is billed at $0.035/GiB-month, prorated hourly, and draws from runtime credit. Bucket counts set the number of buckets you can create; storage charges follow the amount stored.

Connecting an existing Amazon S3, Cloudflare R2, or Backblaze B2 bucket registers that bucket without migrating its objects. Your provider bills its own services separately. The same applies to infrastructure you supply through a connected Linux VPS or Kubernetes cluster.

• Databases and object storage →
• Connected compute limitations →

How does credit affect this example? Hobby uses $16.48: its $10.00 credit covers the first $10.00, leaving $6.48 in additional usage. Pro uses $21.48 within its $50.00 credit, so the plan bill remains $50.00. The remaining $28.52 is available for other usage that month.

What if PostgreSQL needs more RAM? Increasing database RAM from 512 MiB to 1 GiB adds 0.5 GB × 720 hours = 360 GB-hours, costing $3.50. Hobby usage becomes $16.48 + $3.50 = $19.98, leaving $9.98 above its $10.00 credit. Pro usage becomes $21.48 + $3.50 = $24.98, still within its $50.00 credit.

What should I include in a billing question? Send the plan, billing period, resource type, and usage details. Keep credentials and private application data out of the request. Enterprise pricing follows your agreed terms.

How are CPU and RAM billed when my app is idle? The prospective CPU and RAM floors are currently inactive and do not change current invoices. After separate authorization enrolls an organization, eligible measured intervals use the greater of actual usage and a baseline of 50 millicores (0.05 vCPU) for CPU and 128 MiB for RAM per running managed application replica. CPU and RAM are calculated independently; the baseline is not added to actual usage. Configured limits can reduce a baseline, and incomplete evidence can keep actual-only billing. Stopped replicas and scale-to-zero hours have no replica floor.

• Contact billing support →
• Deploy your first app →
• Read the CPU and RAM floor details →