Nfsen-ng
nfsen-ng is a modern in-place replacement for the ageing NfSen web frontend, built on the nfdump tool suite to visualise NetFlow, sFlow, and IPFIX traffic…
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.
74/100 Good
- Maintained
- 100last commit 28 days ago
- Popular
- 49290 GitHub stars
- Easy to install
- 201 install platform, Docker image
- Light to run
- 85512 MB minimum RAM
- Security check
- 100no serious findings, CI, tests
Availability: platform listings confirmed today, links checked 19 days ago
- GitHub stars
- 290
- Open issues
- 3
- Last commit
- 2026-10-24
- Latest release
- v1.0.0-beta.7
- License
- Apache-2.0
- Activity
- stale
Checked 6 days ago - source: GitHub (mbolli/nfsen-ng)
Resources & Compatibility
Minimum requirements: 512 MB RAM.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Collector Setup nfsen-ng is a display-only web UI and does not capture traffic itself. Install a separate nfdump collector (such as the companion nfsen-ng-nfcapd Unraid template) and mount both containers on the same appdata path so the UI can read the collector's data. A network device such as pfSense, OPNsense, or MikroTik must be configured to export NetFlow, sFlow, or IPFIX to the collector. source
- TLS Termination nfsen-ng does not terminate TLS by design. Front it with a reverse proxy such as SWAG, Nginx Proxy Manager, or Traefik to provide HTTPS. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I get flow data into nfsen-ng?
It only displays flow data that a collector has already written to its data directory. Use the companion nfsen-ng-nfcapd collector template or bundled Compose stack and mount both containers on the same appdata path.
Do I need to configure TLS in nfsen-ng?
No, the app does not terminate TLS by design. Front it with SWAG, Nginx Proxy Manager, or Traefik.
Is the MCP endpoint read-only?
Set NFSEN_MCP_HTTP=true to serve the same tools at /_mcp on nfsen-ng's own port. It does not create rules, trigger imports, or change settings.
Can nfsen-ng run in Docker?
A user describes using nfsen-ng for network devices and servers in Docker. They note that this makes configuration management and stack recreation easier.
Answers sourced from github.com, www.reddit.com
Community
- Lab monitoring? : r/homelab - Reddit (reddit)
- NFsen-ng intregration - Feature Requests - LibreNMS Community (other)
- Netflow / ipfix vizualisation in 2024? - LibreNMS Community (other)
- LibreNMS and nfsen (or other netflow...) : r/LibreNMS - Reddit (reddit)
Collected 49 days ago - public community threads