Tools

VPS cost calculator

What your VeloxaHost servers cost this month. Each server is charged its size's hourly rate for every hour it runs, and stops being charged once it reaches its size's monthly price for the calendar month.

How long each server runs this calendar month

0 to 744 hours: a 31-day month has 744, a 30-day month 720.

This calendar month

$4.00

for 1 server of Veloxa 1, 200 hours each

  1. 1. At the hourly rate: 200 h × $0.02 = $4.00
  2. 2. Monthly cap for Veloxa 1: $8.00, which a server reaches in running hour 400
  3. 3. One server: the lower of $4.00 and $8.00 = $4.00 (under the cap: every hour is charged in full)
  4. 4. All servers: $4.00 × 1 = $4.00

How the bill is worked out

Once an hour, every server that is running is charged one hour at its size's rate. A stopped server is not charged. The charges add up per server, and when a server's charges for the calendar month reach its size's monthly price, it is not charged again until the next month begins (months are counted in UTC). In the hour that crosses the cap, only the remainder is charged.

So for one calendar month, each server costs the lower of two numbers: its running hours times the hourly rate, or the monthly cap. Several servers each have their own cap, so the bill for several servers of one size is that amount times the number of servers.

bill = servers × min(hours × hourly rate, monthly cap)

Rates and caps

SizevCPU / RAM / diskHourly rateMonthly capCap reached in hour
Veloxa Nano1 / 1 GB / 25 GB$0.01$4.00400
Veloxa 11 / 2 GB / 50 GB$0.02$8.00400
Veloxa 22 / 4 GB / 80 GB$0.03$15.00500
Veloxa 44 / 8 GB / 160 GB$0.05$30.00600
Veloxa 88 / 16 GB / 320 GB$0.09$60.00667

A 31-day month has 744 hours and a 30-day month 720, so a server of any of these sizes left running all month reaches its cap. Veloxa 16 is sold on request through support, so it is not in the calculator.

Worked examples

CaseSizeHours eachServersAt the hourly rateMonthly capBilled
A CI runner, 8 hours on 22 working daysVeloxa Nano1761176 × $0.01 = $1.76$4.00$1.76
Two staging servers for 10 daysVeloxa 12402240 × $0.02 = $4.80$8.002 × $4.80 = $9.60
A production server left on all of a 31-day monthVeloxa 27441744 × $0.03 = $22.32$15.00$15.00
A build server for 670 hoursVeloxa 86701670 × $0.09 = $60.30$60.00$60.00
  • A CI runner, 8 hours on 22 working days: under the cap, so every hour is charged in full.
  • Two staging servers for 10 days: under the cap, so every hour is charged in full.
  • A production server left on all of a 31-day month: capped in running hour 500; the 244 hours after it are not charged.
  • A build server for 670 hours: capped in running hour 667, which is charged only the $0.06 left; the 3 hours after it are not charged.

What the calculator assumes

  • One calendar month. The cap is per server per calendar month (UTC). A server that runs from the 20th of one month to the 10th of the next gets two bills, each with its own cap.
  • Whole running hours. Charges are made once an hour for the servers running at that moment, so enter the hours a server is on.
  • One size all month. If you resize a server, each hour is charged at the size it has at that hour, and the cap becomes the new size's monthly price, counted against what the server has already been charged that month.
  • The server, not the extras. Dedicated IPv4 addresses, object storage and block storage are charged on their own lines, also by the hour up to their own monthly price. A server you delete and create again starts a new count.
  • Billing has to be active. Hourly charges go on a paid subscription: Pay as you go, with a card on file, or a hosting plan you pay for.

The rule in full, with a three-server example bill, is on hourly billed VPS with a monthly cap. The sizes and what each includes are on the VPS hub and pricing. Badges for app READMEs and blog posts are with the other tools.

Ready to deploy?

Start a free trial, or compare plans to match your team's scale.