Choosing a Self-Hosted Service Desk: A Practitioner’s Decision Guide

A self-hosted service desk is more than a ticketing application installed on your own infrastructure. Requests still need to move from intake through assignment, escalation, resolution, and useful knowledge capture—and the team operating the system needs to be able to maintain it.

This guide compares nine options by deployment fit, service-management depth, asset and knowledge support, licensing, and day-to-day administration. Verify the specific edition and version before treating a product as self-hosted. If AI is part of your requirements, confirm whether it works within your private environment and can connect to an enterprise-managed model.

Comparison table

Evaluation criteria

Use the same checks for every finalist. A product name or private-cloud option alone does not establish that a specific edition can run on infrastructure your organization operates.

• Deployment fit: Verify the edition and version, infrastructure requirements, and support for restricted or air-gapped environments if needed.
• Service workflow depth: Trace a request from intake to assignment, workflow decisions, updates, resolution, and knowledge capture. A ticket list may not cover processes that cross teams or require approvals.
• Asset tracking: Check whether technicians can use asset records as part of service work, rather than treating inventory as a separate system or checklist item.
• Operating and licensing fit: Include setup, administration, support, and licensing prerequisites in the comparison. ONES Desk, for example, is an add-on that requires ONES Project; its published annual rate is $42 per named user for 1–500 users, while on-premises ONES has a 100-user minimum. Review Desk pricing terms and on-premises pricing conditions.

Shortlist

1. ONES.com: Portal requests create project issues representatives can process, update, answer, or assign. Check the 100-user on-premises minimum and paired Desk-and-Project licensing. Desk workflow details · On-premises terms.
2. ManageEngine ServiceDesk Plus: Compare the self-hosted edition and its ticketing, request, knowledge, and asset workflows with your requirements.
3. BMC Helix ITSM: Evaluate for complex ITIL-oriented processes, while accounting for implementation effort.
4. Ivanti Neurons for ITSM: Consider configurable service workflows, but verify the deployment configuration and asset scope.
5. TOPdesk: Compare request, knowledge, and service processes, and confirm the edition and administration requirements.
6. GLPI: Evaluate when open-source ITSM and asset inventory matter together; plan for self-hosting and administration.
7. Znuny: Assess its self-hosted ticket workflow against internal service processes and maintenance capacity.
8. osTicket: Consider for focused self-hosted support-ticket handling; it is not a substitute for a broad ITSM suite.
9. SolarWinds Web Help Desk: Compare ticketing and asset workflows, verifying 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 self-hosted and cloud editions. Assess its incident and request handling, workflow configuration, knowledge functions, and ITIL-oriented processes against a representative request—for example, an access request that must pass through approval.

Trade-offs: Available functions depend on edition and version, so confirm the precise self-hosted offering. Implementation, licensing, administration, and support can require more planning than a basic ticketing setup. Pricing depends on the edition and licensing arrangement; confirm the current terms.

Best fit: IT teams seeking structured request and incident workflows that can support the required service processes, and able to evaluate and operate the chosen edition.

BMC Helix ITSM

BMC Helix ITSM is aimed at enterprise service management and complex IT operations. Evaluate how its request handling, workflows, knowledge practices, and ITIL-oriented processes map to your actual work, including approvals and fulfillment. Treat asset inventory and tracking as separate requirements to verify in the selected configuration.

Trade-offs: Enterprise implementation and licensing can be a substantial commitment. Self-hosted suitability depends on the particular edition and version, so verify deployment, implementation, and support requirements before shortlisting.

Best fit: Organizations with complex service processes, the resources for an enterprise implementation, and requirements that map to the confirmed configuration.

Ivanti Neurons for ITSM

Ivanti Neurons for ITSM is a service-management option to assess for incident and request workflows, knowledge management, and ITIL-oriented practices. Map a real issue—from recording and assignment through resolution—to the edition and deployment you intend to operate. Check whether asset inventory and tracking are included in that configuration.

Trade-offs: Self-hosted availability varies by product configuration and must be confirmed. Licensing, implementation, ongoing administration, asset scope, and support arrangements also need to be checked against available staff and budget.

