Hourly vs monthly VPS billing

Updated 2026-10-30

Hourly VPS billing charges for each hour a server exists, so short-lived servers cost cents; monthly billing charges a fixed amount per month whether you use it or not. Hourly billing with a monthly cap gives you both: you never pay more than the monthly price, and you pay less when you delete servers early.

This guide explains the models, shows real arithmetic and points out the details that change the bill.

The four common models

1. Monthly or yearly contract

You pay a fixed price for a fixed term, often in advance. Cancelling early may not refund anything. Some providers give a discount for longer terms.

• Good for: servers that will certainly run for the whole term, when there is a real discount.
• Bad for: testing, temporary work, projects that might change.

2. Monthly without a term

You pay month by month and can cancel any time, but each started month is charged in full.

3. Hourly without a cap

Each hour is billed at a rate. A month of use costs rate × hours in that month, which varies between 672 and 744 hours.

4. Hourly with a monthly cap

Each hour is billed, but the total per resource per month never goes above the monthly price. This is the model most modern cloud platforms use, and the one Wolkra uses.

How the cap works

Every started hour adds the hourly rate to the bill for that resource. Once the total reaches the monthly price, the charge stops growing for the rest of the month.

Example with a plan at €3.49 a month (the smallest Wolkra plan, s0):

The exact hourly rate is shown in the console when you create a server, and on the pricing page.

Per started hour

"Per started hour" means a partly used hour counts as a full hour. A server that exists for 50 minutes is billed for 1 hour; 1 hour and 5 minutes is billed for 2. This keeps the bill simple and the difference is tiny.

When hourly billing saves real money

Testing and evaluation

Try a plan, run a benchmark, check whether your app fits in 2 GB, then delete it. With hourly billing that costs less than a coffee. With a monthly contract it costs a month.

Temporary capacity

Spin up extra servers for a launch, a sale, a migration or a load test, and remove them afterwards.

CI, builds and batch jobs

Create a powerful server for a few hours to build, render or process data, then delete it. You pay for a CPU-optimised machine only while it works. See CI runners.

Development environments

Create a fresh server for each branch or each developer, and delete it when done (development environments).

Mistakes

Picked a plan that is too big? Resize or replace it after an hour, not after a year.

What still costs money

Billing follows resources, not activity. Watch for these:

• Stopped servers usually still cost money, because their disk and capacity stay reserved. Deleting them stops the charge.
• Snapshots are billed per GB while they exist. Old ones add up.
• Volumes are billed per GB per month whether attached or not.
• IPv4 addresses, floating IPs and load balancers are billed while they exist.
• Backups cost a percentage of the server price (20% on Wolkra) while enabled.

A monthly look at the resources list catches forgotten items.

To keep a configuration without paying for a running server, take a snapshot, delete the server, and create a new server from the snapshot later. You then pay only for the snapshot storage.

Prepaid balance vs invoice

Hourly billing comes in two flavours of payment:

• Postpaid: usage is charged to your card at the end of the month. A runaway script can create a large bill.
• Prepaid: you add credit first and usage is deducted from it. Spending cannot go beyond the balance.

Wolkra uses a prepaid balance. You top up by card through Stripe or with crypto (USDT TRC-20 or TRX on TRON), see payment methods. Optional automatic top-up by card keeps the balance from running low. Low-balance emails arrive before anything stops; when the balance runs out there is a grace period, then servers are stopped, and they are deleted only after a final notice. The details are in billing and balance.

Doing the comparison yourself

To compare a monthly contract with hourly billing:

1. Estimate how many hours each server will really exist this month.
2. Multiply by the hourly rate, cap at the monthly price.
3. Add extras: IPv4, backups, volumes, snapshots, traffic.
4. Compare with the contract price including its extras and any traffic fees.

A worked example for a project that runs one permanent server and a test server for 40 hours:

With a yearly contract, the test server alone might cost a full month or more.

Traffic deserves a separate line. A cheap plan with an allowance and per-GB overage can end up more expensive than a slightly dearer plan with unmetered bandwidth.

Tips to keep the bill low

• Delete what you don't use, instead of stopping it.
• Label servers (env=test, owner=anna) so you can see who owns what.
• Use snapshots instead of idle servers to keep configurations.
• Start small and resize up; disks can grow but never shrink, so don't oversize the disk.
• Use private networks and a NAT gateway so internal servers don't each need a paid IPv4.

Summary

Hourly billing with a monthly cap is never more expensive than the monthly price and often much cheaper. Combine it with a prepaid balance and you also get a hard spending ceiling. Contracts only make sense with a real discount and a server that will certainly run the whole term. Read more on hourly billing VPS or see the prices.