What would your apps cost on Kubernetes vs plain servers?
Set how many apps you run, how much memory each needs, and how many servers you want at minimum. The calculator works out how many 4 GB machines that takes, then prices the same machines three ways.
- Memory your apps need
- 1.5 GB
- 4 GB servers needed (3 GB usable each)
- 1
- Kubernetes nodes (2 minimum)
- 2
- Amazon EKS$163/mo
$73 control plane, t3.medium nodes ($30.37) with a public IPv4 ($3.65), one shared Application Load Balancer ($22.27). EBS disks not counted.
- DigitalOcean Kubernetes$60/mo
Free control plane, 4 GB nodes at $24, one $12 load balancer. High-availability control plane is $40 more.
- Your own server + Ployz$7/mo
Hetzner CX23 ($6.49 + about $0.60 IPv4, Europe) per server. Ployz is free on any number of servers. No load balancer to rent.
The "3 GB usable" figure is my assumption, not a measurement, for a 4 GB machine once the operating system and system containers take their share. I used it for all three rows so the comparison stays fair. Kubernetes nodes also run their own agents, so if anything the real Kubernetes node count is a bit higher.
With the same assumptions (a two-node minimum on Kubernetes, one shared load balancer, AWS at 730 hours a month), here's how the bill grows:
| Setup | Amazon EKS | DigitalOcean Kubernetes | Hetzner + Ployz |
|---|---|---|---|
| 3 apps of 512 MB, 1 server (2 nodes on Kubernetes) | $163 | $60 | $7 |
| 10 apps, 3 servers | $197 | $84 | $21 |
| 30 apps, 8 servers | $367 | $204 | $57 |
The Hetzner column is CX23 servers (2 vCPU, 4 GB RAM, 40 GB) at $6.49 plus about $0.60 for the IPv4 address, from Hetzner's 15 June 2026 price adjustment. Ployz is free on any number of servers, so the column is the server bill.
How the EKS line for three apps adds up: $73 control plane, plus two t3.medium nodes at $30.37 each, plus $3.65 per node for the public IPv4, plus $16.43 for the ALB's hours and $5.84 for one LCU. EBS disks, data transfer and NAT gateways are extra, so the real bill is higher.
The CX23 is Europe only (Germany and Finland). For a US datacenter, Netcup's VPS 500 (2 vCPU, 4 GB RAM, 64 GB SSD) is €8.26 a month incl. VAT on a 12-month term and has a Manassas location (netcup VPS plans); a $24 DigitalOcean Droplet also works.
Two things stand out. DigitalOcean is the fair managed option for a small team, because its free control plane leaves the gap as mostly the second node and the load balancer. And EKS's $73 control plane alone costs more than ten Hetzner servers. If you're on AWS already and want containers without the cluster fee, AWS Fargate is the other route to price.
What does managed Kubernetes cost?
EKS charges $0.10 per cluster per hour, about $73 a month, before any servers. GKE charges the same rate but gives a monthly credit that covers one cluster. DigitalOcean's control plane is free. On all three you pay for the worker machines on top.
| Provider | Control plane | Nodes | Load balancer | Source |
|---|---|---|---|---|
| Amazon EKS | $0.10/cluster/hour (about $73/month); $0.60/hour on extended support | EC2 prices, e.g. t3.medium (2 vCPU, 4 GiB) at $0.0416/hour, about $30.37/month | ALB: $0.0225/hour plus $0.008 per LCU-hour | EKS pricing, EC2 on-demand, ELB pricing |
| Google GKE | $0.10/cluster/hour; $74.40/month free tier credit per billing account covers one zonal or Autopilot cluster | Compute Engine prices | Billed separately | GKE pricing |
| DigitalOcean Kubernetes | Free; high-availability control plane $40/month | From $12/month (1 vCPU, 2 GB); 4 GB nodes are $24 | $12/month | DOKS pricing, Droplet pricing |
The lines people miss:
- Public IPv4 on AWS is $0.005 an hour per address, in use or idle (VPC pricing). That's $3.65 a month for each node with a public address.
- EKS extended support. Each Kubernetes version gets 14 months of standard support on EKS, then 12 months of extended support, which is on by default (EKS versions). It raises the control plane to $0.60 an hour, about $438 a month for one cluster if you fall behind on upgrades.
- GKE's free tier covers one cluster. Google's own example bills every cluster hour past the credit at the full rate (GKE pricing). Regional clusters, the highly available kind, aren't covered by the credit at all.
- DigitalOcean recommends two nodes. Its pricing page says "We recommend using a minimum of two nodes to prevent downtime during upgrades or maintenance." So the real floor is two nodes plus a load balancer, $36 a month with the cheapest node.
GKE isn't in the calculator, because I couldn't confirm the per-hour Compute Engine rate on Google's page. With the free tier its control plane can cost nothing for one cluster, so its bill comes down to nodes and load balancers, like DigitalOcean's.
Moving a few apps to your own servers
You can wire up Docker, the proxy and the private network yourself, or use a self-hosted platform. Coolify and Dokku are the popular ones, and PaaS pricing compares them with hosted platforms on cost. I built Ployz because I didn't want a three-server minimum to get off one server.
ployz up --server root@your-server
That installs Ployz and deploys the current directory. Add a second server and it joins the same private network. Every server serves https itself. There's no load balancer to rent.
Claude Code, Codex or Cursor runs it through ployz mcp or the CLI with --json. Every deploy, restart or delete your agent asks for waits for you to approve.
Run your apps on your own servers with Ployz, free on any number of servers.