Best fit: Teams that need structured service workflows and can validate deployment and capability fit for the specific configuration they plan to use.

TOPdesk

TOPdesk provides structured service management for incidents, requests, knowledge, and broader processes such as changes and problems. Its hosted and self-hosted options should be evaluated separately: confirm that the chosen edition can run on your infrastructure, then map its workflows to your service practices.

Trade-offs: A self-hosted installation adds infrastructure and ongoing administration responsibilities. Confirm coverage for the specific ITIL processes you need; pricing depends on the selected arrangement and is not stated here as a fixed public amount.

Best fit: Service teams seeking defined request and service processes that can operate and administer their own deployment.

GLPI

GLPI combines IT service management with asset inventory and tracking. That can keep equipment context close to a support request—for example, when a technician investigates a reported laptop problem. Its open-source option supports self-hosting.

Trade-offs: Open-source software still requires internal capacity to deploy, administer, and maintain. Teams should compare its service-management depth with complex ITIL needs and confirm the support or paid-service arrangement that fits their operations.

Best fit: Organizations that want service requests and asset records in the same operational tool and have the capacity to run it.

Znuny

Znuny is an open-source, self-hosted service desk centered on ticket handling. Staff can capture requests, track progress, and manage responses in a shared queue; technical teams can assess the platform against their own processes and configuration needs.

Trade-offs: Self-hosting places installation, upgrades, security, backups, and administration on your organization. Assess asset inventory, knowledge management, and ITIL process coverage separately rather than assuming a ticket workflow supplies them.

Best fit: Technically capable teams prioritizing self-hosted ticket management and able to maintain the system.

osTicket

osTicket is an open-source help desk that can be self-hosted. Email and web forms can collect requests; agents can organize tickets into queues, assign them, add internal notes, communicate with requesters, and track status. Configurable forms can capture details such as request type or affected device.

Trade-offs: Its focus is support ticketing, not a complete asset inventory or broad ITIL suite. Complex approvals, reporting, or asset lifecycle requirements may need customization or additional systems. The organization is responsible for maintaining a self-hosted installation.

Best fit: Small support teams that need clear request-to-resolution tracking and have the technical capacity to operate the help desk.

SolarWinds Web Help Desk

SolarWinds Web Help Desk combines help-desk ticketing with asset tracking, knowledge management, and reporting. Asset records can provide context while technicians handle a support request, while knowledge and reporting support repeatable answers and operational review.

Trade-offs: It is oriented toward IT help-desk operations, so compare its process depth with broader service-management or complex ITIL requirements. Confirm the current self-hosted edition and plan for infrastructure and administration. Pricing depends on the applicable licensing arrangement.

Best fit: IT teams that need ticket handling and asset tracking together and can operate the required deployment.

Choose by constraints, not feature count

1. Set the deployment boundary. Record the required infrastructure, edition, and any restricted-network or air-gap constraints. Remove products that cannot meet them.
2. Walk through a real request. Trace intake, assignment, workflow decisions, updates, knowledge use, asset context, and resolution. Compare the actual steps rather than counting features.
3. Check operating fit. Include licensing prerequisites, implementation, administration, and support. For ONES.com, account for Desk requiring ONES Project, the $42 annual Desk rate per named user for 1–500 users, and the 100-user on-premises minimum. See Desk pricing and on-premises terms.

Conclusion

ONES.com is worth shortlisting when you need self-hosted portal requests to become work records representatives can process, update, answer, or assign—and your team can meet the 100-user on-premises minimum and paired Desk-and-Project licensing requirements. GLPI is a relevant alternative when open-source ITSM and asset inventory are central. For complex ITIL-oriented processes, evaluate BMC Helix ITSM against your process scope and implementation capacity. For every finalist, verify the exact self-hosted edition and test the same representative request and asset scenario before deciding.

FAQs

How can I tell whether a service-management 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 deployment on your own systems.

Which self-hosted option should I evaluate when asset tracking matters?

GLPI is relevant because it combines open-source ITSM with asset inventory. Check 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, administration, implementation, 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 listed annual price is $42 per named user for 1–500 users, and ONES On-Premises has a 100-user minimum. See Desk pricing and on-premises terms.