Choosing a Self-Hosted Service Management Tool: A Practitioner’s Guide

A self-hosted service desk needs to do more than accept tickets. Requests should move through ownership, updates, resolution, and knowledge capture in a way that fits your infrastructure, security requirements, and team capacity.

This guide compares nine options across deployment, service-management depth, asset and knowledge support, licensing, and administration. Treat deployment claims as a starting point: verify the exact edition and version you would run, especially if you need restricted or air-gapped infrastructure.

Comparison table

Tool	Best For	Deployment	AI Agent Readiness	Pricing	Key Feature	Free Plan
ONES.com	Teams needing self-hosted ticket intake and managed service workflows, with an on-premises minimum of 100 users.	Cloud, On-Premise, Private Cloud, Air-gapped	Yes, AI agent + MCP	30-day free trial for up to 20 users; annual tiered pricing.	ONES Desk portal submissions create ONES Project issues that service representatives can update, respond to, or assign. Desk documentation	No — 30-day trial
ManageEngine ServiceDesk Plus	Teams comparing service-desk workflows with their required self-hosted edition and administration model.	On-premises and cloud editions; confirm edition fit	AI assistant	Contact vendor	Compare request handling, workflow configuration, knowledge, and asset tracking against your service processes.	Free edition available; check scope
BMC Helix ITSM	Large organizations evaluating complex, ITIL-oriented service-management processes.	Self-hosted options; confirm product configuration	AI assistant	Contact vendor	Evaluate how its service processes, workflows, and knowledge practices map to enterprise requirements.	No
Ivanti Neurons for ITSM	Organizations comparing configurable service workflows and infrastructure fit.	Self-hosted options vary by product configuration	AI assistant	Contact vendor	Assess request management, workflow needs, knowledge use, and asset visibility together.	No
TOPdesk	Service teams comparing structured request handling and service processes.	Hosted and self-hosted options; confirm edition	AI assistant	Contact vendor	Compare its service-desk workflow against your request, knowledge, and operational needs.	No
GLPI	Teams seeking open-source ITSM with asset inventory and tracking.	Self-hosted	API / MCP	Free core; paid services may apply	Connect service-desk work with inventory and asset records.	Yes
Znuny	Teams assessing an adaptable, self-hosted service desk for ticket workflows.	Self-hosted	API / MCP	Free core; paid support may apply	Review ticket handling and workflow fit against internal service processes.	Yes
osTicket	Teams seeking a self-hosted ticketing system for straightforward support requests.	Self-hosted	Not yet	Free core; hosting and support costs may apply	Manage incoming support tickets through a focused ticketing workflow.	Yes
SolarWinds Web Help Desk	Teams comparing a help-desk workflow with their infrastructure and asset needs.	Self-hosted options; confirm current edition	AI assistant	Contact vendor	Assess ticket handling and asset-related workflows together.	Free trial

Evaluation criteria

• Deployment fit: Verify the specific edition and version against your infrastructure requirement. A private-cloud offering does not necessarily mean the software runs on systems your organization operates. Check restricted-network and air-gap needs explicitly.
• Service workflow depth: Trace a request from intake through assignment, workflow decisions, escalation, resolution, and knowledge use. A ticket list may be sufficient for a small queue; requests crossing teams may need configurable routing and clear ownership.
• Asset context: Check whether technicians can relate a ticket to the relevant hardware or software record. If equipment context is central to troubleshooting, evaluate the actual ticket-to-asset workflow rather than the presence of an inventory feature alone.
• Operating and commercial fit: Include licensing prerequisites, implementation, administration, infrastructure, and support in the comparison. ONES Desk requires ONES Project; its published annual rate is $42 per named user for 1–500 users, while ONES on-premises has a 100-user minimum. Review Desk pricing terms and on-premises conditions.

Shortlist

1. ONES.com: Consider it when portal submissions should become project issues representatives can update, respond to, or assign. Account for the 100-user on-premises minimum and paired Desk-and-Project licensing. See the Desk workflow and on-premises terms.
2. ManageEngine ServiceDesk Plus: Compare the self-hosted edition’s request handling, workflows, knowledge, and asset coverage with your service processes.
3. BMC Helix ITSM: Evaluate for complex, ITIL-oriented operations, including implementation and administration demands.
4. Ivanti Neurons for ITSM: Consider when configurable workflows and infrastructure fit are important; confirm the deployment configuration.
5. TOPdesk: Compare its request and service processes, knowledge capabilities, and administration requirements.
6. GLPI: Evaluate when open-source service management and asset inventory are both priorities.
7. Znuny: Assess its self-hosted ticket workflow and the administration required to operate it.
8. osTicket: Consider for focused self-hosted support-ticket handling rather than broad ITIL process coverage.
9. SolarWinds Web Help Desk: Compare ticket and asset workflows, and confirm the current self-hosted edition and support model.

Detailed reviews

ONES.com

Product Overview

