Apps Built with Kubernetes

Kubernetes is the heavyweight option on this page and the honest advice is that most products here do not need it. Where it earns its keep is at genuine scale or genuine complexity: many services, several environments, autoscaling against spiky traffic, and a requirement that a failed node does not become an outage. Fintech and telecoms-adjacent platforms with uptime commitments are the typical adopters. The cost is operational expertise, which is scarce and expensive locally, so a team running it either has a dedicated platform engineer or is spending engineering time it wanted for the product. Its compensating advantage is portability, the same manifests run on any provider, which preserves negotiating room on price. Browse the products running on Kubernetes below and see the scale at which teams made the jump.

Browse by tech stack

Frequently asked questions

Do most startups need Kubernetes?
No. It pays off with many services, strict uptime requirements or highly variable load. Before that it usually costs more engineering time than it returns.
What is the main barrier?
Operational expertise. The skills are scarce and expensive locally, so running it well is a real staffing commitment.