Our cloud offering is for you!
CI
We build your Nix packages — and fast. Get GitHub checks, and nice logs on our website.
Hosting
We spin up VMs for your deployments, all with zero-downtime. Or see what a code change would look like with ephemeral PR deployments.
Cache
Everything you build gets uploaded to our cache, so CI never builds the same thing twice. And you can use our cache on your dev machines and servers too.
Actions
Purity is great, but sometimes you need effects: send a notification, start a deploy, or run an integration test against an external API. Actions allow you to do all of those, and more, easily.
Click
Push
Create a top-level flake.nix file and push it to your garnix-enabled repo.
“The thing I like the most about Garnix is how low friction is it. Add a flake.nix to your project, connect Garnix, and boom”
“The thing I like the most about Garnix is how low friction is it. Add a flake.nix to your project, connect Garnix, and boom”
Done
garnix will then kick off builds for all your packages and run your tests. If they pass, garnix will also deploy any servers you have.
Features
From automatic caching to fast, reproducible builds — everything in Garnix is designed to make your Nix workflow seamless.
- →Easy setup
Designed to work without any further tweaking. If you know Nix, you know garnix. - →Fast builds
garnix CI runs between 2-10x more quickly than alternatives based on GitHub Actions, even when using a Nix-specific cache, see our our benchmarks. Get your code to production quickly. - →Cache
garnix automatically caches all the build outputs. Not only does this make CI faster, it also speeds up local development, and functions as a binary source for your end users. - →Zero-downtime deploys
Get the highest standards of uptime without even thinking about uptime. On any commit, garnix spins up the new servers, waits for them to be ready, and then switches traffic to the new instances. Only then does it shut down old servers. - →Infrastructure-as-Code
With garnix, your git repo is the only source of truth. Everything can be configured there. A simple git diffcan always tell you what changed. - →Preview environments
See what a change would look like with our PR deployments. We keep the deployment up-to-date with the latest changes in a PR, and shut down the deployment after the PR is closed.