3 ms·
Note that this is fundamentally different from the Astral acquisition. At the end of their announcement, they stated: > Cirrus CI will shut down effective Mond
by maxloh 6mo ago
Note that this is fundamentally different from the Astral acquisition. At the end of their announcement, they stated:
> 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.
- hirako2000 6mo agoIt could also be a suite of product acquisition, the CI could be a product OpenAI is interested in having, but not sell.
- trollbridge 6mo agoYeah. Much like Astral - acquiring both the product (because they need to use it internally, but don't care about trying to resell / market), and they also want the talent to keep maintaining it / add features they want.
- fkorotkov 6mo agoJust 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.
- CompoundEyes 6mo agoIf your scope includes making the Codex web app environments have additional functionality I look forward to it. More enterprise features and yaml backed pipelines.
- mogili1 6mo agoIf you are interested in yaml backed pipelines check out this open source tool I built for exactly this purpose: https://github.com/smogili1/circuit https://github.com/smogili1/circuit
- js2 6mo agoWhat are your plans for tart licensing going forward? https://github.com/cirruslabs/tart/blob/main/LICENSE https://github.com/cirruslabs/tart/blob/main/LICENSE https://tart.run/licensing/ https://tart.run/licensing/
- tclancy 6mo agoThat sounds like a British phrase for pimping.
- fkorotkov 6mo agoYou’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.
- naikrovek 6mo agoMIT 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…
- elAhmo 6mo agoFor now.
- koolhead17 6mo agoIs Sam or family an investor in them anyways?
- deleted 6mo ago[deleted]
- fkorotkov 6mo agoWe were 100% bootstrapped with no outside capital or support/advisory.
- koolhead17 6mo agoCongrats, I am sure you and team made some $$$.
- troyvit 6mo agoThis is kind-of neat too, at least in the near term: > 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.
- cschmatzler 6mo agoThis is making my current work 100 times easier. Very welcome timing.
- naikrovek 6mo agoThis is awesome because I flippin love tart.
- rmast 6mo agoThat part is amazing. Back when I first heard of tart I thought it was amazing, with the one downside being the license. Hopefully development on it continues, or a community maintained version keeps it going.
- pxc 6mo agoThis is a huge deal! I secretly hoped for this. :)
- rmast 6mo agoI mostly clicked the link because I was curious if Cirrus Labs operates Cirrus CI and if so how that would be impacted. 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?
- super256 6mo ago>It isn't a product-led acquisition, but more a talent one. I am pretty sure OAI mostly cares about their virtualization IP for MacOS. They already extensively use WSL2 for sandboxing Codex on Windows, and I imagine they want something similar for Codex on Mac.