TL;DR: For most small teams, the best Kubernetes alternative is one server with Docker Compose or a self-hosted PaaS, at about $7 a month for three small apps. Pick by how many servers you need and whether something has to fail over without you.
- Pick Docker Compose if one server runs your apps and a database. Most small teams never outgrow it.
- Pick Ployz if your coding agent runs your servers, or you've outgrown one server and want two or three on a private network with no cluster to run.
- Pick Docker Swarm or K3s if an app must survive losing a server without anyone acting. Both need three servers, about $21 a month.
- Pick Fly.io, Cloud Run or Fargate if you want autoscaling and no servers to patch. Three always-on apps cost $11 to $145.
- Pick Nomad if you run containers, binaries and batch jobs together and have three or more people to own it.
- Pick Kamal if you want a config file and zero-downtime deploys over SSH, with nothing else on the server.
A Kubernetes alternative is any way to run containers in production without operating a Kubernetes cluster: a single server, a lighter orchestrator, a deploy tool, a managed container service or a self-hosted PaaS. For a small team the choice comes down to server count and what happens when a server dies.
Which Kubernetes alternative should a small team pick?
One server: Docker Compose or a self-hosted PaaS on top of it. Two to five servers with replicas, where a person can deal with a dead server: Ployz, Kamal or Swarm. Automatic failover on servers you rent: Swarm or K3s with three nodes. Autoscaling with no servers at all: Cloud Run, Fargate or Fly.io.
| Your situation | Servers | Team | Autoscaling or automatic failover? | Pick |
|---|---|---|---|---|
| A few apps, one database, steady traffic | 1 | 1–3 | No | Docker Compose, or a self-hosted PaaS (Ployz, Coolify, Dokploy, Dokku) on the same server |
| Outgrew one server, want replicas on two or three | 2–5 | 1–5 | No, a person handles a dead server | Ployz, Kamal plus a load balancer, or Swarm |
| Must survive losing a server without anyone acting | 3+ | 2–10 | Failover yes, autoscaling no | Docker Swarm with 3 managers, or K3s HA |
| Spiky traffic, scale to zero, no servers to patch | 0 | Any | Yes | Cloud Run, ECS Fargate or Fly.io |
| Team already knows Kubernetes, wants Helm and operators | 3+ | 3–10 | Yes | K3s, or managed Kubernetes |
| Containers plus plain binaries, batch jobs, VMs | 3+ servers + clients | 3–10 | Failover yes | Nomad, after reading its license |
What does each option cost for three small apps?
For three always-on apps with about 512 MB each, the server options cost $7 to $21 a month (about $14 for Ployz on two servers), Fly.io about $11, ECS Fargate about $43 with a load balancer, and Cloud Run about $145 on instance-based billing. The gap comes from cluster minimums on self-hosted tools and per-second compute prices on managed services.
| Option | What you pay for | Monthly cost | Source |
|---|---|---|---|
| Docker Compose on one server | 1 Hetzner CX23 (2 vCPU, 4 GB) + IPv4 | about $7 | Hetzner price adjustment |
| Docker Swarm, 3 managers | 3 CX23, managers also run apps | about $21 | Swarm admin guide |
| K3s HA, embedded etcd | 3 CX23, servers also run apps | about $21 | K3s HA docs |
| Fly.io | 3 shared-cpu-1x Machines at 512 MB ($3.69 each, Ashburn) | about $11 | Fly.io pricing |
| ECS on Fargate | 3 tasks at 0.25 vCPU / 0.5 GB ($9.01 each) + an ALB from $16.43 | about $43 + LCUs | Fargate pricing, ELB pricing |
| Cloud Run, instance-based | 3 instances at 1 vCPU / 0.5 GiB, minus the free tier | about $145 | Cloud Run pricing |
| Your own servers + Ployz | 2 CX23 + IPv4; Ployz is free on any number of servers | about $14 | Hetzner price adjustment |
How I got the numbers:
- Hetzner: a CX23 (2 vCPU, 4 GB) is $6.49 a month plus about $0.60 for IPv4, so about $7.09, after the 15 June 2026 price rise. The CX line is in Germany and Finland only. In the US, Netcup's VPS 500 (2 vCPU, 4 GB, 64 GB) is €8.26 a month incl. VAT on a 12-month term, about €1 more in its Manassas datacenter (Netcup VPS).
- Fargate: $0.000011244 per vCPU-second and $0.000001235 per GB-second for Linux on x86 in N. Virginia, which is $0.0405 per vCPU-hour and $0.0044 per GB-hour. An Application Load Balancer is $0.0225 an hour plus $0.008 per LCU-hour. Public IPv4 and data transfer come on top.
- Cloud Run: instance-based billing is $0.000018 per vCPU-second and $0.000002 per GiB-second in us-central1, with 240,000 vCPU-seconds and 450,000 GiB-seconds free each month. One 1 vCPU instance running all month is about $47 of CPU. Request-based billing, where idle instances cost nothing, is $0.000024 per vCPU-second while active.
- Fly.io: the 256 MB preset is $2.19 and extra RAM is $6 per GB-month, so 512 MB is $3.69 in Ashburn. Machines bill by the second while they run.
The Swarm and K3s rows assume your apps run on the three manager or server nodes, which both allow. A single-node Swarm or K3s costs the same $7 as Compose, but without failover.
Why are companies quitting Kubernetes?
Mostly because the cluster becomes a second product to maintain. Kubernetes supports only its three newest minor versions, each for about a year, so every cluster needs a minor upgrade every few months. Add-ons get retired too, like Ingress NGINX in March 2026. For a team running a handful of apps, I think those hours cost more than the servers.
The three newest versions today are 1.37, 1.36 and 1.35, and 1.34's patches end on 27 October 2026 (Kubernetes releases). A cluster set up a year ago is already on the edge of support.
Ingress NGINX shows the second cost. A lot of tutorials install it first, and the Kubernetes project says that after March 2026 "there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities" (Kubernetes blog). Existing installs keep working, but someone now has a migration to plan.
Docker Compose on one server
For most small teams, one server is enough. Docker Compose and a reverse proxy like Caddy run several apps and a database, with HTTPS, for about $7 a month in Europe.
- Where it wins: price, and one machine you can SSH into and understand.
- Where it falls short: no failover and no scheduler. If the server dies, you're down until you restore it somewhere else. The ways to take a Compose app past one server are in Docker Compose across multiple servers.
Everything I run sits on one dedicated server at €80 a month, which is more than I ever ran on Railway when I paid $500+ a month there. What the hosted platforms charge for the same apps is in PaaS pricing.
Docker Swarm
Swarm mode is built into Docker Engine and still maintained, and it's the simplest way to get automatic failover on servers you rent. Mirantis says Swarm "will be fully supported through at least 2030" in its Mirantis Kubernetes Engine 3 (July 2025 post).
Two things get mixed up. Docker's docs say "Docker Swarm mode is built into the Docker Engine", and warn not to confuse it "with Docker Classic Swarm which is no longer actively developed" (Docker docs). Swarm mode is what you get with docker swarm init today. In the market, Kubernetes won, which is why Swarm has fewer tutorials, integrations and hires.
| Docker Swarm | Kubernetes (K3s) | |
|---|---|---|
| Install | Built into Docker Engine | One binary for K3s; more parts for upstream |
| Config format | Compose files (docker stack deploy) | Kubernetes manifests, Helm charts |
| Servers for HA | 3 managers (Docker docs) | 3 server nodes (K3s docs) |
| Minimum per node | No separate control plane process | 2 cores and 2 GB for a K3s server node (K3s docs) |
| Autoscaling | No built-in autoscaler | Horizontal Pod Autoscaler |
| Ecosystem | Small | Very large |
The quorum maths is the same for both. In Docker's table, 3 managers survive 1 failure and 5 survive 2, and "an odd number of managers is recommended, because the next even number does not make the quorum easier to keep" (admin guide). Two managers is worse than one.
Dokploy uses Swarm when you add servers (Dokploy cluster docs). Coolify went the other way: its docs mark Swarm support "experimental and deprecated", set for removal in Coolify v5 (Coolify docs).
Where it falls short: a small ecosystem and no built-in autoscaler.
HashiCorp Nomad
Nomad is a single binary that schedules containers, plain executables and VMs, and it's simpler to run than Kubernetes. Since August 2023, new releases are under the Business Source License 1.1 instead of MPL 2.0 (announcement).
The license file names IBM as the licensor and covers "Nomad Version 1.7.0 or later". It allows production use "provided Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis in order to compete with IBM Corp's paid version(s)". Each release converts to MPL 2.0 four years after it's published. For running your own apps, the license doesn't stop you.
Where it falls short: the sizing. HashiCorp's production requirements say "usually running 3-5 servers in a region is recommended", with "4-8+ cores, 16-32 GB+ of memory" each, and your apps run on separate client nodes. I think Nomad fits mixed workloads with three or more owners. For three web apps, it's more cluster than you need.
K3s
K3s is Kubernetes, packaged small: a certified distribution in one binary, with an ingress controller, a load balancer and local storage included. It's the cheapest way to get real Kubernetes on servers you rent.
A server node needs 2 cores and 2 GB, an agent 1 core and 512 MB (K3s requirements). High availability with embedded etcd needs "three or more server nodes", an odd number (K3s HA docs), so about $21 a month on three $7 servers.
Where it falls short: it doesn't remove Kubernetes' upgrades, manifests or concepts. Your team still owns certificates, backups and an upgrade every few months. Pick it if your team already knows Kubernetes or wants Helm charts and operators.
Kamal
Kamal is 37signals' MIT-licensed deploy tool. You list server IPs in a config file, and it builds your image and deploys it over SSH with zero downtime, using kamal-proxy on each server (Kamal README). There's no cluster and no scheduler.
The proxy "runs on ports 80 and 443 and forwards requests to the application container" on its own server. Where it falls short: its automatic Let's Encrypt certificates require "that we are deploying to one server". With more web servers, you bring your own certificates (Kamal proxy docs) and put a load balancer or DNS in front.
Fly.io, Cloud Run and ECS Fargate
Managed container services run your images with no cluster or servers to manage, and Cloud Run and Fargate can autoscale. The trade is price at steady load.
- Fly.io is the cheapest for small always-on Machines, $2.19 a month for 256 MB in Ashburn (Fly.io pricing). Volumes are $0.15 per GB-month (Fly.io docs).
- ECS itself is free: "There is no additional charge for Amazon ECS orchestration" (ECS pricing). You pay for Fargate or EC2, plus the load balancer, which on a small setup can cost more than the tasks.
- Cloud Run shines on request-based billing for spiky traffic, where idle time costs nothing. Keep instances warm all month and it's the most expensive option here.
If you're moving off a PaaS, I compared those in Vercel alternatives and priced Render and Railway separately.
Self-hosted PaaS
A self-hosted PaaS gives you git push deploys, HTTPS and one-click databases on a server you rent, with no Kubernetes. For most small teams, it replaces Kubernetes entirely. The tools differ most on more than one server.
| Tool | One server | More than one server | Source |
|---|---|---|---|
| Dokku | Default docker-local scheduler | Optional k3s or Nomad schedulers | Dokku schedulers |
| Dokploy | Yes | Docker Swarm, with Traefik routing to chosen servers | Dokploy cluster docs |
| Coolify | Yes | Same app on several servers; "configure a cloud load balancer or another external traffic layer in front"; apps with persistent storage can't go multi-server | Coolify multiple servers |
| Ployz | Yes | WireGuard network between servers, a Caddy load balancer on every server, up to 50 replicas per service | Ployz docs |
- Dokku is single-server by default.
- Dokploy spreads apps with Swarm. Its dashboard runs on one of your servers, or on Dokploy Cloud at $4.50 a server (pricing).
- Coolify deploys copies to several servers but leaves load balancing to you. Its dashboard runs on one of your servers, or on Coolify Cloud at $5 a month for two servers plus $3 per extra server (pricing).
- Ployz connects servers itself, with no Swarm or Kubernetes underneath. Its dashboard runs on Ployz Cloud, free on any number of servers, and your coding agent can run it through
ployz mcp.
My full comparison is in best self-hosted PaaS, and Coolify against Ployz is in Coolify vs Ployz.
Where Ployz fits
I built Ployz for the step after one server, without a cluster to run. It turns the servers you rent into a platform your coding agent runs. Paste Read ployz.dev/agents.md and deploy this repo to my server. into Claude Code, Codex or Cursor and it ships the repo.
ployz up --server root@your-server
Your servers share one private network. Every server serves https itself, so you rent no load balancer. Every deploy, restart or delete your agent asks for waits for you to approve. Two servers come to about $14 a month, against about $21 for a three-node Swarm or K3s. Ployz is free on any number of servers. Connect your agent and deploy on your own server.
FAQ
Is Docker Swarm still supported?
Yes. Swarm mode is built into Docker Engine and maintained, and Mirantis says it "will be fully supported through at least 2030". The old standalone Classic Swarm is the one that's no longer developed.
What replaced Docker Swarm?
Swarm mode replaced Classic Swarm. In the market, Kubernetes won, which is why Swarm has fewer tutorials, integrations and hires.
Is Nomad free to use?
For running your own apps, yes. Nomad 1.7.0 and later are under the Business Source License 1.1, which allows production use unless you offer Nomad to others in competition with IBM's paid versions.
Is K3s an alternative to Kubernetes?
Not really. K3s is a certified Kubernetes distribution, so it's cheaper to run but keeps Kubernetes' upgrades, manifests and concepts.
What's the cheapest way to run containers without Kubernetes?
One server with Docker Compose, at about $7 a month in Europe for three small apps. Adding Ployz, or a self-hosted Coolify or Dokploy, costs nothing extra. Among managed services, Fly.io is cheapest for small always-on apps, at about $11 for three.
How I checked
I checked every price and fact on 2026-10-01 against each vendor's own pages and docs, linked next to each number, and the Coolify Cloud and Dokploy Cloud prices on 2026-10-08. Server prices are Hetzner's Europe prices before VAT unless I say otherwise. I didn't build each option for this article; server counts come from each project's documented minimums.
Let your coding agent run your own servers without Kubernetes, free with Ployz. Get started with Ployz.