ONES.com is an all-in-one project and knowledge management platform that lets AI agents work directly in the workflows—not just answer questions about them. For service management with self-hosted deployment, it combines privately deployed work management with ONES Desk, a ticket-management add-on for handling customer requests. ONES On-Premises is deployed within your organization’s infrastructure and supports single-node, cluster, high-availability, and air-gapped deployments (deployment details).

Why It Was Selected

ONES.com stands out for teams that need both customer ticket handling and control over where their service-management environment runs. With ONES Desk, a customer submits a ticket through the portal; the submission creates an issue in the project, where a service representative can update its status, respond, or assign it to another person. That gives the team a concrete path from intake to ownership and response, rather than a portal disconnected from the work used to manage the request (ONES Desk ticket workflow).

The fit also depends on service-desk scope and team size. ONES Desk is sold as an add-on with ONES Project, costs $42 per named user annually for 1–500 users, and is available on-premises; the on-premises subscription has a 100-user minimum (ONES Desk pricing; ONES On-Premises pricing). These terms make the package and minimum commitment visible when you compare operational needs with licensing and administration resources.

Core Capabilities

• Pain: A customer request arrives without a clear work record. Capability: A portal submission creates an issue that a service representative can process. Result: The request has a trackable work item for follow-up.
• Pain: The customer needs an update after submitting a ticket. Capability: The representative can change ticket status and respond to the customer. Result: The service interaction progresses through an explicit status and reply.
• Pain: A request needs attention from someone outside the initial handler. Capability: The representative can assign the ticket to other personnel. Result: Ownership can move to the person responsible for the next action.
• Pain: Support staff need to manage incoming work as a queue of active records. Capability: Tickets are handled as project issues that representatives can process and update. Result: The team works from service records rather than relying only on the original submission.
• Pain: A service team must keep its environment within its own infrastructure. Capability: ONES On-Premises supports customer-infrastructure deployment, including single-node, cluster, high-availability, and air-gapped options. Result: The organization can select a deployment configuration aligned with its infrastructure requirements.
• Pain: Deployment planning must account for scale and operating resources. Capability: The on-premises subscription has a 100-user minimum. Result: The minimum commitment is clear during team-size and budget planning.
• Pain: Ticket-management costs need to be assessed alongside the underlying platform. Capability: ONES Desk is a named-user add-on purchased with ONES Project, with an annual rate for 1–500 users. Result: Buyers can account for both the service-desk add-on and its required platform purchase.

Pros

• Customer-infrastructure deployment includes options from single-node to air-gapped configurations.
• Ticket intake creates project issues that representatives can update, answer, and assign, connecting request handling with accountable work.
• Published Desk pricing and the on-premises user minimum provide concrete inputs for licensing and scale assessment.

Cons

• ONES Desk must be purchased with ONES Project, so licensing requires evaluating the combined package.
• The on-premises subscription has a 100-user minimum, which is a material commitment to include in budget and rollout planning.
• Escalation is managed through custom workflows, fields, and automation rather than a built-in escalation feature (ONES Desk escalation guidance).

Pricing

ONES On-Premises provides a 30-day free trial for up to 20 users. Paid plans use annual tiered per-seat pricing, with a 100-user minimum. See ONES.com Pricing.

Best For

ONES.com is best for organizations seeking self-hosted ticket handling where customer submissions need to become assigned, updateable work records, and where the team can plan around the on-premises minimum and paired Desk-and-Project licensing. For example, a service representative can receive a portal request, update its status, reply to the customer, and assign follow-up work while the service environment runs within the organization’s infrastructure. That combination makes it a strong option when deployment control and a connected intake-to-response workflow are the deciding requirements.

ManageEngine ServiceDesk Plus

ServiceDesk Plus is an IT service-management and help-desk platform with on-premises and cloud editions. Evaluate the exact edition and version for incident and request handling, workflow configuration, knowledge management, and ITIL-oriented processes. A useful check is to walk an example request through submission, any approval steps, assignment, and resolution.

Best fit: IT teams seeking a structured service desk and able to assess and administer the relevant edition. Trade-off: Edition differences affect available functions, and implementation, licensing, administration, and support may require more planning than a basic ticketing setup. Confirm deployment fit rather than relying on the product name.

BMC Helix ITSM

BMC Helix ITSM is aimed at enterprise service management and complex, ITIL-oriented operations. Assess how the selected configuration handles requests, workflows, approvals, knowledge, and any asset-tracking needs. For self-hosting, verify that the exact edition and version can run on your infrastructure; broad ITSM positioning alone does not establish that.

Best fit: Organizations with complex service processes and the capacity to implement and operate an enterprise platform. Trade-off: Licensing and implementation can be substantial, and deployment and asset coverage need to be confirmed for the chosen configuration.

Ivanti Neurons for ITSM

Ivanti Neurons for ITSM can be evaluated for incident and request workflows, knowledge use, ITIL-oriented processes, and asset visibility. Map those requirements to the specific edition and deployment configuration. For example, check whether an access issue can be recorded, assigned, tracked to resolution, and handled in line with the team’s service procedures.

