This 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.

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.

It could also be a suite of product acquisition, the CI could be a product OpenAI is interested in having, but not sell.

Is Sam or family an investor in them anyways?

Yes, it brought back some video card memories

They want to kill the last good ones

Every great journey must have an end. As far as I understand Cirrus CI was struggling due to Github Actions eating their market. Cirrus CI was in my opinion much better than Github Actions but it is hard to compete with a bundled solution.

Same; the reason everyone ran out to buy Mac Minis last month is it gave their Claw access to iMessage, their browser cookies, and a residential IP. Cirrus provides a way to provision and orchestrate MacOS VMs, which is exactly what I did for running Openclaw (for a minute …).

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.

“We will replace white collar workers”

Proceeds to buy white collar workers.

yeah super confused, it looks like some tools to manage vms in ci? what is unique about that vs lxc or docker or apple's native container cli?

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 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.

That is something of a broken promise in the SaaS world; it was supposed to be convenience but instead it became a hundred broken integration points as you struggle to keep up with deprecated APIs and acqui-hires killing off shims you wouldn't have needed if everything had been on-prem to begin with.

What software do you use to run your CI?

  - gitea
  - woodpecker CI
  - my own docker registry
  - portainer running on my docker swarm

This is the way.

This is a VC site. Morality or changing the world for the better is window dressing on earning as much money as possible and damn anyone who gets in the way. Morality is only good in as much as it’s good for business to be seen as moral. Money people have been majority running things for over 2 decades at least but the mythos lives on.

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.