On this page 7 sections
A prepaid cloud wallet is a credit balance you load up front, that your apps then draw down per minute as they run. Usage-based billing does the opposite: the meter runs first and the invoice arrives after.
Both charge you for what you use. The difference is the order, and the order decides whether a forgotten service can surprise you.
Railway has argued that usage-based pricing is the honest model, because you pay for exactly what you consume and nothing more. That is a fair point. Our counter is that a prepaid wallet charges for exactly what you consume too, and it also bounds the total before anything runs, which a postpaid meter cannot do.
TL;DR
- A prepaid wallet is a loaded balance. Usage draws it down per minute, and at zero your apps pause with their data kept, so the most you can spend is the balance.
- Usage-based (postpaid) billing meters what you run and charges a card after the cycle. It is precise, but the total is unbounded until the invoice lands.
- On Ownkube, unused wallet credit rolls over and never expires. A quiet month carries forward instead of resetting to zero.
- A prepaid wallet still meters real usage under the hood, so an idle app barely draws it down. You get precision and a ceiling.
- A pure usage-based meter still makes sense for spiky, high-scale, or pass-through-billed workloads. We say where below.
What a prepaid cloud wallet actually is
A prepaid wallet is a dollar balance you keep on the platform. You load it (or your plan loads it for you), and every app you run draws it down per minute for the CPU and memory it actually uses. It works like a transit card or a prepaid SIM: the money goes in first, and consumption spends it down.
The mechanics that matter are at the edges. When the balance runs low, you top up. When it reaches zero, your apps pause and your data stays put until you add credit.
No card is charged in the background, so the total can’t run past the balance you chose. The ceiling is the money itself, rather than an alert or a budget you hope holds.
On Ownkube the wallet is the billing model for Ownkube Compute, the managed compute you deploy onto with no cloud account of your own, no config, and no subscription to start.
You can fund the wallet with a top-up from $5, or pick a plan that loads it each month: Personal is $5 a month and loads $5 of credit, Team is $20 a month and loads $20. Usage draws that balance down, and you top up any time from a $5 minimum.
What usage-based (postpaid) billing is, and where it leaks
Usage-based billing meters consumption and charges you after the fact. Railway bills per second for what runs, and most clouds bill per hour or per GB at the end of a cycle. The pitch is precision, and it holds: you are charged for what you used rather than a flat box you half-filled.
The leak is in the timing. Because the spend happens before the bill, three kinds of surprise are built into the model.
The forgotten service
You spin something up for a test, move on, and it keeps metering against your card until the invoice reminds you it existed.
The spike
A busy day or a runaway process meters faster than any alert can reach you, and the overage is already spent by the time you read the email.
No ceiling
A budget cap on a postpaid meter is a notification. The meter can cross it, because the limit is enforced by a promise to email you while a payment method stays on file.
None of this makes usage-based billing dishonest. An honest rate and a bounded total are two different properties, and a postpaid meter only gives you the first.
Why rollover credit that never expires changes the math
The strongest objection to prepaid is that it feels like a loss. If you load $20 and use $12, did you just burn $8? On many prepaid systems, yes, because the credit expires at the cycle boundary. That version of prepaid deserves suspicion.
On Ownkube, unused wallet credit rolls over and never expires. Your plan loads credit each month, usage drains it, and whatever you did not spend stays on your balance while the next month loads on top.
A quiet month leaves money in your account. Over a year of uneven usage the balance evens out, because the light months bank credit that the heavy months draw on.
A postpaid meter has nothing to roll over. You pay for August in September and the slate is blank again. On a prepaid wallet with rollover, a $5 month you barely touched leaves roughly $5 waiting for the month you ship hard. The rate you pay per vCPU is the same either way; underuse just stops costing you.
One caveat: the monthly build-minutes allowance (300 minutes on Personal, 1,500 on Team) resets each month and does not roll over. Only the dollar balance carries forward.
Prepaid vs usage-based billing, side by side
Both bill for real usage. The table covers what happens around that.
| Prepaid wallet (Ownkube) | Usage-based / postpaid (Railway, most clouds) | |
|---|---|---|
| Order of events | Load balance, then usage draws it down | Usage runs, then a card is charged |
| Charges for real usage | Yes, per minute on CPU and memory | Yes, per second or per hour |
| Total spend ceiling | The balance you loaded | Unbounded until the invoice |
| Idle app | Barely draws the wallet down | Metered continuously if the instance exists |
| Unused amount | Rolls over, never expires | Nothing to roll over |
| At zero / non-payment | Apps pause, data kept | Meter keeps running against the card |
| Forgotten service | Draws down the wallet, then stops | Runs up the bill until you notice |
| Best for | Personal software, small teams, bounded budgets | Spiky scale, pass-through billing, pooled org spend |
When a pure usage-based meter still makes sense
A prepaid wallet is the wrong tool for some kinds of spend.
Spiky, high-scale traffic
If your load swings by orders of magnitude and you need to absorb every spike without ever pausing, a postpaid meter that bills the overage fits better than a balance you have to keep ahead of. A prepaid ceiling helps when you want a limit and gets in the way when you never do.
Pass-through or client-billed usage
Agencies and platforms that re-bill consumption to customers often want the raw postpaid meter to reconcile against invoices, rather than a pooled prepaid balance.
Large orgs with central procurement
When finance already runs on monthly postpaid invoices and pooled commitments, a per-project prepaid wallet can be more accounting than it is worth.
Usage-based billing optimizes for never interrupting the workload, and a prepaid wallet optimizes for never being surprised by the bill. Most personal software and small-team apps want the second; some high-scale, re-billed or procurement-heavy setups want the first. Ownkube leads with the wallet because Ownkube Compute is a cloud for personal software.
For how the wallet plays out day to day, see how to keep your cloud bill from surprising you. For the reserved-vs-metered choice inside the wallet, see metered or a flat box: how to choose pricing for each app.
And for where this lands against the field, our comparison of Railway, Render, and Northflank walks through each billing model at the end of the month.
FAQ
Is a prepaid wallet just usage-based billing with extra steps?
Under the hood it meters the same real usage per minute, so the rate works the same way. The extra step is loading the balance first, and that step caps the total at what you loaded, which a postpaid meter cannot do.
Does prepaid credit on Ownkube expire?
No. Unused wallet credit rolls over to the next month and never expires. The dollar balance persists across cycles and each monthly plan load adds on top. The one thing that resets monthly is the build-minutes allowance.
Is prepaid more expensive than paying only for what I use?
No. You still pay per minute for actual CPU and memory usage, so an idle app barely registers. The metered rates are about $18 per vCPU per month and $4.50 per GiB per month.
What happens if I load $20 and only use $12?
The remaining $8 stays on your balance and carries into next month, when your plan loads more on top. Underuse banks credit rather than burning it.
When would usage-based billing be the better fit?
When you have spiky high-scale traffic you never want to pause, when you re-bill consumption to clients and need the raw meter to reconcile, or when a large org already runs on pooled monthly postpaid invoices.
Where Ownkube fits
A prepaid wallet and a usage-based meter both charge for what you use. The wallet adds a ceiling you set on purpose and rollover credit that never expires, so a quiet month carries forward and a forgotten service cannot outrun the balance.
Usage-based billing is the right choice when never interrupting the workload matters more than bounding the bill. For personal software and small teams who would rather draw the line before the spend than reconcile it after, the wallet is the calmer default, and it is the model behind Ownkube Compute. Deploy my first app.