Open source CMDB: Understand and organize IT better with i-doit

When an incident occurs, having to search through spreadsheets and track down colleagues to clarify responsibilities wastes valuable time. An open source CMDB like i-doit brings devices, applications, and their dependencies together in a centralized IT documentation system. This enables your team to quickly identify which systems are affected, who is responsible, and what needs to be considered during a planned change. Learn what i-doit Open can do and how i-doit Pro for IT teams enhances your documentation with reporting, automation, and seamless integration into monitoring and ticketing systems.

Table of contents

1. What an open source CMDB does for your IT
2. From a device list to an overview of your IT
3. How a CMDB supports IT administrators and leaders
4. i-doit Open: Getting started with an open source CMDB
5. Comparing i-doit Open and i-doit Pro for IT teams
6. The daily value of additional features (i-doit Pro)
7. Evaluating open source CMDB tools: Questions to guide your selection
8. Connecting IT documentation to monitoring and ticketing systems
9. Implementing an open source CMDB: Start small and expand systematically
10. Frequently asked questions about the open source CMDB i-doit
11. Implementing an open source CMDB improves collaboration

What an open source CMDB does for your IT

CMDB stands for "Configuration Management Database". It refers to a database that documents your IT components and their relationships. This includes, for example, servers, network devices, applications, and the services your IT organization provides to the business.

A simple example: Accounting works with an application. This application requires a database running on a virtual server. That virtual server, in turn, depends on a physical host. A CMDB makes these interdependencies transparent and easy to track.

"Open source" describes software licensing terms that allow users to inspect the source code, modify it, and distribute it under defined conditions. However, open source does not automatically mean free of charge: costs can still arise for such solutions, for example, for support, hosting, or additional services. With i-doit, a distinction is made between the open-source edition i-doit Open and the advanced offering i-doit Pro for IT teams.

From a device list to an overview of your IT

In a basic inventory list, you might find a server's name, its IP address, and its purchase date. While helpful for asset management, you typically need more answers when an outage strikes: Which applications are affected? Who is handling the issue? Which departments need to be notified?

This is precisely where the value of a CMDB lies. It connects technical details with responsibilities and dependencies. You can find further fundamentals and use cases on our page about the CMDB and its functions.

How a CMDB supports IT administrators and leaders

For administrators, the primary objective is getting fast access to reliable information. Anyone maintaining a server or troubleshooting an incident needs data on the system, its connections, and the responsible colleagues.

IT leaders view the exact same information from a different angle. For instance, they want to understand which systems support critical business processes and identify gaps in ownership. A shared documentation base serves both groups. It minimizes back-and-forth inquiries and simplifies task handovers. New team members do not have to ask individual colleagues to piece together dependencies.

Example: Preparing maintenance in the CMDB

A host is scheduled for an update over the weekend. The CMDB documents which virtual servers are running on it and which applications they deliver.

From this, the administrator can determine which systems might be affected during maintenance. The IT manager can then coordinate with the system owners to confirm whether the timeframe works.

Whether you use an open source CMDB or i-doit Pro for this: the documented relationships must be accurate so that your team can rely on them.

i-doit Open: Getting started with an open source CMDB

i-doit Open is the open-source edition of i-doit. It is tailored particularly to individual administrators looking to document a manageable IT environment.

The i-doit open source CMDB provides an entry point into the technical documentation of your infrastructure. It allows you to explore how a central documentation system should be structured and what information you actually need.

This is especially helpful if you currently rely primarily on spreadsheets. For example, you can start with a single location or application and document its associated components.

Our page on structured IT documentation also explains how to consolidate technical information effectively.

When i-doit Open fits your requirements

i-doit Open is a viable option if you are starting with a clearly defined documentation scope and the available features and interfaces cover your tasks.

Test this with a specific question: Can a colleague use your documentation to figure out which systems are needed for an application and who is responsible for them?

Day-to-day operations provide the best feedback. Ask your colleagues whether they can trace the relationships between assets. At the same time, you will see whether you need additional capabilities for data maintenance, reporting, or collaboration.

Comparing i-doit Open and i-doit Pro for IT teams

As soon as multiple colleagues collaborate on documentation, further questions arise: Who is allowed to modify data? How do you import existing inventories? How do you find missing details without opening every record individually?

i-doit Pro for IT teams expands upon the capabilities of the Open edition. This includes, among other things, advanced permissions management, reporting, and tools for editing larger datasets.

The daily value of additional features (i-doit Pro)

A CSV import helps transfer existing inventory data from spreadsheets. Bulk editing allows you to modify details for multiple objects at once, rather than having to update each object individually.

Reports let you filter for systems with specific attributes, for example. Granular permissions management supports the clear delegation of responsibilities among team members.

