Kubernetes is an excellent tool. It is also the most over-prescribed technology in the startup world. Here is when you actually need it — and when you do not.
→ Checking service count…
→ Measuring orchestration overhead…
⚠ 4 developers + Kubernetes = 1 FTE on ops
⚠ 200+ lines of YAML for a single deploy
✓ Docker Compose: 15 min setup, same result
✓ PaaS (Render/Fly.io): 5 min, zero ops
We are not anti-Kubernetes. It is a powerful orchestration platform that solves real problems at scale. The issue is that startups adopt it long before they have those problems, and the complexity kills their velocity.
Kubernetes provides: declarative infrastructure, automatic scaling, self-healing, rolling deployments, service discovery, and load balancing. These are all valuable. The question is whether you need them now, and whether the cost is justified.
Kubernetes requires: YAML manifests (hundreds of lines), an understanding of pods, services, ingress, configmaps, secrets, volumes, namespaces, RBAC, and network policies. A CI/CD pipeline that builds container images, pushes to a registry, and deploys via kubectl or Helm. Monitoring and logging configured for distributed containers. And someone on the team who understands Kubernetes deeply enough to debug it when it breaks.
For a 4-person team shipping a single application, this is weeks of setup and ongoing maintenance. It is a full-time job for one person — a person who is not building your product.
You need Kubernetes when: you have 10+ services that need to scale independently, you have a dedicated platform/DevOps team, your deployment frequency requires automated orchestration, or your cloud provider costs are high enough that bin-packing saves meaningful money.
Until then, simpler alternatives work: a single VPS with Docker Compose for early stage, a managed PaaS (Render, Railway, Fly.io) for growth stage, or AWS ECS / Google Cloud Run for mid-stage. These give you 90% of the benefits with 10% of the complexity.
Start simple. When you outgrow it, migrate. The migration from Docker Compose to Kubernetes is well-documented and straightforward. The migration from "we set up Kubernetes too early and now everything is tangled" to a clean Kubernetes setup is not. Simplicity first, complexity when earned.
Simplicity first, complexity when earned. The migration from Docker Compose to Kubernetes is straightforward. The migration from premature Kubernetes to clean Kubernetes is not.
Most systems work fine at current load. The question is whether they will work at 10x. Here are the five warning signs we look for in every architecture review.
20 Aug 2026Everyone asks this question. The answer is not "it depends" — it is "start with a modular monolith and extract services when you have a reason to." Here is why.
10 Aug 2026We apply the same rigour to real client engagements. Architecture reviews, security audits, and stack recommendations — all fixed-price, all actionable.