Flamingo Raises $4.5M to Get MSPs Out of the Ticket Queue

Skip to content

LibreNMS review for MSPs and IT teams: features, limits, and fit

MSP Tools & Reviews
Open Source
Open Source MSP
June 29, 2026
2,424 views
LibreNMS review for MSPs and IT teams: features, limits, and fit

Release 26.10, Linux and Docker install steps, the 2026 permission changes, alert transports and ticketing hooks, a labor cost model, and head-to-heads with OpenNMS, Observium, Zabbix, Checkmk, PRTG and Nagios Core.


Updated: November 2026

TL;DR

QuestionShort answer
What is it?A free, open-source, SNMP-based network monitoring system, and the actively maintained fork of Observium.
What does it cost?Nothing in license fees. It runs under GPLv3 and is funded by community donations through Open Collective.
Does it do multi-tenancy?Not true multi-tenancy. You scope visibility with roles and device groups inside one shared instance, with no per-client portals or white-labeling.
What is the latest release?26.10.2, a bug fix release on October 21, 2026. A new .0 version ships every month.
How do you install it?On Ubuntu, Debian or a RHEL-based Linux server with PHP 8.4 or later, or with the official Docker image. There is no native Windows build.
Who does it fit?MSPs and in-house IT teams with solid Linux skills who want deep, vendor-agnostic network visibility and are fine self-hosting.
Who should look elsewhere?Teams that need turnkey per-client dashboards, PSA and billing hooks, or zero infrastructure to maintain.

LibreNMS is a free, open-source network monitoring system that auto-discovers routers, switches, firewalls and servers over SNMP, then graphs, alerts and reports on them from one self-hosted web interface. There are no license fees under GPLv3, so what an MSP or in-house IT team pays for is the Linux server and the hours spent keeping it running. The catch is the model: one instance, self-hosted, with client or department separation you build yourself out of roles and device groups.

What LibreNMS is, and what it costs

LibreNMS is a network monitoring system built on PHP, a MySQL-compatible database (MariaDB in the official install guide), and SNMP. It started as a fork of Observium back in 2013 and has become the more openly developed of the two. The project ships under the GPLv3 license, which means the full feature set is free. No license keys, no per-device tiers, no "contact sales" wall in front of the parts you want.

Funding comes from the community, not a vendor. LibreNMS runs an Open Collective page where sponsors and individual contributors cover hosting and infrastructure, with the books published in the open. That matters when you bet part of your monitoring on the tool. There is no company that can get acquired, hike prices, or sunset the product out from under you. The flip side: there is no vendor on the hook for your uptime and no account manager when a poller falls over. Free help runs through the community forum, Discord and GitHub issues, and for an SLA the project points to its partner Config Services Ltd, which sells SLA-backed support and consultancy.

The project itself is busy. The latest release, 26.10.2, shipped on October 21, 2026, two days after 26.10.0, and LibreNMS ships a new .0 version every month using calendar versioning (year.month), with bug fix releases in between. The GitHub repository sits near 5,000 stars with roughly 2,850 forks and a deep contributor list. For an open-source project with no commercial parent, that is a healthy pulse, and it is the single best signal that the tool will still be maintained next year.

Is LibreNMS free and open source?

Yes. The repository's license file says LibreNMS is covered by GPLv3, with exceptions for the third-party packages it bundles, so you can monitor any number of devices, change the code and use it commercially at no cost. GPLv3's source-sharing terms apply when you distribute the software, not when you run it, so hosting one modified instance that clients or staff log into does not oblige you to publish your changes. That is a looser position than the AGPLv3 used by OpenNMS Horizon and Zabbix, where letting users reach a modified version over a network also triggers the duty to offer its source.

Core features that matter for MSPs

Auto-discovery is the headline. Point LibreNMS at a network and it walks CDP, LLDP, FDP, OSPF, BGP, SNMP, and ARP to map devices on its own. For an MSP onboarding a new client site, that beats hand-entering switches and routers one at a time, and it keeps the map current as the network changes.

The device support is broad. Cisco, Juniper, HP, Arista, Fortinet, MikroTik, and hundreds of other vendors work out of the box through SNMP. If a client has it racked, LibreNMS can probably read it. The trade-off is the SNMP dependency itself: every device you want visibility on needs SNMP enabled and configured, which is fine for network gear and less fine for the modern cloud and SaaS surface that lives outside it.