This keeps documentation usable and manageable even as your data grows. When choosing between an open source CMDB and i-doit Pro, the decisive factor is which tasks your team needs to handle on a regular basis.

Evaluating open source CMDB tools: Questions to guide your selection

A feature list alone does not show whether a solution fits into your day-to-day work. Use typical IT tasks to evaluate your options.

Can you model information the way you need it?

Pick an application that is used regularly within your organization. Document its associated servers, location, and owners.

Then have a colleague work with that documentation. Can they find the required information without extra explanation? Do they understand which components belong together?

Can you keep existing data up to date?

Define who records new systems and applies changes. Not all technical information has to be maintained manually: connected discovery tools like JDisc detect devices on the network and capture hardware details, operating systems, and installed software. This data can be imported into i-doit Pro and reconciled regularly.

For additional data sources, the API add-on makes it possible to read, write, and update information automatically. This allows you to enrich technical inventory data with details from other systems.

For synchronization to work reliably, you need unique identifiers and clear rules. Existing devices should be updated rather than created as duplicate records. In addition, specify which data source serves as the single source of truth in case of discrepancies.

Connecting IT documentation to monitoring and ticketing systems

During an incident, your team needs answers fast: Which system is affected? Which applications depend on it? Who is responsible? A well-maintained CMDB delivers this information and streamlines troubleshooting.

Integrating monitoring tools allows you to pair documented systems with real-time status information. If monitoring reports an outage, the relationships in the CMDB help identify affected applications and services. This enables your team to better assess which incident needs to be prioritized.

Connecting to a service desk or ticketing system adds crucial context for support teams. When a ticket is linked to the affected device or system, agents can pull relevant information directly from the IT documentation. This cuts down on unnecessary inquiries and smooths out handoffs between colleagues.

These relationships are equally valuable for planned changes. Before updating a server, for example, you can check which applications depend on it and which stakeholders need to be involved. This facilitates preparation and helps prevent avoidable downtime.

With the right integrations, i-doit becomes the unified source of truth for operations and support. Learn more about these capabilities on our page about IT service management with i-doit.

Implementing an open source CMDB: Start small and expand systematically

You do not have to document your entire infrastructure all at once. Start with an area where missing information currently wastes the most time.

Begin by recording the most critical attributes: name, unique identifier, status, location, and owner. Then, add the relationships required for your specific use case.

Agree as a team on when documentation must be updated. A new system should be documented during commissioning. If equipment is relocated, update location details; when it is decommissioned, adjust its status.

Even with an open source CMDB, ongoing operations must be factored into your planning. Updates, backups, and data maintenance all require time. Therefore, alongside licensing costs, compare the workload and the level of support your team will need.

Frequently asked questions about the open source CMDB i-doit

When is i-doit Open sufficient – and when is i-doit Pro worth it?

i-doit Open is ideal for getting started if you want to document a manageable IT environment. i-doit Pro becomes relevant as soon as you need to import data via CSV, edit multiple objects at once, or create custom reports. Detailed permissions management and additional integrations also make a compelling case for IT teams.

Are devices and applications discovered automatically?

A CMDB does not automatically discover your infrastructure on its own. For this, inventory and discovery tools are integrated to capture technical details and transfer them to the CMDB. In i-doit Pro, automated data ingestion can be configured using matching interfaces and extensions. Responsibilities and business context still need to be maintained alongside it.

Can a CMDB replace existing Excel spreadsheets?

Yes. A CMDB brings scattered information together in one central place and enriches it with relationships between devices, applications, and owners. Existing spreadsheets can serve as a baseline and be imported via CSV into i-doit Pro. Before importing, make sure to clean up duplicate entries and inconsistent naming conventions.

How do you keep IT documentation up to date?

The best approach is to update documentation directly during commissioning, change, or decommissioning of a system. Establish clear responsibilities and automate the ingestion of suitable technical data. Regular audits help uncover missing details and outdated relationships.

Implementing an open source CMDB improves collaboration

An open source CMDB can be your gateway to centralized IT documentation. i-doit Open helps you document your infrastructure in a structured way and make initial relationships visible.

With i-doit Pro for IT teams, you expand this foundation: permissions management, reporting, bulk data editing, and tailored integrations support seamless collaboration. Administrators find the information they need for operations and support, while IT managers gain a clear overview of systems and ownership.

Put your IT documentation on a shared foundation: Discover the CMDB solution from i-doit and see firsthand with your own infrastructure how it simplifies your team's day-to-day work.

Test i-doit group software productively now.

The i-doit group is the leading software manufacturer for IT documentation, CMDB, ITSM & cabling management, as well as for ISMS, emergency management & data protection. Over 2,000 active customers trust us for their digital resilience.

Test for 30 days!