https://github.com/scipy/scipy/issues/24990
https://www.postgresql.org/message-id/3ydjipcr7kbss57nvi67no...
I wish Fedor and everyone at Cirrus the best of luck and OpenAI and thank them immensely for the years of free CI they gave to us in the Pony programming language despite it not having any marketing value to them.
Do service providers not think customers have other things to do than simply maintain their existing infrastructure?
> We never raised outside capital
I guess it worked out though
It's kind of like electric cars charged with electricity from coal power plants.
I’m happy for the founders, they’re great folks. I contributed to CirrusCI a bit in the past and it was a great experience. I even advocated for Cirrus in a couple of my last $DAYJOBs (with varied success). Congrats Fedor!
I’m very sad they’re shutting down, though. IMHO CirrusCI was very close to a perfect CI system (I wrote a blogpost about it [0]). I’ll now have to find something to replace it with in my personal projects. I guess I’ll run their cirrus-cli in GitHub Actions for a while. But GitHub Actions is really poor. I heard some good things about Buildkite.
https://developers.openai.com/api/docs/guides/tools-computer...
> Cirrus CI will shut down effective Monday, June 1, 2026.
And earlier in the article:
> Joining OpenAI allows us to extend the mission we started with Cirrus Labs: building new kinds of tooling and environments that make engineers more effective, for both human engineers and agentic engineers.
It isn't a product-led acquisition, but more a talent one.
Today we use Hertzner and OVH and roll out our own solution whenever possible.
Running lean and mean.
Depending on such third party services is a trap.
We started a company to make a big difference in the world and build an engineer’s dream company, and that’s why we have now decided to do the exact opposite and become employee numbers 32,463 through 32,510 at one of the largest tech companies in the world because money is nice.
Look, I’d have done the same thing, I’m not criticizing the choice. I just think we don’t need this kind of weird unnatural rhetoric.
Please just stop with the tech industry puffery. You’re not Steve Jobs, you’re just the DevOps team at OpenAI now. You’re dumping your worthless code on GitHub, and you’re kicking your customers to the curb.
There’s no PR spin left to do anymore. You’re not a company anymore and you’re not a founder anymore.
It certainly makes the idea of a career progression / promotion more challenging than it used to be, but perhaps it also opens up some new opportunities. It becomes far more "high stakes" since you have to take the risk of starting and running a startup that ultimately fails if it does not get acqui-hired.
So they want an integrated solution with CI, Python packaging and vibe coding.
That is a $100 million valuation at best, not a $1 trillion one.
This just confirms to me that we are no where near AI being able to write any complicated software. I mean, if it could woudln't OpenAI just prompt it into existence? ;)
Can you talk a bit more about your journey without raising funds?
Also what does HN think of that path today when trying to launch a new AI startup?
> In 2022, we built Tart, which became the most popular virtualization solution for Apple Silicon, along with several other tools along the way.
from Tart's github:
> [Tart is for] macOS and Linux VMs on Apple Silicon to use in CI and other automations
My (naive?) hypothesis is this kind of expertise is why OpenAI chose to acquihire.
Looks like I’ll need to move the FreeBSD CI jobs for open source projects I maintain to another solution. Anyone have suggestions for alternatives?
> 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.
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
> We are no longer accepting new customers for Cirrus Runners but will continue supporting the service for existing customers through their existing contract periods.
For most CI use, you can choose between:
Anka, a "contact-us for pricing" closed-source projet, where you have to pay expensive license (easy 3000 USD/yr per machine)
or tart, which is a lightweight wrapper around the official Apple API.
But you have to know that on MacOS, there is an artificial limit of 2 VMs per Mac... but well:https://github.com/cirruslabs/orchard/commit/3cfa2445500f45f...
With https://khronokernel.com/macos/2023/08/08/AS-VM.html
Some people might find it very attractive:
Instead 25 Mac Mini you might need only 5.
+ No licensing to pay to Anka.
Even without bypassing the limit it is great actuallySelf hosting is the way to go if you need to keep monthly services spend as low as possible but you have extra time to spend, such as with a hobby project.
Whenever I’ve worked on real startup projects, self-hosting became a constant source of little tasks for the engineering team to mix into our weekly workload. There were always little tasks to upgrade this service, investigate why that one server was slow, or to migrate something to a bigger server because we were bottlenecked on some resource. Then we had to manage backups and do our recovery drills, along with changing the backup strategy every 6 months because someone had a better idea.
When we started to add up all of the time spent managing everything it starts to look like spending dollars (of engineer time) to save pennies on SaaS bills.
Probably not a popular thing to say on HN, but I now try to stay away from teams that go to extremes to self-host everything because I just want to get my work done, not also be constantly involved in running the underlying services. I do it for my own hobby projects at home but I don’t want to be doing it at work where we have money to spend to lighten the load. If the cost is the occasional migration to a different 3rd party service that’s not a big workload relative to everything involved in self-hosting.
This has been popular for 25+ years. Likely before, but that's when I first started noticing a significant number of companies that were clearly in business solely TO BE BOUGHT.
I'm guessing you're referring to this recent report of the security vulnerabilities Mythos found and submitted patches for? That just seems like they don't want the negative press and/or liability if their new model ends up being used to create 0-days that cause widespread damage.
Proceeds to buy white collar workers.
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.
Hopefully development on it continues, or a community maintained version keeps it going.
@sama if you need someone to buy to implement timers for ChatGPT I’m your guy - my price is 2 billion dollars.
Cost savings are insane and the speed of latest amd epycs are miles ahead of the default ci instances on github and other places.
- gitea
- woodpecker CI
- my own docker registry
- portainer running on my docker swarm
I then define the docker stack in the git repository, and CI builds the images and pushes to build the new image to the docker repository. The portainer API allows to deploy a stack, with the image tag as a parameter.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!
I’m sure there’s a way to say the same thing without coming across as a bullshitter.
I don't understand why these sites just put a bunch of buzzwords instead of telling you what it actually is.
> 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.
I started Cirrus Labs in 2017 in the spirit of Bell Labs. I wanted to work on fun and challenging engineering problems, in the hope of bootstrapping a business as a byproduct.
The mission was to help fellow engineers with new kinds of tooling and environments that would make them more efficient and productive in the era of cloud computing. Even the name reflected that ambition: Cirrus, inspired by cirrus clouds, one of the highest clouds in the sky.
We never raised outside capital. That let us stay patient, stay close to the problems, and put a great deal of care into the products we built.
Over the last nine years, we were fortunate to innovate across continuous integration, build tools, and virtualization. In 2018, we introduced what we believe was the first SaaS CI/CD system to support Linux, Windows, and macOS while allowing teams to bring their own cloud. In 2022, we built Tart, which became the most popular virtualization solution for Apple Silicon, along with several other tools along the way.
In 2026, it is impossible to ignore the era of agentic engineering, just as it was impossible to ignore cloud computing in 2017. Agents need new kinds of tooling and environments to be efficient and productive as well.
This is why when the opportunity arose for us to join OpenAI, it was an easy yes, and I'm happy to announce today that we've entered into an agreement to join OpenAI as part of the Agent Infrastructure team.
Joining OpenAI allows us to extend the mission we started with Cirrus Labs: building new kinds of tooling and environments that make engineers more effective, for both human engineers and agentic engineers. It also gives us the opportunity to innovate closer to the frontier, where the next generation of engineering workflows is being defined.
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.
We are no longer accepting new customers for Cirrus Runners but will continue supporting the service for existing customers through their existing contract periods.
Cirrus CI will shut down effective Monday, June 1, 2026.
To everyone who used our products, contributed code, reported bugs, trusted us with their workflows, or supported us along the way: thank you. Building Cirrus Labs has been the privilege of a lifetime.
That said, I've been free-riding on tart because they've often surfaced issues I needed to address. Free riders like me are possibly the reason these companies can't make their own way.
If you’re taking requests…
If this is a forgettable press release isn't it lower effort than coming up with this type of nonsense?
Long term: they now have experienced dev(s?) to build their next products and features