It won’t and I think it will thrive even more. ;)

You are checking the wrong Cirrus Labs.

We were 100% bootstrapped with no outside capital or support/advisory.

Congrats, I am sure you and team made some $$$.

Thank you! Full journey is too long for a comment here.

It was hard and I was lucky with my previous pre-IPO gigs at Airbnb and Twitter so I had some bootstrap fund. In retrospective a dev tools startup in 2017 with no network and no VC support was a crazy idea but I was young and didn’t think thought too much.

Then it was long 8 years of raw work and constant questioning this choice. Then finally a third component: luck. In 2024-2025 it kind of grew organically due to market changes and back in October 2025 I finally stopped questioning the future of Cirrus Labs.

My only advice if I may, try to get your first dollar from your startup while you are employed.

That is good advice!

I am too late for that as I am full time but also lucky to have had a previous exit.

I am planning to go the VC route this time, because the problem I am going after feels VC size.

However I feel bootstrap or small F&F round gives you more flexibility when it comes to exits.

Congrats again!

Just want to note that we will continue maintaining and improving our virtualization solutions actually with even greater attention. SaaS options like Cirrus CI and Cirrus Runners will eventually wind down so we can focus on incorporating pieces internally.

What are your plans for tart licensing going forward?

https://github.com/cirruslabs/tart/blob/main/LICENSE

https://tart.run/licensing/

You’ll be pleasantly surprised. Updates in the coming weeks.

> In the coming weeks, we will relicense all of our source-available tools, including Tart, Vetu and Orchard under a more permissive license. We have also stopped charging licensing fees for them.

MIT or Apache2 or FreeBSD licenses would be preferable in my case, but GPLv2 or even AGPLv3 (if you have to) would work.

If you’re taking requests…

That sounds like a British phrase for pimping.

If your scope includes making the Codex web app environments have additional functionality I look forward to it. More enterprise features and yaml backed pipelines.

If you are interested in yaml backed pipelines check out this open source tool I built for exactly this purpose:

https://github.com/smogili1/circuit

For now.

Thank you! Cirrus CLI is still around and can run your tasks locally in either Podman or Docker. Can also be used in any other CI.

Cirrus CI was on a downhill in terms of users and revenue for years now. Most of the customers moved to GHA already.

Plus migration is super easy with Cirrus CLI -- tool to run our CI task definitions locally or in any CI. See https://github.com/cirruslabs/cirrus-cli

Thank you for kind words! But we were planning to shut down Cirrus CI anyways. The usage was lower and lower due to GitHub Actions to the point this product was not bringing revenue. As a bootstrapped company we wouldn’t have an option to have a not profitable offering.

It is a pity because your offering was much better than Github Actions. Good luck with your future projects!

I agree! It’s a pity we didn’t make commercially successful.

Can you elaborate on what got “broken” on Tahoe?

How much do you pay for the servers that run actions? Is it much more than $610? Then it kinda makes sense.

No it's much less. Our runners are hosted in AWS ECS, you'd be surprised how affordable you can make that given the right optimizations (which is probably why GH made this decision).