
Open source tools of modern distributed systems.
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about CoreOS (S13).
CoreOS began in 2013 with a systems-maintenance thesis: servers should update as reliably as browsers. Founders Alex Polvi and Brandon Philips built Container Linux around a minimal, immutable base and whole-system automatic updates, then expanded into etcd, rkt, Tectonic, and Quay.[1][2]
Red Hat announced a definitive $250 million acquisition in January 2018, subject to immaterial closing adjustments.[3] The company disappeared, but its products did not share one fate. Tectonic technology flowed toward OpenShift, Quay remained distinct, Container Linux ended, rkt was archived, and etcd became a graduated CNCF project with active releases. Fedora CoreOS and RHEL CoreOS carried the operating-system model forward.
Image 1 / 2
Polvi and Philips were college friends who had seen how difficult it was to keep fleets of server systems current. They founded CoreOS in 2013 and joined Y Combinator's Summer batch.[4] Polvi later said the pair had wanted a technically meaningful project with major commercial potential.[5]
Their first answer was Container Linux, a minimal Linux distribution designed to run containerized workloads in clusters. Instead of letting each server accumulate conventional package changes, the operating system updated as a complete image. A small immutable base and automatic updates reduced configuration drift and shortened the path from security fix to deployed host.[2]
The mission expanded from one operating system to a cloud-native control layer. CoreOS announced etcd in June 2013 as a distributed key-value store for coordination state. Kubernetes adopted it in 2014 as its control-plane backing store.[6] Kubernetes' scaling demands later drove etcd v3 work because the v2 watch behavior could not support the project's 5,000-node target.[7]
CoreOS also challenged Docker's runtime dominance. It introduced rkt in December 2014 as a composable, pod-native runtime. Its appc work contributed to discussions and specifications that fed into the Open Container Initiative image specification. In 2017, CoreOS donated rkt to CNCF as a neutral home.[8]
The packet supplies one short verbatim Polvi quote, "more fuel for the tank," about financing, but not two substantive founder quotes about the founding or product. The canonical quote requirement therefore remains partially unmet rather than fabricated.
Container Linux treated the host as an automatically updated appliance for containers. The design minimized installed software and discouraged manual mutation. That model made upgrades an operating-system property rather than a fleet-by-fleet package-management project.

etcd stored coordination and configuration state with consistency guarantees, watches, and tolerance for leader failure. Kubernetes made it indispensable to its control plane. By August 2024, CNCF counted 873 contributing companies, 5,667 contributors, and more than 168,800 cumulative contributions; CoreOS remained the largest all-time organizational contributor at 36 percent.[11]
Read the complete post-mortem, the rebuild playbook, and the exact reasons CoreOS is still worth studying now.