Hydra vs Runnable
Hydra
github.comRunnable
runnable.cloudSide by side
| Figure | Hydra | Runnable |
|---|---|---|
| Price from | Free | $5/mo |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 5 |
| Spec score · Continuous Integration Software | 8.5 (#11) | 7.3 (#48) |
| Integrations | Hydra jobset inputs can use Git checkout sources, and the documented examples use GitHub repositories. | Runnable documents GitHub, Cursor Origin, Entire, MCP, and a customer API. |
| Purpose | Hydra is a continuous integration service for Nix based projects. | Runnable executes existing GitHub Actions workflows with an independent scheduler and clean Linux machines. |
Plans
Runnable
- Hobby$5 a month
- Starter$29 a month
- Pro$99 a month
- Scale$299 a month
- EnterprisePriced on request
In their own words
Hydra
Hydra is a continuous integration service for projects based on Nix. It checks out project source periodically or continuously, builds it, runs tests, and produces reports. Work is organized into jobsets whose inputs can trigger builds when they change; jobsets can also depend on one another. Flake jobsets are supported when their outputs expose a hydraJobs attribute set. Jobs can produce packages, ISO images, or tarballs, and jobset inputs can use Git checkout sources. Hydra also provides a JSON API. It is aimed at Nix and NixOS package developers, not people who only need to use NixOS. Hydra is open source under GPL-3.0 and listed at free. It is self-hosted, with no hosted option listed, and running it is currently supported only on NixOS; the repository recommends the NixOS module for production. Flake evaluation is restricted from accessing files outside the Nix store. Some state is stored in the database, so backups are needed, and the wiki reports that hydra-queue-runner can sometimes leave queued builds unscheduled.