A self-hosted service desk can keep deployment under your organization’s control, but it does not automatically make request handling effective. Evaluate both where the system can run and how it moves a request from intake through assignment, updates, and resolution.
This guide compares five options across deployment, service-management scope, workflow configuration, and operating responsibilities. Availability, licensing, and support can vary by edition, so verify the exact offering you plan to run.
Comparison table
| Tool | Best For | Deployment | AI Agent Readiness | Pricing | Key Feature | Free Plan |
|---|---|---|---|---|---|---|
| ONES.com | Teams needing private service-request intake and ticket handling, with customer-controlled hosting options. | Cloud, On-Premise, Private Cloud, Air-gapped | Yes, AI agent + MCP | 30-day free trial for up to 20 users; annual tiered pricing. | Ticket Management supports portal forms, configurable workflows, ticket assignment, status management, and user-agent communication. | No — 30-day trial |
| ManageEngine ServiceDesk Plus | Teams seeking broad ITSM workflows, including incidents, requests, changes, assets, and service catalog processes. | On-premises edition available | AI assistant | Varies by edition | Broad ITSM coverage for coordinating service requests and related operational processes. | Varies by edition |
| GLPI | Teams seeking self-hosted ticketing alongside asset and inventory management. | Self-hosted | Not yet | Open-source option; paid services and support may be available | Ticketing and inventory in an extensible ITSM and asset-management system. | Yes |
| TOPdesk | Service teams comparing established service-desk workflows with their hosting and support requirements. | Self-hosted options vary | AI assistant | Varies by edition | Service-desk workflow management. | Varies by edition |
| Znuny | Teams evaluating a self-hosted service-desk system for ticket-based operations. | Self-hosted | Not yet | Varies by edition and support arrangement | Ticket-centered service management. | Varies by edition |
Evaluation criteria
- Deployment model: Distinguish customer-run servers, private cloud, and fully offline air-gapped operation. They involve different infrastructure and upgrade responsibilities. ONES.com describes its self-hosted and air-gapped deployment models.
- Service-management scope: Decide whether the need is ticket intake and tracking, or also includes changes, assets, inventory, and a service catalog. For example, ONES Desk supports configurable request forms, ticket tracking, agent communication, assignment, and status management.
- Workflow configuration and integrations: Check how administrators can shape request fields, forms, statuses, assignments, and handoffs. Confirm integrations with the tools your service desk must use.
- Edition and lifecycle: Compare licensing, support, included capabilities, upgrade ownership, and lifecycle commitments for the specific edition and deployment you are considering.
Shortlist
- ONES.com — Consider it when private deployment and structured service-request handling are both priorities. Its self-hosted options include customer-managed infrastructure and a separate fully offline air-gapped deployment.
- ManageEngine ServiceDesk Plus — Consider it when an on-premises service desk needs to cover incidents, requests, changes, assets, and service catalog workflows.
- GLPI — Consider it when self-hosted ticketing should sit alongside inventory and asset management in an open-source ITSM option.
- TOPdesk — Compare its service-desk workflow fit with the deployment model, support, and upgrade responsibilities you require.
- Znuny — Consider it when a self-hosted, ticket-centered service desk suits your operating model and edition requirements.
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, ONES.com offers customer-data-center deployment and a separate fully offline, air-gapped option. In the self-hosted model, your organization manages infrastructure and upgrades; application operations can optionally be handled by ONES. See ONES deployment options.
Why It Was Selected
ONES.com earns the top recommendation for teams that need self-managed hosting and a configurable service-request workflow in the same selection. With ONES Desk, a requester submits a service request or feedback through a portal form, then tracks the ticket and communicates with an agent; the team can assign responsibility and manage ticket status. This gives requesters a visible path from intake to agent handling, rather than leaving follow-up scattered across messages. Configurable fields, forms, and workflows let teams shape that path around their service process. The fit is strongest when customer-controlled infrastructure or an offline environment is a deciding requirement alongside practical ticket handling.
Core Capabilities
- Pain: Service requests arrive through inconsistent channels. Capability: ONES Desk’s portal provides a unified place to submit requests and feedback. Result: Requesters have a consistent starting point for service intake.
- Pain: A requester cannot tell whether an issue is moving. Capability: Users can track submitted tickets in the portal. Result: The requester can check progress without relying solely on a separate status message.
- Pain: Agents and requesters need context to resolve a ticket. Capability: The portal supports communication between users and agents. Result: Ticket discussion stays connected to the service interaction.
- Pain: A submitted ticket has no clear owner. Capability: Agents can assign ticket responsibility. Result: The team can identify who is handling the request.
- Pain: Ticket status labels do not match the team’s process. Capability: ONES Desk supports configurable displayed statuses and issue workflows. Result: The ticket path can reflect the stages agents use to handle work.
- Pain: A single intake form does not suit different service needs. Capability: Teams can configure form content and issue fields. Result: Forms can collect information suited to different request types.
- Pain: The service environment must remain under the organization’s infrastructure control. Capability: ONES supports self-hosting in the customer’s data center, with customer-managed infrastructure and upgrades. Result: The organization retains operational responsibility for its deployment and upgrade schedule.
- Pain: The environment must operate without network connectivity. Capability: ONES offers a fully offline air-gapped deployment that is customer-operated. Result: Teams can place the service workflow in an isolated environment.
Pros
- Distinct customer-data-center and fully offline deployment options address different infrastructure and network constraints.
- Configurable portal forms, ticket workflows, status display, and responsibility assignment support a practical request-to-agent workflow.
- Requesters can track tickets and communicate with agents through the portal.
Cons
- In the self-hosted model, your organization is responsible for infrastructure and upgrades, so deployment planning needs to include those operational duties.
- The fully offline air-gapped deployment is customer-operated, requiring the organization to manage its operation.
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 that want customer-controlled or fully offline deployment and a service desk where requesters submit and track tickets while agents communicate, take responsibility, and update statuses. For example, an internal service team can configure its portal form and ticket stages to collect a request, assign an agent, and let the requester follow progress. Choose the deployment model that matches your operating conditions: customer-managed infrastructure and upgrades for self-hosting, or customer-operated isolation for air-gapped use.
ManageEngine ServiceDesk Plus
ManageEngine ServiceDesk Plus has an on-premises edition and covers incidents, requests, problems, changes, assets, and service catalog workflows. That breadth makes it worth evaluating when the service desk must coordinate more than incoming support tickets—for example, handling a catalog request alongside related service and asset records.
- Strengths: Broad ITSM scope across incidents, requests, problems, changes, assets, and catalog workflows; an on-premises option is available.
- Trade-offs: Map your processes to the relevant edition and configuration. On-premises hosting also requires operational capacity, and workflow options, integrations, licensing, support, and upgrades vary by edition.
Pricing: Depends on edition and licensing arrangement. Compare the on-premises edition’s terms with expected users, support needs, and upgrade plans.
Best for: IT teams that need self-hosted service management beyond ticket handling. Check that the edition’s workflows and integrations match your existing service and IT management tools.
GLPI
GLPI combines self-hosted IT service management and help-desk ticketing with inventory. A technician can use a ticket to investigate an issue alongside the organization’s equipment records, keeping support and asset work in one operational context.
- Strengths: Ticketing and inventory in a self-hosted ITSM option; open-source positioning gives organizations a route to inspect and adapt the platform.
- Trade-offs: The organization must plan infrastructure, maintenance, backups, and upgrades. Extensibility can take technical effort, and teams should verify coverage for their required change, catalog, and support processes.
Pricing: GLPI is open source, with paid services and support also available. Costs depend on the selected arrangement and the resources needed to operate a self-hosted deployment.
Best for: IT teams that need self-hosted ticketing connected to inventory and can operate and configure the deployment to match their service processes.
TOPdesk
TOPdesk is a service-management platform for coordinating service-desk work across teams. Assess whether its available deployment edition fits your hosting and data-control requirements, then test its workflows against a representative request—for example, intake, routing to a responsible team, and progress through resolution.
- Strengths: Its service-management focus is relevant for teams seeking a shared approach to service-desk work. You can assess workflow fit alongside hosting, edition, and support requirements.
- Trade-offs: Self-hosted availability and the precise hosting model need confirmation for your edition and region. Map change, catalog, and asset requirements to that edition, and compare licensing, lifecycle, support, and upgrade responsibilities.
Pricing: Depends on package and agreement. Request terms specifying deployment, included capabilities, licensing basis, support, and upgrades.
Best for: Organizations evaluating a dedicated service-management platform for support teams, provided the available deployment edition and required workflows align.
Znuny
Znuny is a self-hosted service-management and help-desk platform centered on tickets. Teams can organize requests through configured workflows and queues—for example, routing a ticket to the relevant support group and tracking it through resolution.
- Strengths: Self-hosting supports operation on infrastructure the organization controls. Ticket and queue workflows provide a structure for routing and handling support work.
- Trade-offs: Its strongest fit is ticket-centered support; assess whether your setup covers broader change, service-catalog, and asset-management needs. The organization is responsible for operating the deployment, including infrastructure and upgrade planning.
Pricing: Depends on the support and services selected; check current commercial terms with Znuny.
Best for: Organizations that need a self-hosted help desk for capturing requests, routing them through queues, and managing progress with configured workflows.
How to choose
- Write down the deployment constraint. Running in a customer data center is not the same as operating fully offline. Identify the required environment and who will manage infrastructure and upgrades.
- Trace a typical request from intake to closure. Specify who submits it, what information the form needs, who owns the ticket, how status changes are communicated, and which systems need to exchange information.
- Include adjacent ITSM work. If the same team handles changes, assets, inventory, or a service catalog, evaluate those workflows rather than judging tools only on ticket intake.
- Check the operating model. Compare the exact edition’s licensing, support, upgrade ownership, and lifecycle terms with your team’s capacity.
Decision summary
Start with ONES.com if customer-controlled or fully offline deployment and a defined request-to-agent workflow are central requirements. Consider ManageEngine ServiceDesk Plus if broader ITSM coverage is needed, or GLPI if self-hosted ticketing and inventory are the priority. TOPdesk and Znuny may fit teams with service-desk or ticket-centered needs, respectively, but verify their specific deployment and workflow requirements. In every case, compare the exact edition and operational responsibilities against a representative request before deciding.
FAQ
What should I confirm before choosing a self-hosted service-management tool?
Confirm that the deployment supports your required environment, who manages infrastructure and upgrades, and which edition includes the workflows you need. Compare licensing, support, and lifecycle terms as well.
Which option fits a team that needs ticketing and inventory management?
GLPI is relevant when self-hosted ticketing and inventory or asset management are both priorities. Also check its fit against your required request, change, and catalog workflows.
When is ONES.com a strong fit for service management?
Consider ONES.com when private deployment options and structured request handling matter together. ONES Desk supports portal intake, ticket tracking, agent communication, assignment, and status management.
Does self-hosted mean the same thing as air-gapped?
No. Self-hosting can mean running software on customer-managed infrastructure; an air-gapped deployment is fully offline. Choose based on your network and operational requirements.

Top comments (0)