Faro

Faro is an open-source, self-hosted DNS (Domain Name System) server built on CoreDNS that shows what every device on your network is doing.

  • Network Services
  • Tools & Utilities
Faro is an open-source, self-hosted DNS (Domain Name System) server built on CoreDNS that shows what every device on your network is doing. It combines per-device visibility, blocking and protection profiles, local DNS, encrypted upstreams with health checks and failover, and synchronized replicas in one interface, with no cloud account or tracking.

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.

49/100 Fair

Maintained
88last commit 62 days ago
Popular
176 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM

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

GitHub stars
6
Open issues
5
Last commit
2026-09-20
Latest release
v0.11.0
License
Apache-2.0
Activity
stale

Checked 9 days ago - source: GitHub (derek-diaz/Faro)

Resources & Compatibility

Minimum requirements: 16 GB RAM. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Set your Faro API key and collector URL In the FaroConfig section, replace the placeholders with your real app name, version, environment, API key, and collector URL (where Faro sends the data) before running the app. Without these, Faro cannot send monitoring data to the place where you view it. source
  • Add the faro package to pubspec.yaml Add the faro package under dependencies in pubspec.yaml, then let Flutter fetch the packages. If you skip this, the code that uses Faro will not build. source
  • Wrap the app so Faro can track it Turn on HTTP tracking with HttpOverrides and wrap your app widget with Faro's monitoring components. This is what lets Faro collect requests and user interactions, so your dashboard is not empty. source
  • Install Deploy with Docker Compose; requires no cloud account and includes no tracking. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need a cloud account to run Faro?

No. Faro requires no cloud account and includes no tracking.

How can I set different blocking rules for different devices?

Use Home as the default protection profile or assign separate profiles to selected devices. You can choose blocklists, schedule blocking hours, and add exact-domain allow or block exceptions from the interface.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads