Working-Set Memory
Working-set memory is the amount of memory your application is actually holding at a given moment, as opposed to the memory limit you configured for it. Ownkube meters memory usage on this working set, per minute, for as long as your app runs.
A deployment might be configured with a 512 MiB memory limit as a ceiling, but if it only ever holds 100 MiB of live data and process state, that 100 MiB working set is what gets billed, not the 512 MiB limit. This mirrors active-CPU billing: you’re charged for what the app is doing, not what it was allowed to do. Usage draws from your prepaid wallet.
Unlike active CPU, working-set memory doesn’t drop to zero when idle. Memory is billed for as long as your process keeps data resident, whether or not it’s handling requests right now, which is why always-on services and databases carry a higher steady memory bill than bursty web apps. Workloads that want a flat, predictable price regardless of working set can opt into a reserved box instead.