Overview
FourEyes gives you active-monitoring visibility into your network and the services that depend on it — without the per-test billing, opaque licensing, or UI clutter of commercial tools.
What it does
Section titled “What it does”- Runs active probes from lightweight nodes you place at PoPs, branches, cloud regions, or homelabs.
- Streams results to one self-hosted server over a single outbound mTLS connection per node.
- Stores, alerts on, correlates, and renders the data in a fast React UI, and exposes it via gRPC, REST, Prometheus, and OpenTelemetry.
Who it’s for
Section titled “Who it’s for”Network engineers, SRE/platform teams, NOC analysts, ISPs, and homelab operators who need synthetic-monitoring visibility but want to own the stack.
How it’s different
Section titled “How it’s different”| FourEyes | Commercial NMS | |
|---|---|---|
| Pricing | Free, self-hosted | Per-test-unit billing |
| Deployment | Two static Go binaries | Appliances / agents + SaaS |
| Nodes | Outbound-only, NAT-friendly | Often need inbound access |
| Config | GitOps (YAML + CLI) | Vendor portals |
| Distribution | Pre-built binaries for macOS & Linux | Closed-source appliances / SaaS |
Project status
Section titled “Project status”FourEyes is under active development. The probe registry, alerting, correlation, dashboards, GitOps, auto-mesh, signed self-update, Prometheus metrics, and OTLP metrics/traces export all ship today. See the Roadmap for what is explicitly not built yet.