Is self-hosted GLPI cheaper than ServiceNow cost of ownership?
GLPI carries no license fee, so its cost moves to hosting, implementation, optional support and the staff who run it. ServiceNow's cost arrives through its account team, and the subscription figure must come from your own quote, not from this page. Before comparing, ask ServiceNow for a written breakdown that separates the subscription, any add-on applications you use, and the support tier, and ask for the renewal uplift terms. Then build the GLPI side with the same granularity: servers or virtual machines for the web, PHP and database tiers, backups, monitoring, implementation effort, plugins, and the administrators who will patch and upgrade it. Hosting and staff are recurring costs. Implementation and data migration are mostly one-time.
If you want a paid support contract, GLPI's maintainer Teclib' offers a reference point through its GLPI Network subscriptions: public cloud at 19 euros per user per month, private cloud at 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). Those are list figures from the vendor's subscription page and are not a quote for your environment. Support is optional, so a team with strong internal GLPI skills may not need it, while a team without that depth should price it as a recurring line.
Private Stack is not a zero-infrastructure option. Under ServiceNow Private Stack, the customer or a partner runs the load balancer, application server and database tiers, and ServiceNow's account team sets up a workshop covering architecture planning, hardware sizing, database selection and operational readiness. Ask whether that workshop is a one-time fee, what hardware and database licenses you must buy, and who carries upgrade work. Those items belong beside the subscription in your comparison, because they can narrow the cost gap even where a subscription is required anyway.
Cost components on each side
This table sets each cost component of staying on ServiceNow, or moving to its customer-operated Private Stack, beside the matching component of running GLPI yourself. Read each row for who is paid, whether the cost is one-time or recurring, and what moves the number. No figures appear where the researched sources give none, so use the rows to build the questions you send to your ServiceNow account team and to any implementation partner.
| Cost component | ServiceNow (cloud or Private Stack) | Self-hosted GLPI | One-time or recurring |
|---|---|---|---|
| Software subscription or license | Subscription quoted through your ServiceNow account team, priced by the scope you buy. Private Stack still requires ServiceNow subscription terms for the application software. | No license fee. GLPI is GPL-3.0 software. Optional GLPI Network subscriptions from Teclib' add cost only if you buy them. | Recurring for ServiceNow. None for GLPI core. |
| Private Stack or cloud fees | Cloud: included in the subscription. Private Stack: ServiceNow supplies application software, upgrade packages and support, so confirm what those terms add. | Not applicable. Hosting is your own cost, covered in the infrastructure row. | Recurring |
| Infrastructure | Cloud: included in the subscription. Private Stack: you or a partner own the load balancer, application server and database tiers, and their hardware or cloud spend. | You own the web server, PHP runtime, MariaDB or MySQL database, storage and backups. Size these against your asset and ticket volume. | Recurring, plus one-time build |
| Implementation and workshop | Private Stack deployments go through your account team, who should be expected to sell a workshop on architecture, hardware sizing, database selection and operational readiness. | Internal or partner effort for installation, configuration, LDAP or IMAP authentication, and hardening. Quoted from a written scope. | One-time |
| Data migration | Export from ServiceNow in the formats and limits your instance allows, then map records by hand or through a partner. | Extract, transform and load into GLPI. Workflows and service catalog items usually need rebuilding, so budget that effort explicitly. | One-time |
| Teclib' or other support | Included in subscription tiers for ServiceNow. Confirm response targets and severity levels in the contract. | Optional. Teclib' offers paid self-hosted subscriptions, with the level of support tied to the tier you choose. Community support is free but carries no contractual response. | Recurring if bought |
| Upgrades and testing | ServiceNow supplies upgrade packages. Your team or partner still tests customizations and integrations before each release. | You back up the database, files and config directory, replace application files and run the database update. Plugins are suspended after a new version and must be reactivated, so test each upgrade. | Recurring |
| Internal skills and staff time | Platform administrators for ServiceNow, plus operators for the Private Stack tiers if you choose that model. | Administrators for GLPI, a web server and database operator, and someone who owns backups and patching. Confirm the skill gap with your team before you decide. | Recurring |
What Private Stack moves onto your budget
Private Stack does not remove the cost of running ServiceNow on your own hardware. It moves that cost out of the subscription line and into infrastructure, operations and staffing. Under this model, ServiceNow supplies the application software, upgrade packages, deployment guidance and support, while the customer or a partner owns and operates the load balancer, application server and database tiers. Each of those tiers needs compute, storage, network capacity, backup and monitoring that you pay for directly, and each needs a named person accountable for patching and capacity. Before comparing totals with GLPI, map every tier to a budget line and an owner, because a number that looks lower on the subscription quote can carry a larger run cost once those tiers are counted.
Starting a Private Stack deployment goes through your ServiceNow account team, and you should expect to buy a workshop covering architecture planning, hardware sizing, database selection and operational readiness. This workshop is a distinct purchase that sits outside the platform subscription, so it appears as a separate line item. Ask your account team for its scope, deliverables, duration, price and what happens if sizing changes after the workshop, and get all of it in writing before you commit. Also ask whether the hardware sizing output is binding for the support terms, and whether the database choice limits later upgrade paths. These answers determine how much of the cost is one-time and how much recurs as you grow.
The practical point for the budget is that Private Stack costs change category rather than disappearing. Subscription fees become a mix of infrastructure, database licensing, staff time for operations, backup storage and the workshop. GLPI shifts a different set of costs: its license fee is zero, but you still pay for hosting, implementation, any optional Teclib' support and the people who run it. Build one model with both columns, listing one-time and recurring costs separately, and show who pays for each item. The comparison is only fair when both sides carry the same operational load.
What moves the GLPI cost up or down
GLPI's license fee is zero, so almost every cost lever sits in hosting, implementation, support and staffing. The drivers below show which cost component each one moves, so you can scope a quote against your own environment rather than a generic estimate.
User and agent counts
Headcount of requesters and technicians shapes the sizing of the web, application and database tiers, and it sets the number of accounts your support contract or hosted plan must cover. Ask whether the service desk is priced by named user or by agent, because the two counts often differ. Recount technicians who only read tickets, since they may still need licensed seats on a hosted or supported option.
Asset and inventory volume
The number of endpoints, network devices and software installations drives database growth, inventory processing and the load GLPI Agent places on your server. Higher volumes mean larger database instances and more capacity planning time during implementation. Ask your implementer to size the database against a realistic asset count from your existing CMDB or ServiceNow export.
Teclib' support or GLPI Network
This is the main recurring line that is optional in GLPI. Teclib' offers self-hosted subscriptions with a per-tier monthly fee, and a hosted GLPI Network option priced per user with a minimum user count. Buying one of these moves cost from staff time into a predictable subscription, while skipping it keeps the cost in internal or community-skilled support. Compare the subscription tier against the agent and asset counts you expect.
Availability and backup requirements
A single instance with nightly backups costs far less than a clustered, load-balanced deployment with tested failover. Every requirement for uptime, recovery point and recovery time adds hardware, replicated database capacity and monitoring. The GLPI update procedure also requires backing up the database, files and the config directory, including the glpi.key and glpicrypt.key files, so budget time for that routine on every upgrade.
Data residency and air-gap constraints
Keeping GLPI inside your own data center or an air-gapped network removes hosted fees but adds internal infrastructure, offline patch handling and local support staff. A hosted option in another region may be cheaper to run but must be checked against your residency rules before it is shortlisted. Ask any implementer how updates, plugin packages and vulnerability fixes reach an offline environment.
Skills already in the team
Staff who already run PHP, MariaDB or MySQL, and Linux web servers can absorb GLPI administration at lower cost than a team that must hire or train for it. The largest recurring cost is usually the administrator's time for upgrades, plugin reactivation and customization, not the software itself. Ask whether the internal team or an external provider will own patching, and write that split into the scope before signing.
How to build the comparison with your own numbers
This sequence turns the cost components on this page into a side-by-side total that reflects your contract, your estate and your staff. Each step ends with a figure you can defend in a budget review.
Pull your current ServiceNow spend
Ask your ServiceNow account team for a written statement of your current subscription, including the products, user or fulfiller counts, support tier and the term end date. Ask separately what the renewal would cost if you stay on cloud, and whether any Private Stack option is quoted. Record the annual figure for each line item, not a single bundled total, so each component can be compared later. You know this step is done when every line on the quote maps to a product or service you can name and the term dates are written down.
List every module in active use
Inventory the ServiceNow modules your teams actually use, such as incident, problem, change, service level management, asset management, CMDB, discovery, service catalog and knowledge. Include scripted workflows, integrations and reports that depend on them. Mark which modules are licensed but idle, because idle licenses often carry a cost you can remove in either path. Compare this list with the module-by-module fit on the sibling comparison page. You know this step is done when each module has an owner, a user count and a yes or no for whether GLPI covers its function.
Size the GLPI host and database
Size the target environment against the requirements in the current GLPI README, which list PHP 8.3 or later and MariaDB 10.11 or later or MySQL 8.0 or later. If you plan to install GLPI 11.0, the installation docs list PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6, so confirm which version you will run before pricing hardware. Note that the docs require the web server's document root to point to the public directory and that only MySQL and MariaDB are supported. Ask your infrastructure team for virtual machine or container costs, backup storage and a second environment for testing. You know this step is done when each server role has a documented specification and a monthly cost taken from your own cloud or data center invoices.
Estimate internal staff hours yourself
Estimate the hours your own staff will spend on installation, configuration, workflow rebuilding, plugin management, upgrades and routine administration. Split the estimate into one-time work and recurring work, and assign each task to a named role, such as a platform engineer, a service desk lead or a security administrator. Use timesheets from your current ServiceNow administration team as the baseline for recurring effort, and ask whether any external support will be needed. Account for the GLPI update procedure, which requires backups of the database, files and config directory and a database update step. You know this step is done when every hour has a role, a rate from your own payroll or contract data, and an annual total.
Price the migration as its own line
Add a separate line for moving records, assets and integrations out of ServiceNow and into GLPI. Ask for a fixed-scope written quote from any implementation partner, and list the data you must extract within ServiceNow's export limits, the mapping work, the rebuilding of workflows and service catalog items, and user acceptance testing. Keep this line separate from recurring costs so it does not distort the annual comparison. If you plan to use Teclib' support or a GLPI Network hosted option, record those quotes here as well, using the figures published on the GLPI subscriptions page only as a reference point. You know this step is done when the migration has a written scope, a quote and a named owner.
Compare totals over a fixed horizon
Choose one horizon, such as the number of years in your budget cycle, and apply it to both paths. For the ServiceNow path, add renewals, expected uplifts quoted by the account team and any Private Stack infrastructure or workshop costs. For the GLPI path, add one-time migration, hosting, staff time, optional support and any reserve for upgrades. Show one-time and recurring costs in separate columns so leadership can see the break-even point. Test the result by changing one driver at a time, such as user count or staff rate, to see which assumption moves the total most. You know this step is done when both totals sit in one table with the same horizon, the same currency and a source note on every figure.
Document the sources behind every figure
Attach the source of each number to the comparison: the quote reference, the timesheet period, the invoice or the hardware specification. Mark any figure that is an assumption, and state who approved it. Keep a record of the GLPI version and documentation date you used, since release dates and requirements change. Have finance and the security or compliance lead review the table before it goes into a renewal or procurement decision. You know this step is done when a reviewer can trace each total back to a document your organization holds, with no unsourced line remaining.
Who pays for upgrades, patches and backups
On the GLPI side, every upgrade is work your team or your implementation partner performs. The documented update procedure asks you to back up the database, the files and the config directory, including glpi.key and glpicrypt.key, because losing those keys can make encrypted data unreadable. You then replace the application files, run php bin/console db:update, and check the result. Since GLPI 11.0, plugins are suspended once a new version is detected and must be reactivated after major updates, so every upgrade includes a plugin review step. Budget for this as a recurring cost in staff time or retained support, and confirm who holds the key files and who tests restores.
On the ServiceNow side, the cost model shifts. Under the cloud subscription, ServiceNow operates the platform and applies its own upgrades. Under Private Stack, ServiceNow supplies the application software, upgrade packages and deployment guidance, but your team or a partner still operates the load balancer, application server and database tiers, so those patch cycles, database maintenance and backups remain yours. Ask your account team which upgrade packages are included in your subscription or Private Stack agreement, how often they are released, and whether the workshop or support tier covers help with applying them.
Effort on either side depends on what you have built on top of the base product. A GLPI instance with a few standard plugins and default ticket templates is a very different upgrade from one with custom plugins, bespoke workflows and LDAP or SSO integrations that each need retesting. Inventory your plugins, custom code and integrations before you price anything, and ask any implementation partner to quote upgrades, patch windows and restore tests as separate line items in the written scope.
Questions buyers ask about GLPI and ServiceNow costs
Is self-hosted GLPI really cheaper than staying on ServiceNow?
GLPI has no license fee, so its cost is the infrastructure, the implementation, any support contract and the staff who run it. ServiceNow cost comes from subscriptions quoted through its account team, and that quote depends on modules, user counts and platform scope, which you should confirm in writing. If you move to Private Stack, the cost moves to you as well: you still pay for the subscription, and you add the servers, the load balancer, the database tier and the workshop ServiceNow expects you to buy. Compare both models over the same period, with the same user counts and the same modules, and include the people hours on each side.
Can our team run GLPI without outside help?
Many teams with existing Linux, PHP and database skills can run GLPI in-house, but the answer depends on what you need to operate. GLPI runs on PHP 8.3 or later with MariaDB 10.11 or later or MySQL 8.0 or later according to the GLPI README, while the installation docs list PHP 8.2 and MariaDB 10.6 for GLPI 11.0, so check which version you are installing. Upgrades require backing up the database, files and the config directory, including glpi.key and glpicrypt.key, and running php bin/console db:update. Plugins are suspended after a new version is detected and must be reactivated after major updates, so plan that step. Estimate the skills and on-call coverage you already have before deciding.
What does outside help cost, and how is it quoted?
DeployOpen does not publish a price list. Outside help is quoted from a written, fixed scope that lists the deliverables, the environments, the integrations and the timeline before work starts. The main cost drivers are the number of modules in use, the volume and quality of data to migrate, the number of integrations with identity, monitoring and asset sources, and how much customization your workflows need. Ask for the scope to separate one-time work, such as installation, migration and hardening, from recurring work, such as upgrades, backups checks and support retainers. Ask for the assumptions behind each line so you can see what changes the number.
How long does a migration take, and what does it need from our side?
The duration depends on scope, not on a fixed template, so it should be stated in the written plan rather than assumed. Your side typically needs an owner for service desk processes, someone who can export ServiceNow records within its export limits, and people to validate incidents, changes, assets and configuration items after load. Rebuilding workflows, approval paths and service catalog items by hand usually takes the most time, so agree early which of those you will carry over. Ask your implementation partner to name the inputs they need from you and the validation steps they will run before cutover.
Does GLPI Network change the cost comparison?
Yes, because it replaces the operations work with a subscription. GLPI Network public cloud costs 19 euros per user per month and private cloud costs 21 euros per user per month with a 25-user minimum, according to the GLPI Network subscriptions page. Self-hosted GLPI subscriptions range 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 marketplace plugins, per the same page. Run the per-user figure against your user count and the tiered figure against your agent and asset counts, then add the internal hours you save or keep. Confirm current terms directly with Teclib' before you rely on them.
What support tiers exist for GLPI, and who provides them?
GLPI is edited and maintained by Teclib', which offers the self-hosted subscription tiers and GLPI Network. The subscription page describes Basic, and Enterprise with level 3 support, so check the tier names and included support levels on the current page before you decide. Community support is available for the free software, but it does not carry a response commitment, so it should not be your only plan for production. Separately, DeployOpen offers ongoing support, upgrades and continuous testing as retainers, and those are scoped in writing. Ask each provider what response times, hours and escalation paths are included, and whether they cover your plugins and integrations.
Which costs recur every year in a self-hosted GLPI setup?
The recurring costs are the hosting and its backups, the staff time for upgrades and monitoring, any Teclib' subscription or support contract, and any retainer you buy from an implementation partner. The one-time costs are the initial setup, data migration, integrations, workflow design and training. Upgrades recur because each major GLPI release requires a planned update, and plugin compatibility must be checked at each step. Ask for the recurring items to be listed separately in any quote, along with what triggers an extra charge, such as a new integration or a larger asset count.
When staying on ServiceNow is the cheaper answer
Staying on ServiceNow is often the cheaper answer when the in-house team is small, the platform is used for much more than ITSM, and the cost of replacing those workflows would exceed the subscription. Start by counting the people who would run GLPI: a platform team that already patches, backs up and upgrades a PHP and MariaDB or MySQL stack, and can absorb the GLPI release cycle and plugin reactivation after major updates, lowers the people cost of self-hosting. A team without that capacity pays for it in hours or in a contracted partner, and that cost recurs for as long as the system runs. Ask ServiceNow's account team for a written subscription quote covering the modules you actually use, so you can compare it line by line with the staffing and hosting you would add.
The second case is deep platform use. If your workflows, service catalog items, integrations and reporting depend on ServiceNow's application platform beyond ITSM, a move to GLPI means rebuilding those pieces by hand, and that effort is a one-time cost that can outweigh several years of subscription. The module-by-module comparison in ServiceNow vs GLPI shows where GLPI has direct equivalents and where it does not. Treat any gap there as a line item in your comparison, not a footnote.
The third case is budget already committed. If a Private Stack workshop covering architecture planning, hardware sizing, database selection and operational readiness is already funded, the marginal cost of staying on the ServiceNow path may be lower than a fresh migration. Private Stack still means you or a partner operate the load balancer, application server and database tiers, so compare its infrastructure and operations costs with GLPI's hosting costs before deciding. Non-cost factors such as air-gapped operation, sovereignty and exit terms belong in the ServiceNow Private Stack vs self-hosted open-source ITSM and air-gapped comparisons, which this section does not decide.
How DeployOpen scopes a fixed-price GLPI implementation
DeployOpen plans, implements, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a ServiceNow cost comparison, we start with a written scope that shows what GLPI would replace, what it would cost to run in your environment, and what your team would own afterward.
How we scope
- We inventory your current ServiceNow subscriptions, modules, integrations and the teams that depend on them.
- We agree on the GLPI scope in writing, covering incident, problem, change, asset and contract processes.
- We confirm hosting, PHP and database versions, and whether GLPI Agent or LDAP will be part of the build.
How we build
- We install GLPI on your infrastructure with the web root pointed at its public directory and HTTPS enforced.
- We configure authentication sources, roles, SLAs and ticket workflows that match your documented ITIL processes.
- We test imports, notifications and backup restores before any user group moves onto the new service desk.
How we hand over
- We document the architecture, configuration decisions, backup procedure and the GLPI update steps your team will follow.
- We walk your administrators through daily operation, including plugin reactivation after major updates.
- We deliver the acceptance test results and a list of open items so your team knows exactly what remains.
How we support
- Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Ask for a quote built from the written scope, and confirm which support tier from Teclib' you need alongside it.
