Engineering notes

VPS spend caps explained: alerts, hard caps and what happens at the limit

What a spend cap on an hourly VPS is, why metered billing needs one, how budget alerts differ from hard caps, and what a cap can and cannot do once you reach it.

By Vozora · Published

A spend cap is a ceiling on how much an account can run up in a billing period. On a VPS billed by the hour, it is the thing that stands between a forgotten test server, a runaway script or a leaked API key and an invoice you did not plan for.

Caps come in two broad kinds. An alert tells you that spend has crossed a line and leaves everything running. A hard cap makes the provider act when spend reaches the limit. Most useful setups combine both: alerts on the way up, a cap at the top. Neither one is a guarantee, and the reasons why are worth knowing before you rely on either.

Why hourly billing needs a ceiling

A fixed monthly plan has a ceiling built in: the price. Metered billing does not. You pay for the time a server exists, which is exactly what makes it good for short jobs and bad for forgetting things.

The common ways a metered bill grows without anyone deciding it should:

  • The forgotten test box. You spin up a server to try a config change, it works, you move on. It keeps billing until someone deletes it.
  • The powered-off server. Many providers bill for provisioned time, not running time. On Vozora, usage charges continue while a server remains provisioned, including while it is powered off. Shutting a server down does not stop the meter. Deleting it does.
  • The loop. A deploy script or an automation tool that creates servers and fails before it cleans up. Run it a few times while debugging and you have a small fleet.
  • The leaked key. An API token with permission to create servers, pasted into a public repository or a CI log. Whoever finds it gets to spend your money.

The monthly figure on a pricing page does not protect you from any of these. On Vozora the monthly figures shown for hourly servers are estimates for a server kept for a 730-hour month, not fixed subscriptions and not caps. Ten forgotten servers cost ten times the estimate.

Alerts and hard caps are different tools

A budget alert is a notification. Spend crosses a percentage of a figure, and you get told. Nothing is stopped and nothing is refused. Alerts are cheap to have and easy to ignore, which is their main weakness: an alert that lands in an inbox nobody reads at 3am on a Saturday has not capped anything.

A hard cap is an enforcement point. When spend reaches it, the provider does something. What that something is varies, and the details matter more than the name. Common responses include:

  • refusing to create or start new servers until the cap is raised or the period resets
  • stopping or powering off running servers
  • suspending the account

Each of those limits future damage without destroying anything. None of them, on its own, necessarily stops the bill.

What happens at the cap

This is the part providers are least specific about, and the part you most need to understand.

Caps are checked, not continuous. Billing systems evaluate spend periodically. Between one check and the next, usage keeps accruing, so spend can pass the cap before anything acts on it. The overshoot is usually small, but it is not zero.

Stopping a server may not stop its charges. If a provider bills for provisioned time, including powered-off time, then a cap that powers servers off has limited new work, not ended the meter. The only thing that ends future usage charges on that kind of billing is deleting the server.

Nobody sensible deletes at the cap. Deleting a customer's servers because a billing threshold was reached would destroy data to save money, and most people would rather pay. So caps stop short of deletion, and that means a cap is a brake rather than a wall.

A cap is a control a provider offers in good faith, not a guarantee that spend can never exceed it. Treat any cap as a safety net that catches the large, fast mistakes, not as a promise about the final number on an invoice.

Questions to ask any provider

Before relying on a spend cap, find out:

  1. Is it an alert, a hard cap, or both? A setting called "budget" is often alert-only.
  2. At what percentages do alerts fire, and where do they go? An alert is only as good as the inbox it lands in.
  3. What happens at 100 percent? Are new servers refused, running ones stopped, or the account suspended?
  4. Does a stopped server still bill? If powered-off time is charged, a stop at the cap does not end charges.
  5. What period does the cap cover? Usually the billing period, which may not match the calendar month.
  6. How do you release it? Raising the cap, waiting for the period to roll over, or contacting support. And whether servers restart by themselves afterwards or wait for you.

If the answers are not in the documentation, the cap is harder to plan around than it looks.

How Vozora limits spend: prepaid credit

Vozora does not use spend caps. Hourly usage is paid from credit you add in advance, so there is no invoice at the end of the month for usage you did not plan for. The most an account can run past its credit is one day of usage, taken from the next top-up.

Charges are by provisioned time and continue while a server exists, including while it is powered off. Deleting a server ends them. We email you when your credit is running low. If it runs out, your servers keep running for 24 hours, are then stopped, and are deleted 7 days later if no credit is added, so top up in time or keep backups elsewhere. The billing guide covers credit, usage and what happens when it runs out.

Habits that do more than any cap

A cap catches mistakes. These stop you making them:

  • Delete, do not power off, anything you are finished with. Save the data first. Deletion is the only action that ends future charges on provisioned-time billing.
  • Read an early alert as a question, not a formality. A spend alert in the first week of a billing period, or a low-credit email sooner than you expected, means something is running that you did not plan for.
  • Scope API tokens tightly and keep them out of repositories and CI logs. A token that can create servers is a token that can spend money.
  • Make automation clean up after itself on failure, not just on success. A script that exits halfway through leaves servers behind.
  • Check the list of running servers when a project ends, not when the invoice arrives.

If you are running your own services on a server, cost control is one step of several in our self-hosting on a VPS guide, alongside hardening, backups and monitoring.

Metered billing is the right model for short-lived and bursty work. It just needs a ceiling and the habit of deleting what you no longer use. Current rates for every size are on the Vozora pricing page.

© 2026 Vozora. A trading name of Bankside Technology Ltd, registered in England and Wales, company no. 17253446. Registered office: First Floor, Swan Buildings, 20 Swan Street, Manchester, England, M4 5JW.