Hourly Billed VPS with a Monthly Cap
How VeloxaHost bills a VPS: by the hour while it runs, capped per server at its size's monthly price each calendar month. With a worked example bill.
Every VeloxaHost VPS size has two prices: an hourly rate and a monthly cap. You pay the hourly rate for each hour a server runs, and in any calendar month a server never costs more than its size's monthly price. A server you run for a weekend costs a weekend. A server you leave on all month costs the monthly price, not 744 hours at the hourly rate.
How the bill is worked out
Once an hour, each server that is running is charged one hour at its size's rate. A stopped server is not charged. The hours add up per server, and when one server's charges for the month reach its size's monthly price, that server is not charged again until the next calendar month (UTC) begins.
| Size | vCPU | RAM | Disk | Per hour | Monthly cap |
|---|---|---|---|---|---|
| Veloxa Nano | 1 | 1 GB | 25 GB | $0.01 | $4 |
| Veloxa 1 | 1 | 2 GB | 50 GB | $0.02 | $8 |
| Veloxa 2 | 2 | 4 GB | 80 GB | $0.03 | $15 |
| Veloxa 4 | 4 | 8 GB | 160 GB | $0.05 | $30 |
| Veloxa 8 | 8 | 16 GB | 320 GB | $0.09 | $60 |
| Veloxa 16 | 16 | 32 GB | 640 GB | $0.17 | $120 |
The cap is per server, not per account. Two servers each have their own cap, and a server you delete and create again starts a new count. If you change a server's size during the month, each hour is charged at the size it has at that hour, and the cap is the current size's monthly price, counted against everything that server has been charged so far this month.
When each size reaches its cap
| Size | Hourly rate | Monthly cap | Cap reached in hour |
|---|---|---|---|
| Veloxa Nano | $0.01 | $4 | 400 |
| Veloxa 1 | $0.02 | $8 | 400 |
| Veloxa 2 | $0.03 | $15 | 500 |
| Veloxa 4 | $0.05 | $30 | 600 |
| Veloxa 8 | $0.09 | $60 | 667 |
| Veloxa 16 | $0.17 | $120 | 706 |
A 31-day month has 744 hours and a 30-day month 720, so every size left running all month reaches its cap. February is the exception for the largest size: 672 hours of Veloxa 16 at $0.17 is $114.24, under its $120 cap. In the hour where a cap is crossed, only the remainder is charged: Veloxa 8 is charged $59.94 for its first 666 hours, then $0.06 in hour 667.
Worked example bill
A small team in a 31-day month runs a production server all month, a load-test server for three days, and a CI runner that is started for eight hours on each of 22 working days and stopped overnight.
| Server | Size | Hours running | Hourly rate | At the hourly rate | Monthly cap | Billed |
|---|---|---|---|---|---|---|
| app-prod | Veloxa 2 | 744 | $0.03 | $22.32 | $15 | $15.00 |
| load-test | Veloxa 4 | 72 | $0.05 | $3.60 | $30 | $3.60 |
| ci-runner | Veloxa Nano | 176 | $0.01 | $1.76 | $4 | $1.76 |
| Total | $20.36 |
The production server hit its cap in hour 500 and ran the remaining 244 hours at no charge. The other two never reached theirs, so they cost exactly their hours. On a flat monthly price, the same three servers would cost $15 + $30 + $4 = $49.
What is included
- Root access to a system container on Ubuntu 24.04 or another offered image, with Docker able to run inside.
- A block of ports on the region's shared IPv4 address, 10 by default, with SSH on the first port. A dedicated IPv4 address is a paid add-on with limited availability.
- Browser terminal and serial console, which work even when your firewall blocks SSH, and a file manager.
- Snapshots and backups. Snapshots are not charged; Pay as you go accounts can hold 30. Backups run every 6 or 12 hours, daily or weekly, keeping 1 to 10.
- Firewall rules per server, and live CPU and memory resizing.
- No separate charge today for bandwidth, snapshots or backups. Your plan's quotas are in the console under Settings, Usage.
Limits
- Billing has to be active. Hourly charges go on a paid subscription: Pay as you go ($0 a month plus the hours your servers run, with a card on file) or a hosting plan you pay for. The free trial does not cover servers with a VPS size.
- Running means charged. A server that is idle but running is still charged by the hour. Stop it to stop the charges.
- Disk is set when the server is created. Plan the disk you need up front.
- Veloxa 16 is on request. Self-serve sizes go up to Veloxa 8; ask support for the larger one.
- One region. Servers run in US East, in the Washington, DC area. There are no private networks, floating IPs or load balancers there yet, and no public IPv6.
FAQ
Is a stopped server charged?
No. Only running servers are charged. A stopped server keeps its disk, and starting it again resumes hourly charges.
Does the cap reset if I resize a server?
No. The cap is counted per server per calendar month. After a resize, the cap is the new size's monthly price, minus what that server has already been charged this month.
What happens when a new month starts?
Each server's count starts again at zero on the first day of the calendar month (UTC), and hourly charges resume until the server reaches its cap again.
Are add-ons billed the same way?
Dedicated IPv4 addresses, object storage and block storage are also charged by the hour while you hold them, and stop at their monthly price each month. Each is its own line on the invoice; the console shows the current prices.
How am I invoiced?
Hourly charges are added to your subscription and collected by Stripe with the card on file. Your invoices are listed on the Billing page of the console.
Ready to deploy?
Start a free trial, or compare plans to match your team's scale.