Hacker News: fkorotkov

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 18:24:08 +0000

It won’t and I think it will thrive even more. ;)

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 17:43:30 +0000

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.

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 16:32:43 +0000

You are checking the wrong Cirrus Labs.

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 15:59:31 +0000

We were 100% bootstrapped with no outside capital or support/advisory.

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 15:53:24 +0000

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.

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 14:37:37 +0000

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.

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 14:29:11 +0000

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.

New comment by fkorotkov in "Cirrus Labs to join OpenAI"

fkorotkov — Sat, 11 Apr 2026 14:21:33 +0000

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

New comment by fkorotkov in "Cirrus Labs to Join OpenAI"

fkorotkov — Thu, 09 Apr 2026 22:14:40 +0000

I agree! It’s a pity we didn’t make commercially successful.

New comment by fkorotkov in "Cirrus Labs to Join OpenAI"

fkorotkov — Thu, 09 Apr 2026 20:18:53 +0000

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.

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

fkorotkov — Thu, 05 Feb 2026 15:15:36 +0000

Hey HN — Omni Cache is a sidecar daemon for CI caching. It exposes multiple cache protocols on a local endpoint while storing blobs in S3‑compatible storage.

Instead of funneling traffic through a centralized cache proxy, each job talks directly to S3, avoiding a shared bottleneck as workloads scale. No extra ingress/egress traffic bills.

What it supports: - GitHub Actions cache v2 (used by Docker layer caching) - Bazel HTTP remote cache - Gradle build cache - Xcode/LLVM compilation cache - Custom HTTP clients

How it works: - Run it next to your CI job/runner; HTTP + gRPC on one local address - All built‑in protocols enabled by default - S3‑backed (AWS or any S3‑compatible storage) - Built‑in cache metrics endpoint and `omni-cache stats` - LocalStack dev mode for quick testing

This has powered billions of caching operations for Cirrus Runners/CI since 2017.

Repo: https://github.com/cirruslabs/omni-cache

I’d love feedback on: - Protocols you want next - CI/networking gotchas I should document - Metrics/observability you wish caches exposed

Comments URL: https://news.ycombinator.com/item?id=46900552

Points: 2

# Comments: 0

New comment by fkorotkov in "Show HN: Lume 0.2 – Build and Run macOS VMs with unattended setup"

fkorotkov — Mon, 19 Jan 2026 08:20:06 +0000

Can you elaborate on what got “broken” on Tahoe?

New comment by fkorotkov in "Pricing Changes for GitHub Actions"

fkorotkov — Tue, 16 Dec 2025 19:25:43 +0000

How much do you pay for the servers that run actions? Is it much more than $610? Then it kinda makes sense.

New comment by fkorotkov in "Pricing Changes for GitHub Actions"

fkorotkov — Tue, 16 Dec 2025 18:58:23 +0000

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.

New comment by fkorotkov in "New Pricing of self-hosted GitHub Actions Runners explained"

fkorotkov — Tue, 16 Dec 2025 18:40:48 +0000

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.

New Pricing of self-hosted GitHub Actions Runners explained

fkorotkov — Tue, 16 Dec 2025 18:40:48 +0000

Article URL: https://cirrus-runners.app/blog/2025/12/16/new-pricing-of-self-hosted-github-actions-runners-explained/

Comments URL: https://news.ycombinator.com/item?id=46292492

Points: 2

# Comments: 3

New comment by fkorotkov in "Show HN: Open-source x64 and Arm GitHub runners"

fkorotkov — Wed, 31 Jan 2024 10:08:36 +0000

Cirrus Runners being doing it for a long time now:

https://cirrus-runners.app/

New comment by fkorotkov in "3 to 10 times cheaper runners for GitHub Actions"

fkorotkov — Wed, 24 Jan 2024 19:35:43 +0000

There’s been a lot of conversations about moving off the traditional cloud for companies to save tremendously on infrastructure bills. Famously DHH and 37signals moved off AWS to their own hardware to save millions.

We are doing something similar with Cirrus Runners...

Cirrus Runners team controls, develops and optimizes every layer of the infrastructure involved, from provisioning the fastest bare-metal servers off traditional clouds to building state of the art virtualization solutions for macOS called Tart and for Linux called Vetu.

This vertical integration allows us to provide the most cost-efficient infrastructure for your GitHub Actions. Unlimited monthly usage for a fixed price. No hidden fees. No surprises.

3 to 10 times cheaper runners for GitHub Actions

fkorotkov — Wed, 24 Jan 2024 19:35:43 +0000

Article URL: https://cirrus-runners.app/

Comments URL: https://news.ycombinator.com/item?id=39121679

Points: 2

# Comments: 1

New comment by fkorotkov in "Tart: VMs on macOS using Apple's native Virtualization.Framework"

fkorotkov — Sun, 21 Jan 2024 15:11:02 +0000

Please check out and comment on this issue. There is some movement around but primary it’s waiting for the new promised Vagrant version in Go.

https://github.com/hashicorp/vagrant/issues/12760