iTop review

iTop is open-source IT service management software built around a CMDB: a database for tracking IT assets, their relationships and dependencies. It connects that configuration data to service management, so teams can manage services, requests, incidents, problems and changes in one system rather than treating each as a separate workflow.

The feature list also includes a service catalog, tools for keeping users informed about requests and incidents, and automation for repetitive tasks. A low-code designer lets teams adapt the interface and data model. That flexibility may suit organizations whose processes do not fit a fixed service desk template, but it also means iTop is more than a basic ticket inbox: the value depends on whether you want to maintain a connected service and configuration model. iTop is the ITSM product from Combodo; it is unrelated to the consumer software discussed in some Reddit threads that use the same name.

The clearest case for iTop is a team that wants service workflows tied to its configuration data. Its feature set covers the core ITSM categories—services, requests, incidents, problems and changes—and connects service catalog entries to the CMDB. That gives teams a place to track not just a request, but the IT configurations and dependencies around it.

Other strengths listed for the product include:

• Low-code customization: Adapt the interface and data model with a designer, rather than relying only on fixed fields and workflows.
• Automation: Automate repetitive tasks, which can reduce manual handling where the workflows are a good fit.
• A free open-source edition: iTop Community is listed as free, making it an option to assess without a published subscription price.

The trade-off is that open source does not mean every team will find the system effortless to configure or operate. Still, for organizations that need a customizable ITSM and CMDB together, iTop’s range is more compelling than a request-only help desk.

Pricing is the main planning problem: monthly and annual prices are not published in the available pricing information. Atelier and Forge require custom quotes, so teams cannot compare the paid tiers on list price alone. The published pricing details are marked low confidence; confirm current terms with Combodo before budgeting.

The agent guidance also needs careful reading. Community is free, with up to 10 agents recommended—not stated as a hard cap. Atelier is described for teams with up to 50 agents, while Forge is for 50 or more. That leaves the 50-agent boundary overlapping, and the information does not clarify what happens at exactly 50 or whether other limits apply. A free trial is not listed.

The feature list describes broad customization and automation, but the available material does not specify their plan availability or limits. Do not assume every feature is included in every tier. Get a quote and confirm agent counts, included capabilities and any other plan restrictions before choosing a paid edition.

iTop Community is free and open source. The pricing information recommends it for small teams with up to 10 agents; that is a recommendation, not a stated hard cap.

Atelier is for teams with up to 50 agents, while Forge starts at 50 agents. Both require custom quotes, so the actual price difference between tiers—and whether the 50-agent boundary changes your cost—is not published. Get a quote before budgeting or choosing a tier.

Monthly and annual prices are not published. The published pricing information lists no add-ons, but that does not confirm that every service or extra is included in a quote. It also does not specify billing terms, such as contract length or whether pricing changes with agent count beyond the stated tiers.

The practical takeaway: Community has a clear $0 entry price; paid plans do not have public prices. Ask for a written quote that spells out agent limits, billing frequency, included services and any extra charges.

The available information describes iTop’s service-management features and low-code customization, but does not specify migration tools, supported import formats, data-export options or migration services. We can’t estimate the effort or confirm how easily records move in or out. Before switching, ask for a sample export and import process, and check whether your service catalog, CMDB relationships, request history and custom data can be transferred.

Customization is worth examining before you commit: iTop lets teams adapt its interface and data model with a low-code designer. The published material does not explain how those customizations export or behave in another system, so treat them as a potential migration workstream, not proof of lock-in.

The brief includes no Reddit posts or user reports, so we can’t attribute reasons for leaving to users. Data portability, custom-workflow transfer and paid-tier quotes are the gaps to resolve with Combodo before planning a move in either direction.