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.
The garnix lineage — continued by Solved.
Flake-native CI that ships with you.
{
description = "A sample Nix project";
outputs = { ... }:
{
checks = {
x86_64-linux.test = ...;
};
We build your Nix packages — and fast. Get GitHub checks, and nice logs on our website.
We spin up VMs for your deployments, all with zero-downtime. Or see what a code change would look like with ephemeral PR deployments.
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.
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.
Fork of garnix — backend, frontend, runners, hosting gateway. Self-host the full pipeline.
Deploy with NixOS modules and flakes. Local VM compose for development; production-ready modules for real clusters.
Point builders at your S3-compatible store. Keep artifacts inside your boundary.
Bring your own GitHub App credentials. Webhooks, checks, and repo access stay under your control.
Click. Push. Done.
Point Solved CI at a flake repo — we handle builds, cache, and deploys.
Sign up. Install the Solved CI GitHub App on the repositories you care about.
“Simple to install and manage.”
“Simple to install and manage.”
Create a top-level flake.nix and push it. We’ll evaluate packages, checks, and NixOS configurations.
“If it builds locally, it works in CI.”
“If it builds locally, it works in CI.”
Get GitHub checks, logs, a binary cache, and optional hosting — without a custom CI YAML novel.
“Nix-native from end to end.”
“Nix-native from end to end.”
garnix showed what Nix-native CI can feel like: install a GitHub App, push a
flake.nix, get checks, cache, and hosting. When the commercial service
wound down, the codebase was open-sourced. Solved is continuing
that work — maintaining the platform, hardening it for real ops, and enhancing
the product beyond the original release.