What does ITSM cost when you build, partner or buy SaaS?
The software license is not the main cost in any of the three models. Whether you run GLPI or iTop yourself, bring in a partner, or pay a per-agent SaaS fee, the total depends on scope, agent count, CMDB depth and who operates the platform day to day. The license line is often the smallest and most visible number, which is why it dominates early comparisons. Before you compare anything, write down your headcount of agents (people who work tickets), your device and software asset count, the integrations you need with identity and monitoring, and whether your team can run the platform after go-live.
Some reference points exist. GLPI Network lists a public cloud price of 19 euros per user per month and a private cloud price of 21 euros per user per month with a 25-user minimum, and self-hosted subscriptions from 100 euros per month (Basic, up to 10 agents and 500 assets) to 4,500 euros per month (Enterprise), according to the GLPI Network subscriptions page. Combodo offers iTop Community free for up to 10 agents, per Combodo iTop. Freshservice's pricing page, as read in October 2026, lists Starter at $19, Growth at $49 and Pro at $99 per agent per month billed annually, with Enterprise by quote and 100 IT asset management units per plan (Freshservice pricing). These are list prices from different vendors with different feature sets, so treat them as anchors, not as a comparison of equal scope.
The costs that do not appear on those pages are the ones to budget for. In a self-hosted build, you pay for infrastructure, the one-time CMDB model and process configuration, agent rollout to every device, data migration from spreadsheets or an older desk, and ongoing administration, backups and upgrades. In a partner model, you pay for those services in a fixed-scope quote, then decide between internal administration and a support retainer. In a SaaS model, per-agent fees recur with headcount, and you should ask how asset units, extra sandboxes, integrations and data export are priced. Ask every vendor or partner for a written quote that separates one-time work from recurring fees and states who performs each task.
Which cost components sit with you, a partner or the vendor?
This table compares who pays for each ITSM cost component under an in-house build, an implementation partner, and a per-agent SaaS service desk, and marks each as one-time or recurring. Read the first column for the component, then across for who carries it. SaaS list prices come from the Freshservice pricing page as read in October 2026, and self-hosted subscription tiers come from the GLPI Network subscriptions page.
| Cost component | In-house build (self-hosted GLPI or iTop) | Implementation partner (self-hosted, fixed scope) | Per-agent SaaS (Freshservice list pricing) |
|---|---|---|---|
| Platform license or subscription | Open-source licence costs nothing; optional vendor support is a recurring subscription you buy directly | Open-source licence costs nothing; partner may resell or advise on support tiers, recurring | Recurring per agent per month; Starter, Growth and Pro were listed at $19, $49 and $99 billed annually |
| Hosting and infrastructure | Recurring: servers, database, backups and storage in your own cloud or data center | Recurring, paid to you or your cloud provider; partner sizes and documents the stack | Included in the subscription; data residency and asset-unit overage to confirm |
| CMDB and process configuration | One-time build by your staff, plus ongoing model changes | One-time, fixed scope agreed in writing before work starts | One-time configuration by your team or vendor services; confirm what is included |
| Agent rollout (inventory agents) | One-time deployment effort across Windows, macOS and Linux, then recurring agent updates | One-time, scoped by device count and platforms; agents are the GLPI Agent, which is open source | Vendor or your agent deployment; confirm device and asset-unit limits |
| Data migration | One-time, staff time for extraction, cleansing and reconciliation | One-time, scoped to source systems and record volumes named in the quote | One-time, usually through import tooling; confirm migration assistance and fees |
| Integrations (identity, monitoring, procurement) | One-time build plus recurring maintenance when connected systems change | One-time build with documented interfaces; recurring support if you retain the partner | Connectors listed by the vendor; custom integrations may be extra and recurring |
| Training | One-time, staff time and internal enablement | One-time, included in scope or quoted separately | Vendor documentation and training; confirm whether paid tiers add formal training |
| Ongoing administration and upgrades | Recurring internal staff time; GLPI upgrades require database and config backups and plugin reactivation | Recurring if you buy a retainer; otherwise internal staff continue the work | Largely vendor-managed; you still pay for admin roles, configuration changes and integration upkeep |
What moves the ITSM cost up or down?
Most ITSM cost lines scale with a small set of inputs: who uses the desk, how many assets and classes the CMDB holds, and how much integration and migration work sits around it. The cards below explain which way each driver moves the total under self-hosted GLPI or iTop, and under per-agent SaaS, so you can check the quote against the same inputs.
Agent and user count
Per-agent SaaS pricing multiplies directly with the number of technicians who need a licensed seat, so the subscription grows in step with every hire. A self-hosted GLPI or iTop install has no per-seat license fee, but the support subscription tiers and the infrastructure size still follow the number of users. Count named technicians, approvers and read-only console users separately, because vendors often price them differently. Ask whether requesters who only submit tickets through a portal need a paid seat.
Asset count and allowance packs
Many SaaS ITSM plans include a fixed allowance of IT asset management units, then sell more in blocks. Freshservice's October 2026 pricing page includes 100 asset units per plan and sells additional units in packs of 500, so an estate that grows past the allowance adds cost in steps. Self-hosted GLPI has no per-asset license, but inventory volume still drives database size and agent traffic. Ask how the vendor counts a unit, whether a laptop with several components counts once, and how packs are billed mid-term.
CMDB class depth
A shallow CMDB with a few asset classes is cheap to configure and easy to keep current. Each added class, relationship and impact-analysis rule adds modeling work, data-loading effort and ongoing review, and in iTop the data model is customizable, which means someone must own it after go-live. Ask the partner how many classes are in scope on day one, which relationships drive impact analysis, and who approves changes to the model. Deeper models usually cost more to build and less to change later.
ITIL processes in scope
Incident and request management are the common starting point, while change, problem and service-level management each add workflows, approval paths and reporting. Every process you switch on in a self-hosted tool needs configuration, testing and user training, and it also needs a named process owner. SaaS platforms often bundle more processes into the seat price, which can shift cost from configuration to subscription. Ask which processes are in the first release, which are deferred, and what a later addition costs.
Identity and monitoring integrations
Single sign-on, directory synchronization and monitoring feeds are where ITSM projects often run over budget, because each connection needs a service account, field mapping, error handling and test cases. GLPI can authenticate against LDAP directories and IMAP mail servers, and iTop supports data synchronization for federation, but each source still needs its own build and support. SaaS connectors reduce some of this work and may charge for premium integrations. Ask which connectors are included in the quote, which are custom, and who maintains them after upgrades.
Data migration and agent rollout
Migrating tickets, assets and contracts from a legacy desk is usually a one-time cost that scales with the volume and quality of the source data. Deploying inventory agents to every endpoint is a second one-time effort, and it recurs whenever new device types or operating systems appear. GLPI Agent runs on Windows, macOS and Linux and can perform network discovery, which lowers the manual inventory work but still needs packaging, deployment and exception handling. Ask for a data-cleansing estimate, a record count per object type, and a plan for agent upgrades.
Support level and hosting model
Self-hosting moves infrastructure, patching, backups and upgrades onto your team or a partner, and those costs recur for as long as the platform runs. Vendor support subscriptions add a fixed recurring fee and a defined response scope, and the tiers differ in included support levels. Hosted options from the vendor shift infrastructure work to the provider but change the data location and per-user billing. Ask which tier covers your upgrade path, who applies security updates, and whether the quote includes backup restore tests.
How do GLPI Network and iTop Community tiers compare with per-agent SaaS?
The published subscription lines are not directly comparable, because each vendor meters a different unit. GLPI Network charges per user per month: 19 euros on the public cloud and 21 euros on a private cloud, with a 25-user minimum. Self-hosted GLPI subscriptions run from 100 euros per month for the Basic tier (up to 10 agents and 500 assets) to 4,500 euros per month for Enterprise, which includes level 3 support and access to the GLPI Network marketplace plugins. iTop Community is free for up to 10 agents, Atelier covers up to 50 agents and Forge covers more than 50, each available on premises or as SaaS. Freshservice, by comparison, lists Starter at 19, Growth at 49 and Pro at 99 US dollars per agent per month billed annually, with 100 asset units included per plan. Confirm the current currency, billing terms and asset counting rules on each vendor's pricing page before modeling.
The subscription is only one line in the total. Under per-agent SaaS, the agent count drives the recurring fee directly, so a fifty-agent service desk pays for fifty seats every month whether or not the platform is configured well. Under a self-hosted model, the license fee is a smaller part of the budget, and the larger costs are one-time and internal: CMDB modeling, process configuration for incidents, requests and changes, agent rollout to endpoints, data migration, hosting, backups and the administrator who keeps the platform current. Those costs depend on your estate and processes, not on the vendor's tier table, so the break-even point moves with both the agent count and the internal effort you can staff.
To build a fair comparison, ask each option for a five-year model with the same inputs: agent count, asset count, number of administrators, expected hours for CMDB and process setup, and the support level you need. Ask whether a GLPI or iTop support subscription covers upgrades, security fixes and plugin compatibility, and whether a partner quote includes data migration and a post-go-live review. Then compare the recurring license line with the one-time and staffing lines in the same currency. Illustrative example: a team that outgrows a free tier and needs formal vendor support may find the subscription cost is small next to the administration effort, while a small team with few changes may find the free tier plus a modest partner engagement is the lower-cost route.
How do you build your own ITSM cost estimate?
This sequence turns a vague budget question into a set of counted inputs, so each cost option (build, partner or SaaS) is priced against the same scope. The result is a line-item list you can send to any implementation partner or SaaS vendor for comparison.
Count agents and assets
Start by counting the people who will work in the service desk and the people who will request services, since most ITSM subscriptions and support plans scale with one or both. Separately count the endpoints, servers, network devices and licensed assets that must be tracked. Your IT team can pull these figures from directory services, endpoint management tools and existing spreadsheets. The step is done when you have two numbers, agents and assets, each with a named source and a date. Note that per-agent SaaS pricing applies to agents, while asset counts can trigger separate allowances, so keep them apart.
List ITIL processes in scope
Decide which ITIL-aligned processes go live at launch, such as incident, service request, change, problem and knowledge management, and which can follow later. Each process adds configuration work for workflows, categories, SLAs, approvals and reports, so the list drives build effort directly. Your service management lead should sign off the list and mark any process that needs an audit trail. The step is done when every process has a go-live or later status and an owner.
Size CMDB classes and relationships
Identify the configuration item classes you need, such as servers, applications, business services, locations, contracts and suppliers, and the relationships between them. A smaller model is cheaper to configure and populate, while a model that supports impact analysis or regulator requests takes more design time. Ask whether each class has a named data owner who will maintain it after go-live. The step is done when you have a class list with relationships drawn and an estimate of how many records each class holds.
Plan inventory agent rollout
Estimate how inventory agents will reach each endpoint, including Windows, macOS and Linux systems, and which machines sit behind segmented or restricted networks. Agent deployment usually goes through your existing endpoint management or software distribution tools, and each device group needs testing before wide release. Record the number of device groups, any locations that need manual handling, and who will approve packaging and rollout. The step is done when every endpoint group has a deployment method and a responsible owner.
List integrations and data migration
List every system the service desk must exchange data with, such as directory services for identity, monitoring tools, procurement, finance, HR and existing ticket or asset databases. For each one, note whether the link is a one-time import, a scheduled sync or a live API call, and who owns the other end. Include the volume and cleanliness of data you plan to migrate, because poor source data often adds effort. The step is done when each integration and migration source has a direction, frequency and named owner.
Choose the support model
Decide how your team will run the platform after go-live: in-house administration, a support subscription from the platform vendor or a partner, or a managed service. Support subscriptions for open-source ITSM products typically recur each year or month and vary by tier, while in-house administration is a staffing cost that recurs as well. Confirm response expectations, upgrade handling and who applies security updates. The step is done when you have written the support model and the roles it requires.
Price each option against the same scope
Build three columns, one each for self-hosted build with optional vendor support, partner-led implementation and per-agent SaaS, and price every line from the previous steps in each column. Separate one-time costs such as design, configuration, migration and rollout from recurring costs such as hosting, licenses or subscriptions, administration and support. Take SaaS list prices from the vendor's published page and confirm current figures before you rely on them. The step is done when all three columns share the same agent, asset, process, class, integration and migration counts. Send the same scope to each partner and ask for a written quote, because the written scope is what drives a partner quote and a fair comparison depends on it.
What recurs after go-live and who pays for it?
Most of the running cost of a self-hosted GLPI or iTop desk is recurring, and it sits with your team unless you contract it out. The recurring items are the server and database hosting, backups, upgrades, security patching, vendor support subscriptions, administration time and the continuous upkeep of the CMDB. Hosting and database costs follow your infrastructure budget, so they will be paid whether or not you ever buy a support plan. Backups need their own line in the estimate because the GLPI update procedure requires a database backup, a file backup and a copy of the config directory, including the glpi.key and glpicrypt.key files, before every upgrade. Ask your partner to price the backup target and retention you need, not only the software.
Upgrades and patching recur on the vendor's release cadence, and you should plan the calendar before go-live. GLPI 12.0.0 was released on October 7, 2026, and GLPI 11.0.11 on October 1, 2026, so a team on the 11.0 line will see several releases a year to evaluate. Plugins deserve particular attention: since GLPI 11.0 they are suspended once a new version is detected and must be reactivated after major updates, so each major upgrade carries a plugin regression test. Security releases follow a different rhythm. Zammad 7.2.2, released on October 8, 2026 as a security update, is a useful reminder that a fix can arrive outside the feature cycle, and your change process must accept that. Confirm with your vendor or partner how security advisories are communicated and how fast they expect you to apply them.
Support subscriptions, administration time and CMDB maintenance are the costs most often underestimated. A GLPI Network self-hosted subscription is priced by tier, from 100 euros per month for Basic (up to 10 agents and 500 assets) to 4,500 euros per month for Enterprise, according to the GLPI Network subscriptions page, and these prices should be checked against the current page before a budget is set. Combodo also sells commercial support for iTop, so the choice is between buying vendor support, a partner retainer or in-house expertise. Administration staff time recurs through ticket triage, user and group changes, agent updates and reporting. Continuous CMDB maintenance is the largest hidden item: discovery data goes stale when devices move or are retired, so name an owner for reconciliation, and ask any partner to quote that work as a recurring service rather than a one-off cleanup.
What do buyers ask before they hire outside help for ITSM?
How much does self-hosted ITSM cost compared with a SaaS service desk?
Self-hosted ITSM replaces a per-agent subscription with a set of costs you pay once or on a recurring basis for different work: the platform itself is free under its open-source license, while you pay for infrastructure, configuration, CMDB population, agent rollout, migration, and ongoing administration. SaaS pricing is per agent per month; for example, Freshservice's pricing page, as read in October 2026, lists Starter at $19, Growth at $49 and Pro at $99 per agent per month billed annually, with Enterprise by quote. Compare your agent count over three to five years, including the services you would buy anyway, rather than the license line alone. Ask any partner to split the quote into one-time build work and recurring support.
How long does an open-source ITSM rollout take, and what sets the timing?
The timing depends mainly on how many processes go live at once, how clean your existing asset and user data is, how many integrations you need on day one, and how many sites or entities the desk covers. Each of these adds configuration, testing and approval cycles. A narrow first scope, such as incident and request management with an inventory import, moves faster than a full CMDB with change control and monitoring links. No duration is given here because none is supplied for this topic. Ask the partner for a phased plan with a written milestone list before accepting any timeline.
What does the work need from our own team?
Your team supplies the decisions and the data: which ITIL processes are in scope, who approves changes, how services and owners are defined, and where the authoritative lists of users, devices and contracts live. Engineers also need access to directories such as LDAP, the mail system for ticket intake, and the monitoring tools you plan to link. Expect a named process owner and a subject-matter reviewer for each process, plus someone who can sign off on the migrated data. Agent rollout needs endpoint management support, because GLPI Agent runs on Windows, macOS and Linux and must be deployed through your existing channels.
Can an internal IT team run this without outside help?
Yes, an internal team can deploy GLPI or iTop alone if it has the skills to administer a PHP application on MariaDB or MySQL, configure a web server, and manage backups and upgrades. The harder parts are usually process design, CMDB modeling and data quality, which need time away from daily support. GLPI's update procedure, for example, requires backing up the database, files and config directory including glpi.key and glpicrypt.key, and plugins are suspended after a new version is detected in GLPI 11.0 and later. Decide which parts you will keep in house and which you will buy, and make the handover documented and tested.
What does a support subscription cover, and what does it not?
A support subscription typically covers vendor-level help with defects, upgrades and sometimes training, but it does not replace the work of designing your processes or cleaning your data. Published examples show the range: GLPI Network self-hosted subscriptions run from 100 euros per month for the Basic tier, up to 10 agents and 500 assets, to 4,500 euros per month for Enterprise, which includes level 3 support, according to the GLPI Network subscriptions page. Combodo sells commercial support, training and consultancy for iTop. Confirm in writing the response levels, which versions are covered, whether plugins are included, and who handles upgrades.
What should a fixed-scope quote for ITSM include?
A fixed-scope quote should list the processes, CMDB classes, integrations, sites and user counts covered, with deliverables and acceptance criteria written for each phase. DeployOpen works from a written scope, agreed before work starts, and does not publish a price list, so the quote follows from that scope. Ask for separate lines for platform installation and hardening, process and CMDB configuration, agent rollout, data migration, integrations, training, and post-go-live administration. Also ask which items recur, what is excluded, how changes to scope are priced, and what happens to data and configuration at the end of the engagement.
What should a fixed-scope ITSM quote include?
DeployOpen does not publish a price list. A quote follows from a written, fixed scope, so the scope is the first thing a buyer should insist on. For a GLPI or iTop engagement, that scope should name the ITIL processes in play (incident, request, change and problem), the approval paths and SLA definitions for each, and the service catalog entries that will be live at go-live. It should also list the CMDB classes to be modeled in iTop or the asset types and custom fields to be configured in GLPI, because each class and field is design and test work. Ask for the discovery plan as well: which networks and endpoints the GLPI Agent or other inventory agents will cover, which operating systems are in the first wave, and what the agent deployment method is.
The scope should also state the migration sources and record counts, the integrations (identity directory, monitoring, procurement, and any mail or chat tools that create tickets), and the reports to be delivered. Record counts matter because they drive the size of data cleansing and the number of validation passes. Training should be named by audience (service desk, administrators, approvers, asset owners), and hypercare should have a stated duration and exit criteria, with handover items listed. Finally, the post-go-live support model must be explicit: whether it is a retainer, a support subscription from the platform vendor, or internal staff, and what each covers. Confirm with the vendor what its subscription includes, since support tiers and inclusions differ, and treat anything unstated in the quote as an open cost.
How DeployOpen scopes and delivers a fixed-scope ITSM implementation
DeployOpen plans, implements, customizes, integrates, documents and supports self-hosted open-source service management platforms inside your own infrastructure. For ITSM cost: build, partner or SaaS, we start by putting the cost components on paper so the build, partner and SaaS options can be compared on the same written basis.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope lists which ITIL processes, asset classes, agent counts and integrations are included in the cost comparison.
- The quote follows from the written scope, so ask that every cost line names who is paid, for what and whether it recurs.
How we build
- We configure GLPI or iTop, the CMDB model, the agent rollout and the process configuration against the agreed scope.
- Migration of existing tickets, assets and contracts is planned and tested in a separate environment before any cutover.
- Testing covers the agreed workflows, data consistency checks and access controls, with results recorded for your review.
How we hand over
- Deliverables include configuration records, the CMDB data model, agent deployment notes and administrator documentation.
- We document the update procedure for the chosen platform, including database, file and configuration backups before upgrades.
- Handover covers the cost model you need to run the platform, so internal and partner effort can be tracked after go-live.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped separately from the build.
- Retainers can cover platform upgrades, plugin revalidation after major releases and changes to processes or integrations.
- Ask any partner, including DeployOpen, to state in writing what a support subscription covers and what it excludes.
