Cirrus Labs logo

Cirrus Labs

Developer infrastructure for continuous integration and virtual machines.

Related collections

Cirrus Labs at a glance

  1. A useful product can lose its distribution. Korotkov attributed Cirrus CI’s decline to customers moving to GitHub Actions. Technical preference alone did not protect a separate hosted service.
  2. Separate the component from the business. Tart and Orchard continued while hosted CI wound down. A reusable infrastructure capability can retain strategic value after its original packaging weakens.
  3. Bootstrapping makes product economics matter. The founder said Cirrus CI was already headed for closure. Evaluate each product’s contribution before extending a struggling offering for the sake of completeness.
  4. Read the current license. Fee removal and promised relicensing did not erase every restriction in Tart’s current repository. Commercial plans need version-specific permission checks.

Overview

Cirrus Labs built useful developer infrastructure while one of its hosted products lost its commercial footing. Founder Fedor Korotkov said Cirrus CI's customers and revenue had declined as users moved to GitHub Actions. The company also developed Tart, Orchard, and Vetu, tools for creating and managing virtual machines. In April 2026, it announced an agreement to join OpenAI's Agent Infrastructure team. The hosted CI service and the virtualization tools had different futures.[1][2]

Patient engineering, uneven economics

Korotkov started Cirrus Labs in 2017 and said it never raised outside capital. Its 2018 CI service supported Linux, Windows, and macOS, including customers' own cloud infrastructure. In 2022 it introduced Tart for Apple Silicon virtualization.[1]

Bootstrapping gave the team control over its product choices, but required products to support their operating costs. In a separate public discussion, Korotkov said Cirrus CI was already headed toward closure because falling usage left it commercially unsuccessful. That is a founder's explanation for one product's decline; it does not establish that the whole company was distressed.[3]

The distinction matters. A startup can struggle to sell a broad hosted service while developing a component that other engineering teams need. Cirrus's later product portfolio makes that interpretation plausible. OpenAI has not publicly assigned a separate purchase value to each component.

Cirrus CI build page with successful build, lint, spell-check, deploy, and Dockerfile prebuild tasks
Cirrus CI’s documentation screenshot shows a completed build and its individual tasks.

Source: Cirrus Labs

Virtual machines as reusable build inputs

Tart creates and runs macOS and Linux virtual machines on Apple Silicon using Apple's Virtualization framework. It can push and pull machine images through container registries and automate image creation with Packer. A team can prepare a known build environment and reuse it instead of repeatedly installing dependencies.[4]

Source: Cirrus Labs; tweet excerpt

Orchard manages Tart machines across a cluster of Apple Silicon hosts. Vetu addresses ephemeral Linux virtual machines. Together, the tools cover machine creation, distribution, and coordination. Their public repositories now live under OpenAI's GitHub organization, which corroborates the technical continuation beyond the original company announcement.[5][6]

Tart's website names Codemagic, Expo, and Snowflake in user testimonials. Codemagic describes VM startup performance; Expo emphasizes source access and maintenance; Snowflake describes segmented macOS development infrastructure. These are vendor-published customer accounts, with no independently audited adoption or revenue figures supplied.[7]

Users valued what the market bundled

The announcement's Hacker News discussion contains both praise and migration complaints. Users called out FreeBSD support, custom machine images, and disposable build environments. Korotkov said the team would continue virtualization work while the hosted services wound down. Those comments explain why technical users could value the product even as its standalone CI revenue declined.[2]

The supported lesson is about distribution and packaging. GitHub Actions put CI next to repositories; Cirrus had to persuade users to adopt another service. The founder directly attributes customer movement to that competitor. Public evidence does not quantify the effect of price, reliability, or individual feature gaps, so those alternatives remain unresolved.[3]

Outcome and evolution

The April 7 announcement scheduled Cirrus CI to close on June 1, 2026. Cirrus Runners stopped accepting new customers, with existing contracts supported through their terms. The team also stopped charging tool license fees and promised more permissive licensing.[1]

The current Tart repository uses FSL-1.1-ALv2, which contains a competing-use restriction and a later Apache 2.0 grant. Older website pricing still describes paid license tiers. A new operator should review the exact version and intended service before assuming it can resell hosted Tart. The announcement's fee change does not by itself settle every license permission.[8][9]

Buildkite already offers metered macOS hosted agents. A new business would need a distinct workflow, such as maintaining reproducible images on customers' own Mac fleets, rather than another general CI dashboard. That is an opportunity hypothesis, with demand and support costs still to test.[10]

Timeline

  • 2017: Korotkov started Cirrus Labs.[1]
  • 2018: Introduced its cross-platform hosted CI system.[1]
  • 2022: Introduced Tart.[1]
  • April 7, 2026: Announced the agreement to join OpenAI.[1]
  • June 1, 2026: Announced shutdown date for Cirrus CI.[1]

Sources

  1. Founder announcement
  2. Main announcement discussion
  3. Founder explanation of CI economics
  4. Tart repository
  5. Orchard repository
  6. Vetu repository
  7. Tart product and customer accounts
  8. Current Tart license
  9. Legacy licensing page
  10. Buildkite Mac Hosted Agents

Pressure-test this opportunity

Explore the risks and possibilities with a prompt for ChatGPT, Claude, or your agent.