Back to all companies
Sign in
Back to all companies
CoreOS logo

CoreOS

Summer 2013Acquired

Open source tools of modern distributed systems.

Save
CoreOS logo

CoreOS

Summer 2013Acquired

Open source tools of modern distributed systems.

Save
Company details

CoreOS is part of the Red Hat family. A leader in the open source community and an innovator of open source projects, CoreOS creates and delivers critical components for containerized applications that help fuel broad adoption of secure, scalable and resilient infrastructure. The team maintains several open source projects, including: Container Linux: the secure automatic updating OS; and etcd, the distributed data store for Kubernetes.

Join us at https://coreos.com/ and @CoreOS on Twitter.

Location
San Francisco, CA, USA
Founded
2013
Category
Open Source
YC Directory Pagecoreos.com
Founder
  • AP
    Alex Polvi
    Founder/CEO
    LinkedIn

CoreOS is part of the Red Hat family. A leader in the open source community and an innovator of open source projects, CoreOS creates and delivers critical components for containerized applications that help fuel broad adoption of secure, scalable and resilient infrastructure. The team maintains several open source projects, including: Container Linux: the secure automatic updating OS; and etcd, the distributed data store for Kubernetes.

Join us at https://coreos.com/ and @CoreOS on Twitter.

Location
San Francisco, CA, USA
Founded
2013
Category
Open Source
YC Directory Pagecoreos.com
Founder
  • AP
    Alex Polvi
    Founder/CEO
    LinkedIn

Pressure-test this opportunity

Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.

On this page
  • Overview
  • Founding Story
  • Timeline
  • What They Built
  • Market Position
  • Category and competition
  • Open source and commercial control
  • Customers and scale
  • Business Model
  • Traction
  • Post-Mortem
  • Acquisition separated the portfolio
  • Container Linux became two successors
  • Neutral governance produced opposite outcomes
  • Key Lessons
  • Sources

This report was generated by our Deep Research agent and may contain mistakes.

Did we get something wrong? DM @oscrhong and we'll fix it ASAP!

Startups.RIP — Dead startups, alive ideas
PricingContactPrivacyGot feedback? DM @oscrhong
Exec Briefing

Actionable insights

If you only have a few minutes to spare, here’s what investors, operators, and founders should know about CoreOS (S13).

  1. The stack had separate futures. The operating system, enterprise platform, registry, runtime, and datastore followed different owners, governance bodies, and lifecycle states.
  2. Neutral governance preserved possibility. Two donated projects diverged: one became critical graduated infrastructure while the other lost contributors and was archived.
  3. Successors need explicit acceptance. New operating systems carried the update model forward, but the original still required a dated EOL and migration path.
  4. Technical legacy exceeded economic evidence. Several components became durable infrastructure even though revenue, margins, customer counts, and acquisition proceeds remained undisclosed.

Overview

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.

CoreOS logo
The company built a portfolio of open-source infrastructure around automatic operations.
Alex Polvi portrait
Alex Polvi co-founded and led the company from its 2013 start through the Red Hat acquisition.

Image 1 / 2

Founding Story

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]

GV conversation with CoreOS co-founders Alex Polvi and Brandon Philips

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.

Timeline

  • 2013: Polvi and Philips founded CoreOS; etcd was announced and the company joined YC.[1][6]
  • 2014: Kubernetes adopted etcd; CoreOS introduced rkt.[8]
  • May 2016: CoreOS raised a $28 million Series B, bringing reported funding to $48 million.[9]
  • March 2017: CoreOS donated rkt to CNCF.[8]
  • January 2018: Red Hat announced the $250 million acquisition.[3]
  • May 2018: Red Hat published its integration roadmap for Tectonic, Container Linux, Quay, and OpenShift.[10]
  • December 2018: etcd joined CNCF.[11]
  • August 2019: CNCF archived rkt.[12]
  • January 2020: Fedora CoreOS became generally available.[2]
  • May 26, 2020: Container Linux reached end of life; images and update infrastructure were removed after September 2020.[13]
  • November 2020: etcd graduated from CNCF.[11]
  • 2026: The packet's official Kubernetes source announces etcd v3.7, evidence of continuing project development.[14]

What They Built

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.

CoreOS product imagery
CoreOS joined minimal hosts, distributed coordination, container runtimes, cluster automation, and image distribution into one infrastructure portfolio.

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]

Unlock the full CoreOS teardown

Read the complete post-mortem, the rebuild playbook, and the exact reasons CoreOS is still worth studying now.

See Pro plans