Which GLPI plugins need a GLPI Network subscription
Whether a GLPI plugin carries a subscription cost depends on where it comes from. A plugin is either free, published by the community, or sold through the GLPI Network marketplace, and the subscription level decides what a paying customer receives. Sort your shortlist into those groups first, because the cost question only applies to marketplace plugins. GLPI itself is distributed under the GNU General Public License version 3 and maintained by Teclib', so the core platform does not require a subscription to self-host. Teclib' also sells GLPI Network, and the GLPI Network subscriptions page lists the hosted and self-hosted options that apply to paid tiers.
The subscriptions page lists GLPI Network public cloud at 19 euros per user per month and private cloud at 21 euros per user per month, with a 25-user minimum for private cloud. Self-hosted subscriptions run from 100 euros per month for Basic, which covers up to 10 agents and 500 assets, to 4,500 euros per month for Enterprise, which includes level 3 support and access to GLPI Network marketplace plugins. For a self-hosted instance, the tier is the deciding factor, because marketplace access and support level both depend on it. Confirm current pricing with Teclib' before you budget, and ask which tier each marketplace plugin requires rather than assuming the Basic tier is enough.
Before you commit, ask each publisher three questions: whether the plugin is free, community-published or marketplace-only; which GLPI Network level, if any, it requires; and what support it receives. Support paths differ between Teclib'-published and community plugins, so get the answer in writing. Record each answer against the GLPI version you plan to run, since a plugin that works on GLPI 11 may not yet have a matching build for GLPI 12. Finally, confirm that the licensing answer applies to the hosting model you chose, whether self-hosted or cloud, and keep the written confirmations with your architecture records.
How GLPI Network subscription levels differ
GLPI Network public cloud is the subscription model where Teclib' hosts the GLPI instance. The published price is 19 euros per user per month, according to the GLPI Network subscriptions page. That figure is the main recurring cost, and it scales with the number of users rather than with hardware or agents. Because the service is hosted by the vendor, the infrastructure, patching and platform operation sit with Teclib' rather than with your team.
- Price basis: 19 euros per user per month, per the GLPI Network subscriptions page.
- Recurring cost: the per-user fee repeats monthly, so user growth is the main driver of spend.
- Hosting responsibility: the vendor operates the service, which limits where your own data and systems can sit.
- Trial: the GLPI project site describes a 45-day free trial for GLPI Network Cloud.
- Plugin entitlements: confirm in the subscription terms which plugins and support levels apply to this tier.
Before committing, ask the vendor to confirm the data location, backup arrangements and exit terms in writing.
GLPI Network private cloud is priced per user as well, at 21 euros per user per month, with a 25-user minimum, according to the GLPI Network subscriptions page. The private cloud option is aimed at organizations that want a dedicated hosted environment rather than a shared one. The minimum seat count means smaller teams pay for more users than they have, so the break-even point against other models depends on headcount.
- Price basis: 21 euros per user per month, per the GLPI Network subscriptions page.
- Minimum commitment: a 25-user minimum applies, which matters for small teams.
- Dedicated hosting: the instance is dedicated to your organization, which differs from the shared public option.
- Recurring cost: the per-user fee repeats monthly for the life of the subscription.
- Level entitlements: confirm which support level and marketplace plugins are included before signing.
Ask the vendor to state the minimum billable seat count, how user changes are invoiced and what happens to data at contract end.
Self-hosted GLPI Network subscriptions run on infrastructure you control and are priced per month by tier rather than per user. The GLPI Network subscriptions page lists tiers from 100 euros per month for Basic up to 4,500 euros per month for Enterprise. Basic is limited to 10 agents and 500 assets. The higher tiers raise those limits and add support and plugin entitlements, so the tier choice depends on agent count, asset volume and the level of vendor support you need.
- Basic tier: 100 euros per month, limited to 10 agents and 500 assets, per the GLPI Network subscriptions page.
- Enterprise tier: 4,500 euros per month, and per the same page it includes level 3 support and GLPI Network marketplace plugins.
- Intermediate tiers: confirm the price, agent limit and asset limit for each tier in the current price sheet.
- Hosting responsibility: your team operates the platform, backups and upgrades, so internal staffing is a cost in addition to the subscription.
- Upgrade path: plan GLPI 11 and 12 upgrades against the tier you choose, because plugin support depends on it.
Request a written comparison of tiers against your actual agent and asset counts before choosing a level.
Which plugin types are free and which need a subscription
GLPI plugins fall into four groups with different cost and support terms. Core features need no plugin at all, while community and Teclib-published plugins differ in license and support, and GLPI Network marketplace plugins sit behind a subscription level. Check each plugin's listing and license terms rather than assuming which group it belongs to.
Core features needing no plugin
Since GLPI 11, forms and generic assets are part of the core, so the plugins that once provided them are no longer needed for those functions. Before you budget for a plugin, check whether the capability already ships in your version. Plugin data migrations from GLPI 10 still need planning, because the core now holds data that older plugins may have stored elsewhere. Confirm the exact feature set against the GLPI 11 release notes for your target version, since the core feature list changes between releases.
Free community marketplace plugins
Community plugins listed in the GLPI marketplace are published by third parties and are not covered by a GLPI Network subscription. Each one carries its own license, maintainer and release cadence, so the free price does not imply vendor support. Check the plugin's license terms, the GLPI versions it declares compatibility with, and whether the maintainer still publishes updates. Plan your own test and update process for these plugins, because a plugin that lags a GLPI release can block an upgrade.
Teclib-published plugins with licensing terms
Some plugins published by Teclib, the company that maintains GLPI, may require a paid subscription for full use or support. Ownership by Teclib does not settle the question on its own. Read the individual listing for the license model, the features gated behind a subscription and the support scope it includes. Ask Teclib in writing which subscription level, if any, applies to the exact plugin and version you plan to deploy.
GLPI Network marketplace plugins
Plugins available through the GLPI Network marketplace are tied to subscription levels. The subscriptions page lists the self-hosted Enterprise level as including level 3 support and GLPI Network marketplace plugins, so these plugins are not a free add-on for lower tiers. Confirm which self-hosted level unlocks each plugin, and whether the plugin is available to public or private cloud subscribers as well. Ask for the entitlement in writing before you design a workflow around it.
How support differs for Teclib and community plugins
This table compares Teclib-published plugins, GLPI Network marketplace plugins and community plugins on who publishes them, who fixes defects, what a subscription adds and who to contact. Read each row as a question to put to the vendor before you commit to a plugin in production. Response commitments are not supplied here, so confirm them in writing for each plugin you plan to use.
| Dimension | Teclib-published plugins | Community plugins |
|---|---|---|
| Who publishes | Teclib' itself, the company that maintains GLPI | Independent developers or groups, often outside Teclib' |
| Who fixes defects | Teclib' development team, on its own release schedule | The plugin author or maintainers, if they are still active |
| Subscription effect | Support and access depend on the GLPI Network tier; confirm which tier covers each plugin | No vendor subscription covers the plugin; support is best effort |
| Plugin access | Confirm whether the plugin is included at your tier or sold separately | Free to install from the project, subject to its license |
| Upgrade alignment | Expect updates tied to GLPI releases; confirm compatibility with your target version | Check the plugin's latest release against the GLPI version you plan to run |
| Who to contact | Teclib' support channel included with your subscription | The project repository, issue tracker or listed maintainer |
| Response commitments | Ask for written response times and severity definitions before purchase | None unless the maintainer states them; plan for self-support |
| Ownership risk | Lower risk of abandonment while the vendor maintains the product | Higher risk: confirm the project is active before depending on it |
How to decide whether a plugin is worth a subscription
This sequence turns a plugin wish list into a go or no-go decision per plugin, based on the business need, publisher and license, subscription fit, written support scope and a tested result on a copy of your GLPI version.
List required plugins against business requirements
Start by writing down each business requirement the plugin is meant to meet, such as custom fields, purchasing, customer credits or AI ticket summaries. Map each requirement to a candidate plugin and note whether a native GLPI feature already covers part of it. The product owner and the GLPI administrator should sign off the list together. The step is done when every plugin on the list has a named requirement it serves and every requirement has either a plugin or a documented gap.
Check each plugin's publisher and license
For each candidate, confirm who publishes it, whether Teclib' maintains it or a community author does, and under which license it is distributed. Check whether the plugin is listed as part of the GLPI Network marketplace or sits outside it. Record the publisher, license and release page in the decision log. Confirm these details on the publisher's own page rather than relying on a third-party listing, and treat any plugin without a clear maintainer as a risk to log.
Count users and agents against subscription tiers
Count the named users, managed agents and assets that the plugin would touch, then compare those numbers with the subscription options on the GLPI Network subscriptions page. The page lists public cloud pricing per user per month, private cloud pricing with a minimum user count, and self-hosted tiers with agent and asset limits. Ask Teclib' or a reseller which tier includes the plugin you need and whether that tier changes as your counts grow. The output is a tier recommendation with the counts used to reach it.
Confirm support scope in writing
Ask the publisher, in writing, what support covers for each plugin: installation help, bug fixes, feature requests, response channels and whether the support level depends on the subscription tier. Ask community authors the same questions and record that community support has no contractual commitment unless a separate agreement says otherwise. Store the answers next to the decision log. The step closes when every plugin has a written support statement that the approver has read.
Match plugin versions to the GLPI release
Confirm that the plugin version you intend to install supports the exact GLPI release in use or planned, including minor releases. Plugins are tied to GLPI versions, so a plugin built for one major line may not run on another, and GLPI 11 suspends plugins after a new version is detected until they are reactivated after major updates. Record the GLPI version, the plugin version and the compatibility statement from the publisher. Do not proceed to testing if the match is unclear.
Test the plugin on a non-production copy
Restore a copy of the production database and files into a separate environment running the same GLPI version, then install and configure the plugin there. Run the business scenarios from step one, check that existing tickets, assets and permissions behave as before, and confirm that the GLPI update and backup procedure still works with the plugin active. Record defects and workarounds. The step is complete when the test report shows each required scenario passing and the owner accepts the result.
Record the subscription decision
Bring the requirement map, license review, tier count, written support statement, version match and test report into one decision record. Mark each plugin as subscribe, use free, or drop, and state the recurring cost owner for each subscription. Name the person who will review the decision when GLPI or the plugin releases a new version. The record is the output of the sequence and the basis for the purchase request.
What licensing choices mean for security and upgrades
Plugin licensing shapes who fixes a problem and how fast a GLPI upgrade can proceed. The cards below cover the risks that appear when a GLPI major version changes and the steps that keep the instance recoverable. Confirm each point against the plugin's own release notes and your GLPI version before you commit to a design.
Community plugins after a major update
A community plugin is maintained by its authors, not by Teclib', so there is no contractual obligation to ship a build for the next GLPI major version. Before a GLPI 11 or 12 move, check whether the plugin publishes a release for that version and who will answer if it breaks. Ask the question in writing and record the answer as part of the upgrade scope.
Plugins suspended until reactivated
Since GLPI 11.0, plugins are suspended after a new version is detected and must be reactivated after major updates. Plan for a window in which plugin-driven features such as custom forms, fields or purchasing are unavailable. Test the reactivation order in a staging copy so users do not discover missing functions on the production instance.
Back up the encryption keys
The update procedure requires backing up the database, the files and the config directory, including glpi.key and glpicrypt.key. Without these keys, encrypted values stored by GLPI and its plugins may not be readable after a restore. Store the keys separately from the database dump, restrict access to them, and test a restore that uses the copied keys.
Align plugin versions with the core
Each plugin release targets a range of GLPI versions, and mismatched pairs can fail during php bin/console db:update or after reactivation. Record the GLPI version and the exact plugin version in your change log, and keep the two on a matched pair before and after each move. Confirm the supported range for every plugin you run on GLPI 11 or 12.
Subscription support and update entitlement
Teclib-published plugins sold through a GLPI Network subscription come with the vendor's support channel, while community plugins rely on public issue trackers and volunteer responses. Ask the vendor whether the subscription level you buy includes plugin updates for future major versions, and whether support covers a plugin conflict during an upgrade. Get the answer in the quote.
Test plugins on a copy first
Because a plugin change can alter database structures, run every GLPI and plugin update first on a restored copy of production. Compare custom fields, forms, approval circuits and notification templates before and after the move. Keep the rollback path documented, including the backup set and the previous plugin packages.
Questions buyers ask about GLPI plugin licensing
Do community GLPI plugins need a GLPI Network subscription?
Not every plugin does, and the supplied information does not map each plugin to a subscription level, so confirm this plugin by plugin before you commit. GLPI itself is distributed under the GNU General Public License version 3, but each plugin carries its own license and distribution terms, which you should read in its source repository. The GLPI Network subscriptions page describes marketplace plugins as part of its higher self-hosted tiers, so ask Teclib or your reseller which plugins in your list are included at which level, and which ones you can install and run without a subscription.
What does a self-hosted GLPI Network subscription cost?
According to the GLPI Network subscriptions page, self-hosted subscriptions run from 100 euros per month for the Basic tier, which covers up to 10 agents and 500 assets, to 4,500 euros per month for Enterprise, which includes level 3 support and GLPI Network marketplace plugins. The fee is recurring and paid to Teclib, so it sits alongside any one-time implementation work, which is paid to whoever builds and tests your plugins. Check the tier limits against your current agent and asset counts, and ask whether growth moves you to a higher tier and how that change is billed.
How much do GLPI Network cloud subscriptions cost per user?
According to the GLPI Network subscriptions page, the public cloud plan costs 19 euros per user per month, and the private cloud plan costs 21 euros per user per month with a 25-user minimum. These are managed cloud services run by Teclib, so they answer a different question from a self-hosted deployment in your own infrastructure. The GLPI project site also mentions a 45-day free trial for GLPI Network Cloud. Ask Teclib for the current terms, including what the per-user count includes and how inactive users are counted.
How long does GLPI plugin work take, and what drives the timeline?
No duration for plugin work is supplied here, so the timeline should come from a written scope. The main drivers are the number of plugins, whether each one supports your target GLPI version (the GLPI 11 and 12 release lines differ in their requirements), the amount of data to migrate, how many integrations and custom fields are involved, and how much testing your business owners need before go-live. Plugins that depend on a database or form structure that changed between GLPI 10 and 11 usually add more analysis. DeployOpen agrees scope, deliverables and timelines in writing before work starts, so ask for each phase to be listed separately.
What does our team need to provide for a GLPI plugin project?
Your team should provide the target GLPI version, a current list of plugins with their versions, and a staging environment in infrastructure you control, since DeployOpen works inside your own cloud accounts, data centers or air-gapped networks. You will also need named business owners who can approve configuration choices, test users who represent each team, database and file backups before any change, and access to any subscription or marketplace registration the plugins require. Ask the project lead to confirm these items in writing, along with who approves go-live and who signs off on rollback steps.
Can our own administrators manage GLPI plugins after go-live?
Yes, if your administrators follow the documented procedures and have a rollback plan. The GLPI update guidance asks you to back up the database, the files and the config directory, including the glpi.key and glpicrypt.key files, replace the application files, and run php bin/console db:update. Since GLPI 11.0, plugins are suspended when a new version is detected and must be reactivated after major updates, so each upgrade needs a plugin compatibility check. Your team should also track which plugins have active maintainers and which depend on a single developer. The GLPI update documentation is the natural next read for this procedure.
How does DeployOpen support relate to Teclib's support?
They cover different things. Teclib's support depends on your GLPI Network subscription, and the supplied subscription information ties level 3 support to the Enterprise self-hosted tier. DeployOpen plans, implements, customizes, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms in your infrastructure, and ongoing support is available as a retainer. DeployOpen is not an official partner, reseller or certified provider of Teclib, so it does not replace Teclib's product support or subscription entitlements. Confirm in writing which issues go to Teclib, which go to DeployOpen, and how the two handoffs work.
Who supports a community GLPI plugin when it breaks?
Usually the plugin's maintainers, and only as far as they are active, so check the repository's release history, open issues and compatibility notes for your GLPI version before you rely on a plugin. Teclib's support covers the plugins and tiers it sells, and that coverage does not extend automatically to third-party community code. If a community plugin becomes critical, a retainer can include monitoring, testing after each GLPI update, and a documented fallback, or your team can keep the plugin pinned to a tested version. Ask for the support boundary in writing before the plugin enters production.
How DeployOpen scopes GLPI plugin licensing work
DeployOpen plans, implements, integrates, hardens, backs up, upgrades and supports self-hosted GLPI inside your own infrastructure, whether that is your cloud accounts, data centers or an isolated network. Plugin licensing is part of that planning work. Before anything is bought or installed, the scope should record which plugins you need, whether each one is published by Teclib' under the GLPI Network subscription or is a community plugin, which GLPI version each plugin supports, and which entities and profiles will use it. DeployOpen can help you map those answers against the GLPI Network subscription levels and check them against the plugin's own documentation, so the decision is made from written facts rather than from assumptions about what a subscription includes.
Most engagements are fixed-scope. The deliverables, the plugins in or out of the build, the environments, the cutover approach and the acceptance checks are agreed in writing before work starts, and any change to that scope is recorded as a change to the agreement. Licensing questions belong in that document: who holds the subscription, who receives the key, which environments need it, and how renewals will be tracked. DeployOpen does not publish a price list. A quote follows from the written scope, so the inputs that move cost, such as the number of plugins, the number of agents and users, and the number of environments, should be stated clearly when you request one.
Some work continues after go-live. Upgrades to a new GLPI release, plugin version matching, licence renewals and security fixes recur over the life of the platform, and they can be handled through an ongoing support retainer agreed alongside the original scope. Ask any provider, DeployOpen included, to confirm in writing which of these items sit inside the retainer and which are billed as separate work. DeployOpen is not a Teclib partner or reseller, so subscription purchasing and Teclib support terms are confirmed directly with Teclib, and the GLPI Network subscriptions page is the place to check current plan details.
