If you spot an inaccuracy in this table, please let us know .
NixCI provides the exact command to reproduce each job locally, including for impure tests and deployments.
Every job on NixCI can be reproduced locally with a single command. NixCI shows you the exact command for each job, so when CI fails, you can start fixing it immediately on your machine.
Hercules CI builds are Nix-based so you can rebuild derivations locally, but it does not provide per-job repro commands.
NixCI reads your
flake.nix
and automatically discovers what to build.
All
configuration
is optional.
If it builds with
nix flake check
locally, it builds on NixCI.
Hercules CI requires installing and configuring a self-hosted agent before CI starts working.
NixCI automatically discovers all flake outputs and creates build jobs for them.
NixCI uses standard Nix flakes. Your build definition is your flake.nix, which works everywhere Nix does.
NixCI's hosted workers have 16 vCPUs and 64 GB of RAM, billed per second of actual build time. You can also bring your own workers with whatever hardware you choose.
Hercules CI requires self-hosted agents. You provision your own build machines.
NixCI integrates with GitLab.com via webhooks and commit status updates.
NixCI integrates with Codeberg.org via webhooks and commit status updates.
NixCI supports self-hosted Forgejo instances.
A single NixCI installation can serve GitHub, GitLab, and Codeberg repositories simultaneously.
NixCI works with GitHub , GitLab , and Codeberg . One CI system across all your forges.
NixCI supports self-hosted GitHub Enterprise instances.
NixCI supports self-hosted GitLab instances.
NixCI caches automatically without any configuration. Every build result is cached and subsequent builds pull from the cache to skip work that's already been done.
Hercules CI has no built-in binary cache. It supports Cachix and your own cache.
NixCI has built-in Cachix support. Just add your Cachix cache name to your configuration.
NixCI can push build results to your own binary cache via SSH.
NixCI can be fully self-hosted on your own infrastructure, including the leader, workers, and cache. It also works with self-hosted forges like GitLab and Forgejo.
Hercules CI self-hosting may be available for enterprise customers.
NixCI has built-in support for continuous deployment and impure tests with access to secrets and the network.
Hercules CI supports impure tests as effects.
NixCI automatically runs deployment after all builds and tests pass, with no manual dependency declaration needed.
NixCI does not have FlakeHub integration. FlakeHub only allows publishing from trusted platforms .