Garnix to shut down, open source its Nix CI as team joins Shopify

Why it matters

A Nix-native managed CI is going away, but its code is now available for the community to run. That both disrupts teams relying on Garnix's cache and macOS builders and signals growing big-company interest in Nix workflows. Users have a hard deadline to migrate or self-host by July 15, 2026.

Alex David, Soenke Hahn, and Julian K. Arni said they are joining Shopify and will shut down Garnix, their Nix-native CI/CD service, on July 15, 2026. In an email shared "as is" on NixOS Discourse, the team added that they are open sourcing the Garnix codebase at the garnix-io/garnix-ci repository and will delete all user data, including build artifacts, on the shutdown date.

The founders called the move "joining forces with Shopify" and thanked the Nix community for early support, noting their "Open Collective days" and years of feedback, per the email quoted on Discourse. The message did not describe deal terms or structure, and as of the post time, the Discourse user who surfaced the email said they could not find a notice on garnix.io.

What they built

David, Hahn, and Arni spent the last few years pushing a simple idea for Nix users: CI that speaks Nix out of the box. Garnix integrated via a GitHub App, watched for a top-level flake.nix, and then built packages, ran tests, uploaded every output to a binary cache, and could even provision and deploy servers with zero-downtime rollovers. Teams could wire in "Actions" for side effects like notifications and external integration tests. The company positioned Garnix as faster than pipelines assembled on top of GitHub Actions, pointing to benchmarks that claimed 2-10x speedups (benchmarks).

That Nix-first stance won advocates in the community and made Garnix a go-to hosted option for macOS and Linux binaries when teams did not want to maintain their own builders. One commenter on the Discourse thread lamented losing Garnix's macOS builds for a work laptop while praising how well it had worked for home-manager setups, underscoring the practical hole this shutdown will leave for some users.

What changes for users

Per the email quoted on Discourse:

• The hosted Garnix service will shut down on July 15, 2026.
• All user data, including build artifacts, will be deleted on the same date.
• The codebase is open sourced at the garnix-io/garnix-ci repository.
• The team invites anyone interested in running a public community instance to get in touch.

For teams that depended on Garnix's cache and builders, the open source release provides a path to self-host or to rally around a community-operated instance, even as the managed cloud winds down. The email encouraged users to download anything they want to keep before July 15.

The Shopify piece

The founders framed the next chapter as "joining forces with Shopify." The note does not specify whether this is an acquisition, acquihire, or another arrangement. It also does not include Garnix customer counts, revenue, or headcount. The immediate practical news is narrower: the managed service is ending, the code is available, and the Nix community is invited to pick up the torch on hosting.