All products 
When an hourly-billed VPS beats a monthly plan
With hourly billing you top up your balance, create a server, and the host charges for every hour the server exists. Delete it after three hours — you pay for three hours. The model comes from the cloud and suits tasks that have a beginning and an end. For a server that runs around the clock for months, it's usually no cheaper than ordinary monthly rental.
Which tasks an hourly VDS is for
- Tests and experiments. Try a new OS version, run a database migration, compare the performance of two configurations.
- Builds and CI. A powerful machine is needed for the duration of the build, not around the clock. For permanent runners see the VPS for CI/CD runners page.
- One-off computations. Video conversion, a large scraping job, load testing your own site.
- Temporary projects. A weekend gaming tournament, a demo environment for a client, a work server for the duration of a trip.
If your goal is simply to get to know a host, look at plans with a trial period: there the trial days are free or nearly free.
How an hourly price becomes a monthly one
A month has about 720–730 hours. Multiply the hourly rate by that number and compare it with the same host's monthly plan. Many hosts cap the charges: if the server ran for the whole month, you pay no more than the monthly price. Others have no such cap, and round-the-clock operation comes out noticeably more expensive. Check this in the plan description before launching.
Two more nuances. The hourly rate sometimes doesn't include a dedicated IPv4, snapshots or backups — they're billed separately. And whatever is left of the minimum top-up after you delete the server stays on the balance; not every host will refund it to your card.
Stopping is not deleting
A common mistake is to shut the server down and assume billing has stopped. With most hosts a stopped machine still occupies disk space and an IP address, and you're charged for them, sometimes at the full rate. For charges to end, the server must be deleted. If you'll need the data later, take a snapshot: storing it is usually cheaper than keeping a stopped machine, and a server comes up from a snapshot in a few minutes.
Automation via API
An hourly plan shows its full potential when the server is created and deleted by a script. Cloud hosts offer an API for this, and some have a Terraform provider. The pipeline spins up a machine, runs the job and deletes it, and you pay for hours of work, not idle time. Turn on spending notifications so a forgotten server doesn't eat your budget.
The hourly model is offered mostly by large clouds, and their payment options can be narrower than those of ordinary hosts. The "Payment" column in the table above shows the methods for each plan; prices are shown in your currency.