Alerting is rule-based and flexible. You can route notifications to email, Slack, webhooks, and more, with conditions tuned per device group so a flapping access switch at one client does not bury the rest of your board. The rule engine supports thresholds, regex matches, and time-of-day windows, which is enough to keep a multi-client board sane once you invest the setup time. The cost of that flexibility is the setup time itself: out of the box the default rules are generic, and tuning them per client is a project, not a checkbox.

There is a full REST API, native iOS and Android apps, and a port-based billing module that meters bandwidth and generates transfer reports. That billing feature bills traffic, not clients, so do not confuse it with PSA invoicing. The API is the piece that earns its keep in an MSP context: it is how you pull device state into a dashboard your account managers can read, or push discovery from an onboarding script instead of clicking through the UI for every new client.

For dashboards, a common setup pairs LibreNMS with Grafana rather than living in the stock web UI. The integration is well-trodden, and Grafana is where you build the per-screen views a NOC wants. If you are weighing LibreNMS against the wider field, our network management software roundup lines up the contenders by detection speed.

Alerting transports and integrations

LibreNMS calls its notification targets transports, and the alert transport docs list more than 40 of them. They cover chat (Slack, Microsoft Teams, Discord, Matrix, Telegram), paging and on-call (PagerDuty, Opsgenie, VictorOps, Grafana OnCall, Pushover), SMS (Twilio, Clickatell, MessageBird), ticketing (Jira, Jira Service Management, Zendesk, GLPI, osTicket), and generic API, mail, syslog and SNMP trap transports for anything else. None of them targets ConnectWise, HaloPSA or Autotask, which the stack section below covers.

For an in-house IT team on an open-source helpdesk, the GLPI and osTicket transports open tickets directly, with no glue code. Our open-source ticketing roundup compares those desks if you are still choosing one.

Beyond alerting, LibreNMS hooks into the tools network teams already run: Oxidized, RANCID and Unimus for configuration backups, SmokePing for latency graphs, NfSen for flow data, and Nagios plugins for service checks that SNMP can't do. Sign-in works against LDAP, Active Directory or RADIUS, so staff use the accounts they already have.

The multi-tenancy question every MSP asks

Here is where MSP buyers need to read carefully, because the marketing shorthand and the reality diverge.

LibreNMS is single-instance with role-based access control. It is not multi-tenant the way a SaaS NMS like Auvik is. You create roles, assign permissions, and grant users access to specific devices or static device groups. A technician without broad view permissions sees only the devices you assign them. That is working access control, and for a small shop it can be enough.

What you do not get is tenant isolation. Every client lives in the same database and the same instance. There is no per-tenant administrator, no hard data partition between Client A and Client B, and no white-labeled portal you can hand a customer. The project spent 2026 rebuilding permissions: 26.3.0 added more granular permissions as groundwork for full role-based access control, 26.4.0 added auth roles management, 26.8.0 brought permissions to the API, and 26.10.0 enforces device permissions in the legacy API. Those changes tighten who sees what inside the instance, and none of the release notes adds tenant isolation. If your model depends on giving each client a branded dashboard with their data walled off, LibreNMS will fight you the whole way.

The common workaround is to name device groups by client and lean on naming conventions plus user roles to keep things tidy. It works until it does not. A misassigned device group, a shared dashboard, or a global alert template can expose one client's hostnames or topology to a technician who should only see another's. Nothing in the data model stops that, so the discipline has to come from your process, and process discipline degrades as a team grows and turns over.

Put plainly: LibreNMS treats your entire managed estate as one big network that you happen to administer on behalf of many clients. If that matches how your NOC already operates, the device-group approach is workable and people run real businesses on it. If you sell monitoring as a per-client product with its own login and logo, the gap is structural, not a setting you flip.

Where LibreNMS fits in an MSP stack

LibreNMS is an NMS, full stop. It watches network gear and tells you when something breaks or trends the wrong way. It is not an RMM, and it is not a PSA.

That means no native ticket sync to ConnectWise, HaloPSA, or Autotask, and no client billing integration. Alerts can fire into a webhook, so you can bridge to a PSA with your own glue code, but you are the one building and maintaining that bridge when an API changes. Remote client sites need a network path back to your server. The distributed poller docs say distributed polling is not meant for remote polling, because every poller connects straight to the central database, RRDCached and Redis. The documented pattern for remote sites is a site-to-site VPN, with a tinc guide in the docs, plus poller groups to keep each client's devices on the right poller. Each tunnel is one more moving part to babysit per location.