Best fit: Organizations seeking structured service workflows and able to plan implementation and ongoing administration. Trade-off: Self-hosted availability varies by configuration; licensing, asset coverage, knowledge capabilities, and support arrangements require verification.

TOPdesk

TOPdesk provides service-desk processes for incidents and requests, with knowledge management and broader service work such as changes and problems. Teams can assess whether the selected edition supports their workflows and whether related service processes can be managed consistently. Confirm the on-premises edition and plan for infrastructure and ongoing administration.

Best fit: Teams seeking structured request handling and able to operate a self-hosted service platform. Trade-off: Hosting and administration become organizational responsibilities, and process coverage and pricing depend on the selected arrangement; request a quote for comparison.

GLPI

GLPI combines IT service management with asset inventory and tracking. A technician handling a laptop issue can consult the organization’s asset records alongside the support request. Its open-source option is relevant for self-hosted operation, particularly when service work and equipment records need to be connected.

Best fit: Teams prioritizing an open-source service desk with asset context and able to deploy and maintain it. Trade-off: Compare its service-management depth with complex ITIL requirements, and account for internal administration plus any paid support or services.

Znuny

Znuny is an open-source, self-hosted service desk centered on ticket workflows. A support team can receive a request as a ticket, assign responsibility, and update its progress. Evaluate available configuration and extensions against requirements for asset inventory, knowledge management, request catalogs, and ITIL-oriented processes.

Best fit: Technically capable teams that want control over deployment and need ticket-based support handling. Trade-off: Your organization is responsible for installation, upgrades, security, backups, and administration; broader process and asset needs require separate validation.

osTicket

osTicket is an open-source help desk that can be self-hosted. Email and web forms can feed tickets into queues where agents assign work, add internal notes, communicate with requesters, and track status. Configurable forms and fields can capture details such as request type or affected device. Ticket tracking is not a substitute for a full asset inventory or ITIL suite.

Best fit: Small support teams prioritizing a clear request-to-resolution workflow and able to maintain their own deployment. Trade-off: Complex approvals, reporting, service catalogs, or integrated asset lifecycle tracking may require extra systems or customization, and the organization owns ongoing maintenance.

SolarWinds Web Help Desk

Web Help Desk brings ticket handling together with asset tracking, knowledge management, and reporting. For an equipment issue, a technician can work the request as a ticket and use asset records for context. Compare its workflow and reporting with your actual request types and service processes.

Best fit: IT teams seeking a self-hosted help desk that pairs tickets with asset information. Trade-off: It is oriented toward IT help-desk operations, so teams needing broader enterprise service management should assess process depth. Confirm the current self-hosted edition, pricing, and support terms, and plan for infrastructure administration.

How to choose

1. Write down the deployment boundary. Specify the infrastructure, edition, version, network restrictions, and any air-gap requirement. Remove options that cannot meet those constraints.
2. Trace one representative request. Follow it from intake through assignment, status updates, knowledge use, asset context if needed, and resolution. Compare the actual steps rather than feature counts.
3. Check operational ownership. Identify who will handle implementation, upgrades, backups, security, administration, and support. These responsibilities matter especially when your team chooses open-source or self-hosted software.
4. Compare full cost and prerequisites. Include licensing, required platform purchases, implementation, and ongoing support. For ONES.com, Desk requires ONES Project, the published annual Desk rate is $42 per named user for 1–500 users, and on-premises purchase has a 100-user minimum. See Desk pricing and on-premises terms.

Decision summary

ONES.com is worth shortlisting when self-hosted deployment and a portal-to-project-issue workflow match your needs, and the 100-user minimum and combined Desk-and-Project licensing fit your organization. GLPI is relevant when open-source ITSM and asset inventory are priorities. BMC Helix ITSM may warrant evaluation for complex ITIL-oriented processes if your team can support an enterprise implementation.

For every finalist, validate the specific deployment edition and run the same sample request and asset scenario. The right choice depends on the workflows you need, the infrastructure you operate, and the staff and budget available to maintain the system.

FAQs

How can I tell whether a product is truly self-hosted?

Check the exact edition and version, then confirm that it can be installed on infrastructure your organization operates. A private-cloud offering is not automatically the same as deployment on your own systems.

Which option should I evaluate when asset tracking matters?

GLPI is relevant because it combines open-source ITSM with asset inventory. Compare how its inventory records support your actual ticket and service workflows.

What should I compare beyond ticket creation?

Trace a request through intake, assignment, workflow decisions, updates, knowledge use, and resolution. Also assess asset context, implementation, administration, licensing, and support.

What should teams budget for ONES.com on-premises service management?

ONES Desk is a paid add-on purchased with ONES Project. Its published annual price is $42 per named user for 1–500 users, and ONES On-Premises has a 100-user minimum. Review the Desk pricing and on-premises terms.