Firelink vs Hydra

Firelink is a free desktop download manager for direct files, browser handoffs, media, playlists, torrents and scheduled queues. It supports segmented HTTP and HTTPS downloads with retries, speed limits, connection controls and adaptive mirror selection. Queues can be paused, resumed, retried, redownloaded and scheduled. Bundled yt-dlp, FFmpeg and Deno support media and playlist downloads, including direct HLS, DASH and Smooth Streaming manifest URLs; DRM and other protected-key workflows are not supported, and subtitle or multiple-audio-track selection is not exposed in the current phase.

The Firelink Companion can send browser downloads, selected links, media pages and torrent information to the desktop app for review. It supports Firefox and Chromium Manifest V3, with Edge installation through Microsoft Edge Add-ons and a release ZIP for other Chromium browsers. The extension says download data stays local. Firelink is available for macOS, Windows and Linux under the MIT License. The macOS package is ad-hoc signed and not notarized, the Windows installer is unsigned, and the current Linux AppImage requires glibc 2.35 or newer.

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.