A common pattern is to run LibreNMS exactly this way: as the deep network-visibility layer underneath a separate RMM and PSA. It pairs naturally with an open-source stack, and our guide to Nagios alternatives covers the neighboring monitoring tools and how they hand off to each other.

If LibreNMS is replacing a commercial NMS, our SolarWinds alternatives guide covers the paid tools on the same shortlist.

LibreNMS for in-house IT teams

For an internal IT team, the multi-tenancy gap mostly disappears. One company is one tenant, so a single instance with device groups per site, building or department matches how the network is run, and roles keep the service desk on read-only views while network engineers own the alert rules. Active Directory or LDAP sign-in means a leaver can't log in once their directory account is disabled.

The trade-off is the same, scaled to one organization: the license is free, and someone on the team owns the server, the upgrades and the SNMP settings on every switch. LibreNMS fits a team with Linux skills and a network-heavy estate of switches, firewalls, wireless controllers and UPS units. A team that needs one tool for servers, applications and cloud services as well should compare it with Zabbix or Checkmk below, and keep an RMM for the laptops and desktops that SNMP doesn't reach, such as one from our open-source RMM roundup.

How to install LibreNMS

LibreNMS runs on Linux. The install guide covers Ubuntu 24.04 and 26.04, Debian 12 and 13, and RHEL 8, 9 and 10 derivatives such as Rocky Linux, AlmaLinux and Oracle Linux. You need PHP 8.4 or later (8.5 is recommended), MariaDB, and a web server, with NGINX recommended and Apache supported. There is no native Windows build, so a Windows-only shop runs it in a Linux VM or a container.

A package install follows the same steps on every supported distro:

  1. Install the packages, then create a librenms system user with /opt/librenms as its home.
  2. Clone the repository into /opt/librenms and set its permissions.
  3. As the librenms user, run ./scripts/composer_wrapper.php install --no-dev to install the PHP dependencies.
  4. Create the MariaDB database and configure PHP-FPM and NGINX or Apache.
  5. Enable the librenms-scheduler.timer systemd unit, which drives polling, discovery and maintenance jobs.
  6. Finish in the web installer at /install, then run ./validate.php as the librenms user before you add devices.

The Docker path is shorter. The project publishes an official image built on Alpine Linux with NGINX, and the example compose file in the librenms/docker repository starts LibreNMS alongside MariaDB, Redis, a dispatcher, syslog-ng and snmptrapd containers. sudo docker compose -f compose.yml up -d brings the stack up, with the web interface on port 8000. Containers suit a lab, a small client or an internal IT team that already runs Docker hosts, while a package install on a dedicated VM is easier to tune as device counts grow.

Size the first server before you add the second client. The distributed poller docs put a single poller at up to 1,000 or more devices, and past that point you add pollers that share one database, RRDCached and Redis, with the dispatcher service handing out work through poller groups.

What it really costs to run

The license is free. The tool is not.

Self-hosting LibreNMS means you own the whole stack: the Linux host, the MySQL database, SNMP configuration on every monitored device, version upgrades, and tuning when the poller starts falling behind. A single poller commonly handles north of a thousand devices, but getting there takes capacity planning and the occasional late night. A single-server install follows one documented guide, while a scaled-out deployment adds the dispatcher service, Redis, RRDCached and extra pollers that all share one database, which is a project in its own right.

LibreNMS is also resource-hungry. Reviewers flag high CPU use at scale and thin plugin documentation, and reporting is basic: tables export to CSV since 26.9.0, but a polished client-facing report is something you build in Grafana or another tool. None of that is fatal, but all of it is labor, and labor is the cost that does not show up on an invoice. The recurring chores are predictable: monthly version upgrades that occasionally break a template, database growth that needs pruning, SNMP credentials that drift when a client swaps hardware, and poller capacity that has to be watched as device counts climb. Each one is small. Together they are a part-time job.

For an MSP, the question is whether the engineering hours you pour into running LibreNMS cost less than a paid tool's subscription would. At high device counts the free tool often wins, because the subscription would scale with every endpoint while your labor stays roughly flat. For a lean team already stretched across clients, the hours can quietly outrun what Auvik or PRTG would charge, and the bill arrives as burnout and missed alerts instead of a line item.

To put numbers on it, start from the BLS median pay for network and computer systems administrators, $99,130 a year in May 2025, and add the 43% that benefits add to wages in private industry. That comes to about $68 an hour. If upkeep takes eight hours a month, an assumption to replace with your own, LibreNMS costs about $545 a month in labor before the server. That is more than PRTG's entry tier at $200 a month and far less than its top tier at $1,642, both billed annually, so the answer turns on how large an estate you would otherwise license.

