Kubernetes Alternatives for Small Teams
10 ways to run containers without a cluster, ranked by how much you have to learn before the first deploy
For a small team that wants containers without Kubernetes, the options with the least to learn are Light Cloud, Railway and Render: you connect a repository and get HTTPS URLs, with no cluster, no registry and no config file to master. Fly.io and Coolify each add one new thing, Google Cloud Run and AWS ECS add cloud permissions and plumbing, and Kamal, Docker Swarm and Nomad hand you the servers. Light Cloud is first because, of the three, it is also the cheapest way to keep a few quiet services online.
I run Light Cloud, so weigh that. The scoring below is simple enough to redo yourself from the vendors' own docs.
How we ranked
Kubernetes is hard for a small team for a boring reason: the list of things you have to understand before anything runs. Nodes, a registry, ingress, certificates, YAML for each object. The longer argument ran on this blog earlier this month, so this post stays practical.
Every option below got one point for each of these six things it makes you learn or run yourself before your first deploy:
- machines you rent, patch and keep alive;
- a config file in the tool's own format;
- a container registry to set up and log in to;
- HTTPS and load balancing you configure;
- cloud permissions, such as IAM roles;
- extra tools that must run next to it.
Writing a Dockerfile doesn't count, since every option accepts one. Fewer points rank higher. Where two options tie, the one where someone else runs the machines goes first, and after that the lower bill for a reference system: three small services that are quiet most of the day. Facts come from the vendors' own docs and pricing pages, checked on 2026-10-13. Self-hosted tools get "your servers" in the price column, because I couldn't check a server price on a page I trust.
The ranking
1. Light Cloud
Best for: teams that want push-to-URL with nothing to configure and services that cost nothing while idle.
Zero points. You connect a GitHub repository and each push builds and deploys; with a Dockerfile at the root it builds exactly that, and without one it detects the framework and writes the Dockerfile for you, so you can deploy Node.js, Python, Go and Java without a Dockerfile. Certificates are issued and renewed automatically. There is no registry to log in to and no IAM. Those git push deploys come with a preview URL per branch, and logs and metrics sit next to the deploy history.
Three quiet services fit the Free plan. The pricing page puts a quiet server app at about $0.10 a month of usage, so three use $0.30 of Free's $1, with no card (pricing). Your own domain and a database start on Lite at $5. That's pay-per-use container hosting in practice: every container scales to zero by default and bills by the hour while it runs.
Now the part a Kubernetes refugee should read twice. Services talk to each other over public HTTPS, not a private network; the microservices series shows the CORS and shared-secret setup that takes. There is no cron and no background worker type. An app scales to 3 instances on Free and Lite, 10 on Starter and 50 on Business, and a warm instance that never sleeps costs about $52 a month and needs Starter. A cold service takes 3.1 to 3.7 seconds to answer. And settings live in the console, not in a manifest in your repository (the CLI's small .lightcloud file only records which app a folder belongs to). That's the point of it, but it also means no infrastructure diff to review in a pull request.
2. Railway
Best for: small systems that need private networking and cron between services from day one.
Also zero points. Railway builds from your repository, and services in a project reach each other over a private WireGuard network with internal DNS, which is exactly what Light Cloud lacks (docs). Cron jobs and pull request environments come on every paid plan.
Hobby is $5 a month with $5 of usage included, billed by the RAM and CPU your services actually use (plans). Three quiet services may stay inside that, but I can't promise it: Railway has no fixed sizes, so it depends on how much memory your processes hold. Sleep is opt-in, and Railway warns that the first request to a sleeping service may get a 502.
3. Render
Best for: fixed prices per service, and a whole system in one optional file.
Zero points, because nothing beyond a repository is required. When you want it, a Blueprint describes services, databases and environment groups in a single render.yaml, which is the closest thing here to the manifests you'd keep in a Kubernetes repo. Private networking, background workers and cron jobs are all built in.
It ranks third on the tiebreak. A paid service is a fixed instance, the smallest $7 a month (pricing), so three services are $21 whether anyone calls them or not. The free instances spin down after 15 minutes and Render says not to use them in production.
4. Fly.io
Best for: the same containers in many regions, with a private network between them.
One point: fly launch writes a fly.toml for your app's Fly-specific settings (docs), and you'll edit it sooner or later. In exchange, every organization gets a private WireGuard network across regions, and machines can stop when idle so you pay only for their disk.
The smallest always-on machine is $2.19 a month (pricing), so three are at most $6.57, less if they stop. There is no free tier for new accounts, a card is required after the trial, and Fly says it doesn't support billing alerts yet.
5. Coolify
Best for: a Heroku-style dashboard on servers you already pay for.
One point, but it's the big one: you run the machines. Everything else is handled from a dashboard. Coolify builds with Nixpacks, a Dockerfile or Docker Compose, issues Let's Encrypt certificates, starts databases from a list and deploys pull requests separately (features). It also runs cron jobs inside your apps, which several managed rows can't.
Self-hosted Coolify is free with every feature; Coolify Cloud, where they run the dashboard and you bring the servers, is $5 a month for two servers plus $3 per extra one (pricing). The Coolify server needs 2 CPU cores, 2 GB of RAM and 10 GB of disk on its own (installation). Patching, backups to your own S3 bucket, and what happens when the box dies are yours.
6. Google Cloud Run
Best for: teams already on Google Cloud that want scale to zero at raw cloud prices.
Two points. gcloud run deploy --source builds from a Dockerfile or buildpacks and creates the registry for you (docs), which is kind. But you set up a billing account and IAM, and your own domain needs a load balancer or Firebase Hosting, because Cloud Run's built-in domain mapping is a preview that Google calls not production-ready.
Three quiet services cost $0 inside the free tier of 180,000 vCPU-seconds and 2 million requests a month (pricing). Light Cloud runs on Cloud Run, so this is the same engine with the setup handed back to you.
7. AWS ECS Express Mode
Best for: AWS shops that want Fargate with the load balancer and TLS done for them.
Two points. AWS says an Express Mode service needs only three things: a container image, a task execution role and an infrastructure role. It then creates the Fargate service, a load balancer with TLS, auto scaling and monitoring. The image has to live in a registry first, and the roles are IAM.
Express Mode is free; Fargate isn't. The smallest task, 0.25 vCPU with 0.5 GB, is about $8.89 a month around the clock in us-east-1 (Fargate pricing), and a load balancer adds about $16.20 before usage charges. Three services sharing one load balancer come to about $43, before the load balancer's usage charges.
8. Kamal
Best for: Linux-comfortable teams putting containers on cheap servers.
Three points on one server, four on more. You run the servers, you write config/deploy.yml, and you need a registry, because kamal setup builds the image, pushes it, and pulls it on each host (installation). On a single server kamal-proxy gets Let's Encrypt certificates for you; with more than one, you put a load balancer in front yourself.
What you get back is a lot: zero-downtime deploys to any Ubuntu box with an SSH key, under the MIT license, from the team at 37signals that uses it for their own apps. Kamal's own homepage is candid that you're probably better off with a fully managed service if basic Linux or Docker is still difficult.
9. Docker Swarm
Best for: a real multi-machine cluster for people who already know Docker Compose.
Three points: machines, service definitions, and a load balancer for outside traffic. Swarm is built into Docker Engine, so there is no extra orchestrator to install, and it gives you service discovery by DNS name, rolling updates and rollbacks. Docker's tutorial uses three Linux hosts with ports 2377, 7946 and 4789 open between them.
It is the gentlest way to learn what a cluster is. It's also a cluster, with managers, workers and reconciliation, and Docker's own docs call it an advanced feature and suggest plain Compose if you don't plan to run Swarm in production.
10. Nomad
Best for: mixed fleets that schedule containers, Java apps and VMs side by side.
Three points: machines, job files, and the tools Nomad expects next to it. HashiCorp describes Nomad as a single binary that focuses on scheduling and composes with Consul for service discovery and Vault for secrets. It schedules more than containers, which no other row here does.
The license matters for some teams: Nomad Community Edition is under the Business Source License, per HashiCorp's own page.
Where the others beat us
Plenty of places, and they're the reasons people pick Kubernetes in the first place. If your services must talk privately, Railway, Render and Fly give you a private network today and we don't. Cron jobs are built into Railway, Render and Coolify, and Render sells background workers as a service type. Once your services are busy around the clock, a server running Kamal or Coolify is far cheaper than our always-on price, and Render's fixed $7 beats our $52. Teams that want the whole system in a reviewed file will prefer Render's Blueprint or a Kamal config to our console. And Nomad runs workloads that aren't containers at all.
What we do better is the first step and the quiet months. There is nothing to install, no file to learn and no registry, and a service nobody calls costs nothing. For three small services that's $0 on Free, and the Kubernetes alternative for small teams I'd pick for a first product is the one where you can bring your own Dockerfile and be live before lunch.
Which of the six points would you happily take on, and which made you leave Kubernetes in the first place?
More articles
Kubernetes Won. Developers Lost.
Kubernetes hit 82% production adoption and got crowned the operating system for AI. Total victory. And the losers are application developers, who were never supposed to touch a kernel, and now write YAML against one for a living.
The Day I Explained Kubernetes to My Mom
My mom asked what I do for work. Three hours later, she had accidentally designed a better container orchestration system using kitchen analogies. Here's what happened.
Julia