Ferrite

Ferrite is a self-hosted DNS server for your home or homelab network that blocks ads, trackers, and malware and routes selected traffic through a tunnel.

  • Network Services
  • Security
  • Tools & Utilities
Ferrite is a self-hosted DNS server for your home or homelab network that blocks ads, trackers, and malware and routes selected traffic through a tunnel. A Pi-hole-style sinkhole in one Rust binary that goes further: selective routing through built-in WireGuard (kernel-backed for line-rate throughput where the host allows it, with an in-process userspace fallback that needs nothing from the kernel), plus SOCKS5/Tor and a DPI-evasion path; encrypted upstream resolvers (DoH/DoT/DoQ) with DNSSEC forwarding; per-device query history keyed by MAC; a live query log and a web/API management surface with hot-reload.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

66/100 Good

Maintained
100last commit 10 days ago
Popular
2927 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM
Security check
90no serious findings, CI, tests, new single-developer project

Availability: platform listings confirmed today, links checked 22 days ago

GitHub stars
27
Open issues
0
Last commit
2026-11-11
Latest release
v0.2.1
License
MIT
Activity
rising

Checked 7 days ago - source: GitHub (syntlyx/ferrite-server)

Resources & Compatibility

Minimum requirements: 2 GB RAM.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Docker port mapping Docker publishes TCP and UDP with separate rules — keep both DNS rules on the same host/container port (53:53). If host port 80 is taken, keep the container on 80 and remap, e.g. -p 8080:80. source
  • Point devices at Ferrite Ferrite answers DNS for devices on your network; configure devices to use it as their DNS resolver. It runs as one process without root. source

Fetched 16 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Ferrite need root or a TUN device to use its built-in WireGuard routing?

No. Ferrite runs WireGuard in userspace using boringtun and smoltcp, fully in-process.

Can selected domains or whole devices be routed through SOCKS5 or Tor with DPI evasion?

Yes. Chosen domains or whole devices can go through WireGuard, SOCKS5, or Tor, with per-device TLS ClientHello/SNI fragmentation to defeat DPI.

How much memory does Ferrite use on an ARM board with a large blocklist?

It uses about 60 MB RSS on an ARM board serving 30 clients with a 1.8M-domain blocklist, with sub-2 ms cache and block decisions and tens of thousands of QPS.

Does Ferrite make outbound calls for updates or blocklists?

It performs an hourly GitHub check for updates and fetches configured blocklists. It does not send telemetry or query data off the box.

Can I set up a device profile that blocks everything except an allowlist?

Yes. Per-device profiles can be set to default-deny, blocking everything except an allowlist, while local network names keep resolving.

Answers sourced from github.com

Community

Collected 41 days ago - public community threads