Active-CPU Billing
Active-CPU billing meters the CPU your app actually uses, not the CPU capacity it’s allowed to use. If your app sits idle most of the time and only spikes under real traffic, the idle seconds barely register on the CPU line of your bill.
Ownkube meters active CPU per minute, counted only while your app is running work, up to the CPU limit you configured. A deployment provisioned for 1 vCPU but averaging 5% utilization is billed close to that 5%, not the full vCPU. This differs from a fixed-size instance tier, where you pay the same price whether the CPU is busy or sitting idle. Usage draws straight from your prepaid wallet.
Active-CPU billing applies to metered deployments; a reserved box bills its flat rate regardless of use. It pairs with working-set memory metering, the other half of the usage-based rate: CPU tends toward zero for an idle app, while memory keeps billing as long as the app holds it in memory. Scale to zero goes further, removing even the idle memory cost once an app has had no traffic for a while.