That calculation is easy to get wrong, because the license line is visible and the labor line is not. Price both before you commit.

LibreNMS vs the alternatives

LibreNMS sits in a crowded field. The right comparison depends on whether you value zero license cost or zero maintenance, and whether per-client separation is a must-have.

ToolModelLicense costTrue multi-tenantSelf-hostBest fit
LibreNMSOpen source (GPLv3)FreeNo (RBAC + device groups)YesDeep SNMP visibility, Linux-comfortable teams
AuvikCommercial SaaSPaid, per deviceYesNoMSPs that want turnkey per-client monitoring
ZabbixOpen sourceFree (paid support)PartialYesAll-purpose monitoring beyond just the network
PRTGCommercialPaid, sensor-basedLimitedYesSmall teams that want polish over tinkering
ObserviumFreemiumFree / paid ProNoYesThe lighter parent project LibreNMS forked
CheckmkOpen coreFree Community / paidPartialYesFast agent-based discovery, lower CPU
OpenNMSOpen sourceFree (paid support)PartialYesEnterprise-grade event and flow management
NagiosOpen coreFree Core / paid XINoYesPlugin-driven checks, heavy DIY

The standout contrast for MSPs is Auvik. It is the commercial, cloud, purpose-built-multi-tenant answer to everything LibreNMS makes you assemble yourself: automated topology, per-client dashboards, and no servers to patch. You pay for that, per device, every month. LibreNMS flips every one of those terms. That is the real decision, and it is less about features than about who you want maintaining the machine.

Among the open-source options, Zabbix is the natural cross-shop. It monitors far more than the network, so teams that want one tool for servers, applications, and switches often land there, at the cost of a steeper configuration curve than network-focused LibreNMS. Checkmk is worth a look if CPU load and discovery speed are pain points, since its agent-based model tends to be lighter than polling everything over SNMP. Observium, the project LibreNMS forked, is the lighter and more locked-down sibling, with its better features gated behind a paid tier. None of the free editions solve the multi-tenancy gap either. Checkmk sells it as a separate paid edition, which is the tell that per-client isolation is a commercial feature, not a community one.

LibreNMS comes up constantly in these replacement threads, and so do its limits:

LibreNMS vs OpenNMS

OpenNMS Horizon is the free edition, open source under AGPLv3, with Horizon 36.0.5 released on October 14, 2026. Meridian is the supported subscription edition, listed in November 2026 at $6,000 a year for Basic up to $66,000 a year for Premier. Where LibreNMS starts from SNMP auto-discovery and graphs, OpenNMS is built around event and fault management, service monitoring and flow data. It also has a remote-site answer LibreNMS lacks: Minions, collectors that run behind a client's firewall and NAT and report to the core over ActiveMQ or Kafka.

The trade-off is weight. OpenNMS is a larger Java platform to install and tune, so LibreNMS stays quicker to stand up for a network-first team, while OpenNMS suits larger estates that need remote collection without a VPN per site. Our OpenNMS profile has the project details.

LibreNMS vs Observium

LibreNMS began in 2013 as a fork of Observium, so the two share an SNMP-first design and a similar interface. The difference is how they are developed and paid for. Observium Community Edition is free but gets a release every six to twelve months, while Professional (£250 a year) and Enterprise (£1,500 a year) get daily updates, and Professional is free for registered charities and open-source projects.

LibreNMS keeps every feature in the free GPLv3 build, ships monthly, and takes pull requests from anyone. Pick Observium if you would rather pay a small fee for a vendor-curated build; pick LibreNMS if you want the full feature set at no cost and are comfortable with a community project. Our Observium profile covers its editions.

LibreNMS vs Zabbix

Zabbix is open source under AGPLv3, with 7.4 as the latest stable branch and 8.0 in release candidates as of November 2026. It monitors servers, applications, cloud services and networks through agents, SNMP and templates, so it covers more ground than LibreNMS. Zabbix proxies collect data at remote sites and forward it to the server, which replaces the VPN-per-site pattern LibreNMS needs.

The cost is configuration. Zabbix asks you to pick templates and tune triggers, where LibreNMS auto-discovers network gear and starts graphing with less setup. If the job is the network, LibreNMS gets there with less work; if it is the whole estate, Zabbix is the stronger fit, and our Zabbix review goes deeper. Network engineers weigh the same trade-off in this thread:

