Free CMDB Tools in 2026: NetBox, GLPI, iTop Compared
A practical guide to free and open-source CMDB and asset tools — NetBox, GLPI, iTop, i-doit, Snipe-IT, Ralph and OCS Inventory — with a checked comparison table.
Looking for a free or open-source CMDB in 2026? There are mature options. NetBox, GLPI, iTop, i-doit (open edition), Snipe-IT, Ralph and OCS Inventory all cost nothing to license. They solve different problems, though: some model network infrastructure, some run a full service desk, and some track hardware assets. This guide explains what each tool is built for, compares them side by side and lists what to check before you choose.
Try the free CMDB health check →
CMDB vs Asset Management
Asset management tracks *what you own*: laptops, servers, licences. A CMDB (configuration management database) tracks *how things relate*: this application runs on this virtual machine, which depends on this database. Relationship data is what makes incident routing and change impact analysis possible. Several tools below are excellent asset trackers but are not designed as relationship-centred CMDBs, so match the tool to the job.
What Changed for CMDBs in 2026
- Short-lived cloud resources: containers and serverless functions make manual CI entry impractical. Tools need API-based discovery or integration-driven updates.
- AI-assisted operations: incident tools increasingly use CI relationships to suggest responders and impact, so stale CMDB data now degrades AI suggestions directly.
- Security scrutiny: self-hosted tools need patching, SSO and audit logs, and auditors ask who maintains them.
- Consolidation: many teams want CMDB, incident and change in one place rather than separate tools connected by scripts.
- Data residency: European teams increasingly ask where CI data is stored — see GDPR-compliant ITSM in Europe.
Open-Source and Free CMDB Tools Compared
| Tool | Best for | Licence | Hosting | Built-in discovery | Official site |
|---|---|---|---|---|---|
| NetBox | IPAM / DCIM (network and infrastructure source of truth) | Apache 2.0 | Self-hosted; paid cloud from NetBox Labs | Add-on | netboxlabs.com/docs |
| GLPI | Full ITSM with CMDB and asset inventory | GPL v3 | Self-hosted; paid cloud from Teclib | Yes (native inventory) | glpi-project.org |
| iTop | CMDB with ITSM | AGPL v3 | Self-hosted | Add-on (data collectors) | combodo.com/itop |
| i-doit (open edition) | CMDB and IT documentation | Self-hosted | Add-on | i-doit.org | |
| Snipe-IT | Asset inventory (hardware and licences) | AGPL v3 | Self-hosted; paid hosting from Grokability | No (import / API) | snipeitapp.com |
| Ralph | Asset inventory and DCIM for data centres | Apache 2.0 | Self-hosted | github.com/allegro/ralph | |
| OCS Inventory NG | Asset inventory | GPL v2 | Self-hosted | Yes (agents, network discovery, SNMP) | ocsinventory-ng.org |
*Last checked: October 2026.* Licences were checked against each project's published licence file; capabilities against the project's own site. Cells we could not verify are left blank. Features and licences change, so confirm with each project before adopting.
Tool-by-Tool
NetBox
NetBox is widely used as the source of truth for networks and infrastructure: IP address management (IPAM), data centre infrastructure (DCIM), circuits and devices, with a strong API for network automation. It is not a service desk, so incidents and changes live in another tool that reads from it.
GLPI
GLPI combines service desk, asset management and a CMDB in one open-source package, with native inventory for collecting hardware and software data. It suits teams that want ITSM and CMDB together and can invest time in configuration and version upgrades.
iTop
iTop has a detailed ITIL-oriented data model with flexible CI classes and impact analysis views. It fits teams for whom relationship modelling matters most. Automated population usually relies on data collector extensions.
i-doit (open edition)
i-doit is popular in German-speaking markets for IT documentation and CMDB. The open edition suits smaller estates; check which features sit in the paid editions before planning around them.
Snipe-IT
Snipe-IT is a clean, focused tool for tracking hardware, licences and accessories, including check-in and check-out. It is an asset tracker rather than a relationship-centred CMDB, and many teams pair it with a separate incident tool.
Ralph
Ralph, originally built at Allegro, manages data centre and back-office assets: racks, servers, networks and their lifecycle. It is a good fit for infrastructure-heavy teams comfortable running a Python/Django application.
OCS Inventory NG
OCS Inventory collects hardware and software inventory through agents and can scan the network for devices that cannot run an agent. It is commonly paired with GLPI, which can use it as an inventory source.
Open-Source vs Free Tiers of Commercial Tools
"Free" covers two different things. Open-source tools (NetBox, GLPI, iTop, Snipe-IT, Ralph, OCS Inventory) give you the code under a licence such as Apache, GPL or AGPL: you can self-host, modify and keep using them indefinitely, but you run the servers, upgrades and security yourself. Free tiers of commercial products are hosted for you but are usually capped by users, assets or features, and the vendor decides what stays free. Open source gives you control and portability; a free tier gives you less to operate. Read the licence (especially AGPL if you plan to modify and expose the tool) and the free tier's limits before committing.
NetBox vs GLPI: Which to Choose
- Choose NetBox when your main problem is modelling networks and infrastructure — IP space, racks, cabling, devices — and you want an API-driven source of truth that automation can read and write.
- Choose GLPI when you need a service desk and asset inventory together, with tickets, a CMDB and native inventory in one product.
- Use both when network engineering and IT service management are separate teams: NetBox as the infrastructure record, GLPI or another ITSM tool for tickets and changes, connected through their APIs.
When a Spreadsheet CMDB Stops Working
A spreadsheet is a reasonable starting point for a small estate. Signs it has stopped working:
- Several copies exist and nobody knows which one is current.
- Relationships (what depends on what) live in people's heads rather than in the sheet.
- Cloud resources appear and disappear faster than anyone updates the rows.
- During an incident, nobody can quickly answer what else a failing component affects.
- An auditor asks what was running on a given date and the answer takes days to assemble.
What to Check Before Choosing
- Discovery: can the tool populate CIs automatically (agent, network scan, cloud API), or will every record be entered by hand?
- Relationships: can you model services, applications, infrastructure and their dependencies, and see impact when one fails?
- API: is there a documented API for imports, integrations and automation?
- ITSM integration: does it connect to the tools where incidents and changes are handled, or include them?
- Upkeep effort: who will host, patch, back up and upgrade it, and how many hours a month can they give it?
How to Run a Free CMDB Well
Teams that succeed with open-source CMDBs tend to do five things deliberately:
1. Pick one system of record. If CIs also live in a spreadsheet, the spreadsheet wins and the CMDB dies. Decide on day one which tool is authoritative.
2. Automate intake before you widen scope. Get one reliable feed — cloud inventory, endpoint agent or monitoring — writing CIs automatically before adding more CI classes by hand.
3. Model the services you actually govern. A small number of well-owned services is more useful than thousands of orphaned CIs. Each service needs an owner, a support group and an escalation path.
4. Schedule reconciliation like a backup job. A recurring task to find CIs with no owner, no recent update or no relationships keeps data trustworthy.
5. Name the maintainer. Free CMDBs fail when ownership is collective. One named person with allocated hours keeps it alive.
How to Run a Two-Week Pilot
Before committing, run a short, structured pilot so the decision is based on your data rather than a feature list:
- Days 1–2: deploy the tool on a test VM with backups and SSO if supported. Record the hours spent.
- Days 3–5: model three real business services end to end — for example email, ERP and your client portal — including applications, servers, databases and third parties.
- Days 6–8: connect one data source (endpoint inventory, cloud API or network scan) and see how much of the model updates automatically.
- Days 9–10: simulate an incident and a change. Can you see what depends on the failing component? Can a change approver see impacted services?
- Days 11–14: check data freshness. How many records went stale during the pilot, and who would own updates?
Score each tool on setup effort, relationship quality, automation, incident and change usefulness, and maintenance burden.
Security Checklist for Self-Hosted CMDBs
A CMDB is a map of your estate, which makes it a valuable target. Put it behind SSO or enforce strong passwords and MFA, keep it off the public internet or behind a VPN, patch the application and its database on a fixed schedule, encrypt backups and test restores, restrict API tokens to the integrations that need them, and log administrative changes. Assign a named owner and document the patch cadence, because auditors ask.
Keeping Your Options Open
Many teams start with a free tool and move later. Make that easier from day one: use consistent naming for services and CIs, keep an owner and support group on every service, avoid over-customising classes, export regularly to CSV, and document which integrations feed which CI types. The services, owners and relationships you model are the valuable part — the tool itself is replaceable.
When to Move to a Paid or Enterprise CMDB
Free tools stop being the cheapest option when nobody has time to run them. Before you shortlist paid CMDB vendors, pin down what matters for your team:
- Discovery — agent, agentless or both; on-premises, cloud and hybrid coverage.
- Dependency mapping — a flat list of CIs, or upstream and downstream service relationships.
- Incident and change links — whether CIs are updated from live incident and change work or from batch imports.
- Pricing model — flat plan, per agent, per asset, per device or on quote.
- Rollout — whether the tool is usable in weeks or needs a larger platform programme.
- Extensibility — API, webhooks and custom CI types.
- Compliance — SSO, roles, audit logs and data-residency options.
Paid mid-market CMDB tools
- Freshservice publishes ITSM pricing per agent per month, and lists CMDB in its IT Asset Management Growth, Pro and Enterprise packages (checked October 2026): Freshservice ITSM pricing and Freshservice ITAM pricing. A natural fit if you already run Freshservice.
- Jira Service Management Assets is part of Atlassian Service Collection; Atlassian states that asset and configuration management is included from the Standard plan, with objects counting toward usage allowances (checked October 2026): Service Collection pricing and Assets licensing.
- Device42 prices as an annual subscription based on device count, without public dollar amounts (checked October 2026): Device42 pricing. Best evaluated as a discovery-led CMDB that feeds an ITSM tool.
- Lansweeper publishes asset-based annual plans, including a free plan for small estates (checked October 2026): Lansweeper pricing. Strong for inventory; pair it with an ITSM tool for incident and change work.
- SLAShield includes CMDB Lite on Growth ($799/month, up to 500 CIs, manual dependency mapping, CSV import and export, CIs linked to incidents) and the full CMDB on Professional+ ($4,999/month or $49,990/year, dependency mapping, asset management and license tracking). Growth ready within 1 business day of your request (Mon–Fri); Professional access within 1 business day of payment, go-live 3–5 weeks.
Enterprise CMDB tools
ServiceNow CMDB, BMC Helix CMDB and Ivanti Neurons for ITSM are built for very large estates and governed platform operations. All three price on request, and cost depends on modules, CI volume and services. If one of them is already your platform of record, extending it is usually the simpler path.
Which route fits
- Small team, strong platform skills, wants control → a free tool from the comparison above.
- Simple estate, ITSM or discovery is the bigger need → Freshservice or Lansweeper.
- Discovery-heavy hybrid estate with ITSM already in place → Device42 or Lansweeper alongside it.
- Mid-market team that wants CMDB inside incident and change work on one plan → compare SLAShield and Freshservice using your real incident and change workflows.
- Already on ServiceNow, BMC or Ivanti → extend the existing platform.
Frequently Asked Questions
Q: What is the best free CMDB?
It depends on the job. For a full service desk with CMDB, GLPI is the most complete open-source package; for ITIL-style relationship modelling, iTop; for network and infrastructure, NetBox; for hardware and licence tracking, Snipe-IT.
Q: Is NetBox a CMDB?
NetBox describes itself as a source of truth for network and infrastructure — IPAM and DCIM. Many teams use it as the infrastructure part of their CMDB, but it is not a service desk, so incidents and changes are handled in another tool. See the NetBox documentation.
Q: Is GLPI free?
Yes. GLPI is open source under the GPL v3 licence and free to self-host. Teclib, the company behind GLPI, also sells hosted and supported plans. See glpi-project.org.
Q: Is there an open-source CMDB with discovery?
Yes. GLPI includes native inventory, and OCS Inventory NG discovers devices through agents, network scans and SNMP. NetBox, iTop and i-doit offer discovery through add-ons.
Where SLAShield Fits
SLAShield is a paid incident management platform, not a free or open-source CMDB. Its Growth plan includes CMDB Lite (up to 500 CIs, manual dependency mapping, CSV import/export) with CIs linked to incidents; Professional+ includes full CMDB with dependency mapping, asset management and license tracking. Auto-discovery and impact analysis are on the roadmap, not available today. If you would rather not host and maintain a separate CMDB, see what Growth and Professional include on the pricing page; if you prefer to self-host, the tools above are solid choices.