i-doit
German CMDB and IT documentation, open source - European alternative based in Germany
Quick Overview
| Company | i-doit |
|---|---|
| Category | IT Service Management |
| Headquarters | Düsseldorf, Germany |
| EU/European | Yes - Germany |
| GDPR Compliant | Yes |
| Main Features | CMDB and IT documentation, Open source core, Dependency mapping |
| Pricing | Open source core + paid editions |
| Best For | Teams that need an accurate CMDB before they need a service desk |
| Replaces | ServiceNow CMDB, Device42, spreadsheets |
Detailed Review
i-doit is a German IT documentation and configuration management database from synetics in Düsseldorf, built around the thing most ITSM projects postpone and then discover they needed first: an accurate record of what exists and how it connects.
What Makes i-doit Stand Out
Most organisations buy a service desk and inherit an empty CMDB nobody fills in. i-doit inverts the order — documentation first, with an open-source core, so asset and dependency data can be built up before a ticketing platform is chosen or alongside one that already exists.
What the Platform Covers
Configuration database with object types, relations and dependency maps, documentation covering racks, networks, licences and contracts, integrations into monitoring and ticketing, and an API for everything else.
European Jurisdiction and Data Protection
synetics GmbH is based in Düsseldorf and the open-source core is self-hostable. For a CMDB — which by definition describes every system an organisation runs — self-hosting is the strongest answer to the jurisdiction question.
A service desk accumulates more than tickets: asset inventories, staff records, access rights and often the security incidents themselves. Under a European vendor that whole estate is processed under the GDPR by a company inside the same legal system as its customer.
Pricing
Open-source core free to self-host, with paid editions adding support and enterprise modules. The cheapest way to start building a real CMDB.
i-doit vs ServiceNow
Against ServiceNow CMDB, Device42, spreadsheets, the argument is rarely feature parity at the top end — ServiceNow will win a checklist. It is implementation cost, licensing model and jurisdiction. A European platform that a mid-sized organisation can actually finish deploying delivers more service management than a larger one that stays half-configured.
Who Should Use i-doit
i-doit suits IT teams that need documentation and dependency mapping accurate enough to trust, whether or not they have chosen a service desk.
Pros and Cons
Pros
- Open-source core, free to self-host
- Dependency mapping across the estate
- Documents racks, networks, licences and contracts
- Integrates into monitoring and ticketing
- German vendor, self-hostable data
Cons
- Not a service desk — no ticketing of its own
- Data quality depends on the discipline behind it
- Interface is functional rather than modern
- Paid editions needed for enterprise modules and support
Alternatives to i-doit
Looking for other European ITSM platforms? Here are the alternatives worth comparing:
Frequently Asked Questions
i-doit is based in Germany and operates under European data-protection rules including the GDPR. Ticket content, asset inventories and staff records stay under European jurisdiction rather than under US legislation.
i-doit is based in Germany. We list European ITSM platforms because a service desk holds an organisation's asset, access and incident data in one place.
Configuration database with object types, relations and dependency maps, documentation covering racks, networks, licences and contracts, integrations into monitoring and ticketing, and an API for everything else.
Open-source core free to self-host, with paid editions adding support and enterprise modules. The cheapest way to start building a real CMDB.
i-doit is a European alternative to ServiceNow CMDB, Device42, spreadsheets. The practical differences are implementation effort, licensing model and which jurisdiction your service data sits in.
Yes. i-doit covers the core ITIL service management processes — incident, request, problem and change management with a configuration database underneath. How much of ITIL you actually implement is a question about your organisation rather than about the tool.