Hydra vs Inclavare Containers
Hydra
github.comInclavare Containers
github.comSide by side
| Figure | Hydra | Inclavare Containers |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | — |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Desktop Wallpaper Software | 8.7 (#5) | 7.7 (#14) |
| Integrations | Hydra jobset inputs can use Git checkout sources, and the documented examples use GitHub repositories. | The project documents integration with dockerd, containerd, and pouchd. |
| Purpose | Hydra is a continuous integration service for Nix based projects. | Inclavare Containers is a container runtime for launching protected containers in hardware-assisted Trusted Execution Environments (TEEs). |
Plans
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.
Inclavare Containers
Inclavare Containers is a free, open-source Linux container runtime for launching protected containers in hardware-assisted Trusted Execution Environments. It creates hardware-enforced isolation between a tenant workload and privileged cloud-provider software. Its Enclave Attestation Architecture provides remote attestation that sensitive workloads run on trusted TEE hardware. The rune component is described as compliant with the OCI Runtime specification, while documented integrations include dockerd, containerd, and pouchd. Deployment can use Occlum LibOS or WebAssembly Micro Runtime, and Rats-TLS provides an attested secured channel between heterogeneous TEEs. shim-rune handles enclave signing and management between containerd and rune; epm manages cache pools for enclave startup. The project is cloud-platform agnostic and can run on public-cloud Kubernetes platforms. It supports Kubernetes CRI, uses the OCI image format, and documents Linux hosts including Ubuntu 18.04 and Alibaba Linux 2. Installation is described through source builds or RPM/DEB repositories.