[flagged]
Cirrus Labs to join OpenAI
131–140 of 157 posts
Re: Cirrus Labs to join OpenAI
#132I've moved most companies away from using others stuff 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.
Been there, done that, and I still find value in 3rd party services despite the occasional need to migrate. Self 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 workloa…
>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.
We did not have any budget constraints at all.
Depending on 3rd party meant:
1. Begging for issues where project owner has marked them "won't fix"
2. Navigating hundreds of features we don't use, don't need and not having features we absolutely need but they don't have.
3. Weird gotchas and cost saving implemented by them, where we do not want to save any money.
>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.
We actually factored all costs, our self hosted solution are "very lean" and still come out ahead when you factor in time/cost.
>spending dollars (of engineer time) to save pennies on SaaS bills.
I ran by this for long time fasely believing "engineers are way more expensive than cloud bills, so these thousands of dollars we are spending on these services don't matter"
but when we actually got down to fixing all , we realised now it costs us 1/10th of what it used to with more flexibility and reliability.
>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
we found exact opposite tbh, integrating into others hurt our performance, wasted our time, made us frustrated and desperate.
Only external service we use now are Anycast for serving our sub millisecond api and "billing", yes billing because it has lots of edge cases, taxes and all wicked things we can't manage on our own.
Still looking to rollout inhouse biller soon though.
Re: Cirrus Labs to join OpenAI
#133Earlier quoted context omitted.
Not to sell Tart short (it is quite good), but it's "just" a wrapper around Virtualization.framework with a few extra pieces. This is the kind of thing that Codex driven by experts _should_ be able to build very easily.
interesting that was what i thought this was, it keeps boggling my mind the sums being paid for what really could be built by experienced devs on their own teams
You don't want a 40-men strong team that needs to be managed, you want 2 guys that already did it and are hungry for the next 10 problems all on their own.
"Hey guys, make our agents verify tool use before responding to the user. See you in 2 months. Here's 2$b"
Re: Cirrus Labs to join OpenAI
#134Earlier quoted context omitted.
A timer?
> Then, unprompted, Altman offers up a kind of shocking timeline for the groundbreaking feature of counting: “Maybe another year before something like that works well.” Per Altman, ChatGPT’s voice model doesn’t have the capability of starting a timer or keeping track of time. “But we will add the intelligence into the voice models,” he said. -- https://gizmodo.com/sam-altman-says-itll-take-another-year-b...
I started writing “why would you want that?”, thinking about Alexa users…
Then I remembered scripting existed ^_^
Re: Cirrus Labs to join OpenAI
#135Did anyone else think this was Cirrus Logic? https://en.wikipedia.org/wiki/Cirrus_Logic
I definitely had to look and see if this was the same company, yes.
Edit: TIL “Apple makes up 89% of the company's revenue in 2025”
Re: Cirrus Labs to join OpenAI
#136Re: Cirrus Labs to join OpenAI
#137[dead]
Re: Cirrus Labs to join OpenAI
#138Earlier quoted context omitted.
A timer?
> Then, unprompted, Altman offers up a kind of shocking timeline for the groundbreaking feature of counting: “Maybe another year before something like that works well.” Per Altman, ChatGPT’s voice model doesn’t have the capability of starting a timer or keeping track of time. “But we will add the intelligence into the voice models,” he said. -- https://gizmodo.com/sam-altman-says-itll-take-another-year-b...
I cant wait till chatgpt sets me 14 minute timers when I request a 40 minute timer, just another year!
Re: Cirrus Labs to join OpenAI
#139The projects that tend to get acqui-hired — Astral, Bun, Cirrus, etc. — share something specific: they solved a real problem that the acquirer depends on internally, and nobody else had solved it well enough. That's a different dynamic than "be notable and hope someone bids."
What's actually happening is that AI labs have infrastructure needs that don't map cleanly onto existing commercial products, so the fastest path to having the tool they want is to bring the team building it in-house. That's closer to procurement than a traditional acqui-hire.
Whether that's net positive for the ecosystem is genuinely unclear. You get a better-resourced tool in the near term. But you also get organizational risk: if the acquirer pivots or the team gets reassigned, the institutional knowledge goes with it. Tart being relicensed more permissively is the hedge against that scenario, and it's a smart move.
Re: Cirrus Labs to join OpenAI
#140Note 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…
>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.