Kedge bills per second for the resources an app actually consumes while it runs.

resource limits and billing

The cpus, memory, and volume.size settings are optional guardrails. They set an upper limit on what an app may consume; they do not reserve capacity or create a fixed-price instance. Billing measures runtime use beneath those limits:

• CPU: time your code is scheduled on a core. Waiting for I/O accrues nothing.
• Memory: pages touched recently, not the configured limit. Resident memory is used when working-set measurement is unavailable.
• Egress: bytes leaving the app.
• Storage: bytes stored. Sparse databases and volumes bill written data, not their logical limit.

For example, an app limited to 4 vCPUs, 8 GiB of memory, and 100 GiB of storage but averaging 0.25 vCPU, a 400 MiB working set, and 2 GiB stored is billed for the latter amounts.

A scaled-to-zero app has no running CPU or memory usage, so it accrues only its stored-data cost.

rates

A vCPU-month is 730 vCPU-hours. Billing is per second; the monthly figure is a reference scale.

the free tier

Every account includes $5 of monthly usage, consumed before paid credit.

credits and enforcement

Usage draws down your credit balance. The billing page shows the balance, trailing-hour and trailing-day run rate, 30-day burn-down, and transaction ledger.

Kedge notifies you below $1 and suspends the account at zero; apps stop and data remains. During beta, email support@kedge.dev for more credit.

Check the same live summary from a shell:

kedge billing

For automation, use the generated account REST operations.