LibreNMS vs Checkmk

Checkmk now ships as Checkmk Community, a free GPLv2 edition the vendor positions for up to about 100 hosts, and paid Pro and Ultimate editions, with Ultimate listed from €275 a month billed annually. Checkmk Ultimate with Multi-Tenancy adds central management of customers with strict data separation, and Checkmk Cloud is the SaaS option. It combines agents and SNMP and discovers the services on each host, so it covers servers and applications as well as the network.

For an MSP, the multi-tenancy edition is the clearest contrast: Checkmk sells the client separation LibreNMS leaves you to build, while LibreNMS gives you the network depth for free. Our Checkmk review compares the editions.

LibreNMS vs PRTG

PRTG is commercial monitoring from Paessler, licensed by sensor rather than by device, with a free edition of up to 100 sensors and paid tiers from $200 to $1,642 a month billed annually, per our PRTG review in November 2026. Its core server runs on Windows, and it ships a polished console, maps and reports that take less setup than a self-hosted Linux stack. Remote probes cover client sites without a VPN.

LibreNMS has no sensor meter, so device growth adds server load instead of subscription cost. On client separation the two are close: PRTG scopes each client through roles and permissions inside one database, much like LibreNMS device groups, so neither gives true tenant isolation without extra work.

LibreNMS vs Nagios Core

Nagios Core is open source under GPLv2, with 4.5.14 released on August 5, 2026, and Nagios XI is the commercial edition built on Core. Nagios runs checks: small plugins that return OK, warning or critical for a host or service, with everything defined in configuration files. LibreNMS discovers devices over SNMP and graphs every port and sensor it finds without per-check setup.

Nagios gives finer control over custom checks; LibreNMS gives network history and topology with far less configuration. The two can also coexist during a migration, because LibreNMS runs Nagios plugins as services and ships a Nagios-compatible alert transport. Our Nagios profile covers Core and XI.

What reviews and ratings say

LibreNMS has a light formal-review footprint, which is normal for an open-source tool whose users live on GitHub and the community forum rather than on B2B review sites.

On G2, LibreNMS held 4.7 out of 5 across 14 reviews as of June 2026, a strong score on a thin sample. There is no Capterra listing as of June 2026, and no Trustpilot review page for librenms.org. SourceForge carries a product listing with zero reviews, and PeerSpot ranks it around #18 in network monitoring with category mindshare that has slipped year over year as cloud tools pull buyer attention.

Read that the right way. A 4.7 from 14 people is not a broad market signal, it is a small group of operators who run the tool and like it. The reviews worth weighting are the ones from people describing your exact setup, and you will find those in r/networking and the LibreNMS community forum, not on a star-rating page. Go read three of those threads before you decide.

The call: who LibreNMS fits

LibreNMS is a strong pick for an MSP or in-house IT team with Linux depth, a network-heavy estate, and the discipline to run its own infrastructure. You get vendor-agnostic visibility, broad auto-discovery, and an active project, all with no license meter ticking. For a shop that already self-hosts and treats its managed estate as one network, it earns its place, and the savings grow with every device you add.

The teams that regret it are the ones that picked it for the price tag alone, without staffing the maintenance. Free software with no one assigned to run it becomes shelfware fast, and an unmonitored monitoring tool is worse than none, because it tells you everything is fine right up until it is not. If you adopt LibreNMS, name an owner on day one.

It is the wrong pick if you need per-client portals with isolated data, native PSA and billing integration, or a tool that someone else keeps running. Those are not bugs in LibreNMS. They are simply outside what an open-source NMS was built to do.

LibreNMS leaves endpoint management, ticketing and remote access to other tools, and that is the part of the stack OpenFrame covers. OpenMSP is published by Flamingo, which builds OpenFrame: open, AI-native infrastructure for IT and security with RMM, a native PSA and remote access in one platform. AI agents work inline: Fae resolves support requests and Mingo runs IT operations. It costs $1 per device a month with 10M AI tokens included, or $0.80 on annual billing, after a 14-day free trial.

LibreNMS proves you do not need a license budget to see your network clearly. Just count the second invoice before you celebrate the first: the hours your team spends keeping it alive. Price that in, and you will know whether free is cheap for your team.

Kristina Shkriabina

Content Marketing Lead

Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.

Related Content

Frequently Asked Questions

/blog/librenms-review

Loading related content and questions