Kamatera pricing explained: real costs and the add-ons

Kamatera's base server is $4 a month for 1 vCPU, 1 GB of RAM, 20 GB of NVMe and 5 TB of traffic, and almost nobody ends up paying exactly $4. The add-ons are published and flat, which is more than most hosts manage, but there are two line items that catch people and one that is genuinely not possible to look up.

This goes through every component of the bill, then prices three servers that look like things people actually run.

The published rates

Kamatera's pricing page states these plainly, and they do not change with volume:

• Base server, $4/month. 1 vCPU at 2667 MHz on the Type A pool, 1 GB RAM, 20 GB NVMe, 5 TB of monthly traffic.
• Additional storage, $0.05 per GB per month. A 100 GB data volume is $5. No tiering, no IOPS charge, no separate provisioned-throughput line — which is the thing anyone arriving from AWS will notice first.
• Additional traffic, $0.01 per GB. Overage past your included allowance. 1 TB over is $10.
• Managed service, $50 or $150 per server per month. Pro covers OS monitoring, firewall and networking, DNS, performance metrics, application installation and 24/7 NOC coverage. Premium is the $150 tier above it.

Everything else — more cores, more memory, a better CPU class — moves the base figure on the configurator, and the total updates as you drag each slider. There is no quote process and no sales call, which for a $4 product should be table stakes but frequently is not.

CPU class is the biggest single lever

The same four cores cost very different amounts depending on which pool they come from, and this is where a build gets expensive without obviously changing on the spec sheet.

• Type A — Availability. The cheapest, and what the $4 plan uses. Shared, best-effort, fine for scratch work.
• Type B — General Purpose. Kamatera's own recommendation for production. Costs more per core than Type A and is the sensible default for anything serving users.
• Type T — Burstable. Priced low for an idle baseline with short bursts allowed. Lean on it continuously and it throttles, so it is a trap for a build server and a bargain for a brochure site.
• Type D — Dedicated. Reserved cores at the top of the range. Worth it for a database under constant load or a CI runner, and wasted on anything that idles.

Picking Type D when Type B would do is the most common way to double a bill for no benefit. Picking Type A for a production database is the most common way to save $6 a month and spend an afternoon on it.

The storage rule that costs money later

A primary disk can be expanded and can never be reduced. If you grow a 20 GB boot volume to 200 GB to get through a migration, that server costs $9 a month more from then until you rebuild it — $0.05 × 180 GB — whether or not the data is still there.

The way around it is architectural rather than clever: keep the boot volume small and put bulk data on a second volume, which can be detached and deleted when you are done with it. It costs the same per GB and it is reversible.

The cost with no rate card: Windows

Kamatera deploys Windows Server and Windows Desktop with licensing handled, and does not publish what the licence adds. The cost is folded into the total the configurator shows once you select a Windows image, so the only honest way to price a Windows box is to build one on screen and read the figure.

That is not a hidden charge — you see the number before you pay anything — but it does mean you cannot compare Windows pricing against another host from a table, and anyone quoting you a precise per-vCPU Windows figure for Kamatera has worked it out from one configuration rather than read it somewhere. Our Windows VPS review covers what a workable Windows build needs in hardware terms, which is the part that actually drives the total.

Hourly against monthly, and the charge people complain about

Every server is provisioned on one cycle or the other, chosen at build time:

• Hourly bills by the minute. Terminate the server and charges stop. Slightly more expensive per hour if the machine runs all month.
• Monthly is cheaper for a server that stays up, and does not prorate on the way out. Delete a monthly server on the 2nd and that month is still billed in full.

The second rule generates most of the billing complaints about Kamatera, and it is in the terms rather than buried. The related one worth internalising: powering a server off does not stop the meter. Kamatera's own FAQ confirms an hourly server keeps accruing while powered down, because the disk image and the public IPv4 address remain reserved. Shutting down the guest OS is not the same action as releasing the resource. Terminate it.

Three realistic builds and what they cost

Read the third row carefully, because it is the one that changes architectures. Managed support is priced per server. A single 4 GB box with Pro management is about $85. The same workload split across a load balancer, two web nodes and a database — the shape our SaaS architecture piece walks through — is four servers, and $200 a month of management before any compute. On Kamatera, managed support rewards consolidation and punishes microservices.

Where this sits against the obvious alternatives

DigitalOcean charges $6 for the memory Kamatera gives you at $4, and bundles managed Postgres, object storage and Kubernetes that Kamatera does not sell at any price. Hetzner's CX23 is €5.49 for 2 vCPU, 4 GB and 20 TB of traffic, which beats anything here on hardware per unit of money — though Hetzner's own June 2026 price notice moved its dedicated CCX13 to €42.99, which is where Kamatera's Type D now looks good by comparison.

The full arguments are in Kamatera vs DigitalOcean and Kamatera vs Hetzner.

Pricing a build without paying for it

The 30-day trial covers one server configured up to $100, plus 1 TB of traffic, which is enough to build the thing you are actually costing and watch it under load rather than reasoning about a spec sheet. Two details to know going in: a fully refundable $10 deposit is sometimes requested in place of card verification, and the allowance covers one server rather than a cluster. Our trial guide has the rest, and the full review is the wider picture.