HackerTrans
TopNewTrendsCommentsPastAskShowJobs

fkorotkov

no profile record

Submissions

Show HN: Omni Cache – friendly sidecar for CI caching needs

github.com
2 points·by fkorotkov·5 bulan yang lalu·0 comments

New Pricing of self-hosted GitHub Actions Runners explained

cirrus-runners.app
2 points·by fkorotkov·7 bulan yang lalu·3 comments

comments

fkorotkov
·3 bulan yang lalu·discuss
It won’t and I think it will thrive even more. ;)
fkorotkov
·3 bulan yang lalu·discuss
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.
fkorotkov
·3 bulan yang lalu·discuss
You are checking the wrong Cirrus Labs.
fkorotkov
·3 bulan yang lalu·discuss
We were 100% bootstrapped with no outside capital or support/advisory.
fkorotkov
·3 bulan yang lalu·discuss
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.
fkorotkov
·3 bulan yang lalu·discuss
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.
fkorotkov
·3 bulan yang lalu·discuss
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.
fkorotkov
·3 bulan yang lalu·discuss
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
fkorotkov
·3 bulan yang lalu·discuss
I agree! It’s a pity we didn’t make commercially successful.
fkorotkov
·3 bulan yang lalu·discuss
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.
fkorotkov
·6 bulan yang lalu·discuss
Can you elaborate on what got “broken” on Tahoe?
fkorotkov
·7 bulan yang lalu·discuss
How much do you pay for the servers that run actions? Is it much more than $610? Then it kinda makes sense.
fkorotkov
·7 bulan yang lalu·discuss
IMO it's long time coming. Streaming logs and other supporting functionality is not free. We at Cirrus Runners provide runners as a service for a fixed monthly price with unlimited usage. We target large entrerprises that save $100K+ yearly by switching to us (10-25 times). In our calculations the new per-minute fee is roughly ~0.1% of the effective per-minute cost our customers avoid by using our fixed-price model. Over providers with the traditional per-minute pricing will have bigger impact.
fkorotkov
·7 bulan yang lalu·discuss
Today GitHub announced changes to pricing for GitHub-managed runners and introduced a new per-minute charge for organizations using self-hosted runners. Below we’ll dive into what changed, the backstory, how companies have been using self-hosted runners, and how this affects third-party providers like Cirrus Runners.