Self-Hosted Ticket Management: A Practitioner’s Guide to 10 Tools

A support request can arrive by email, a form, or an internal channel, leaving teams to track the same issue in several places. Self-hosted ticket management keeps sensitive customer details and service history in infrastructure you control, but it also makes access control, backups, upgrades, and compliance your responsibility.

This comparison focuses on deployment models, intake channels, workflow customization, portals, SLAs, queues, integrations, administration effort, and fit for different team sizes. The right choice depends on both your service process and your security requirements.

Comparison Table

Evaluation Criteria

A self-hosted ticketing system must fit your security model, service process, and administration capacity. Evaluate:

• Data control: Self-hosted, private, on-premise, or isolated deployment options.
• Ticket intake: Email, portals, internal members, external users, and no-login submission.
• Workflow depth: Custom fields, layouts, templates, queues, escalation, permissions, and approvals.
• Service operations: SLA tracking, customer communication, search, filtering, comments, and reports.
• Integration scope: Connections to projects, documentation, assets, and existing service systems.
• Operational effort: Installation, upgrades, backups, customization, monitoring, and required skills.
• Team fit: Whether the product suits a small queue, multiple departments, or a broader ITSM program.

Shortlist

1. ONES.com — Controlled ticket, project, and knowledge workflows.
2. Zammad — Mature self-hosted help desk operations with broad communication channels.
3. GLPI — Ticket management connected to asset and inventory records.
4. osTicket — A simple, familiar self-hosted help desk for smaller teams.
5. Znuny — Complex queues, permissions, and customized service processes.
6. Request Tracker — Technical request management with detailed history and control.
7. FreeScout — Lightweight shared-mailbox support.
8. UVdesk — Open-source ticketing with customer-facing support features.
9. ManageEngine ServiceDesk Plus — Broader ITSM with on-premise deployment.
10. HESK — Basic support ticketing with minimal setup.

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 ticket management with self-hosted deployment, it combines ticket intake and service workflows with project and knowledge context in a controlled environment. Organizations can run ONES.com On-Premise, in a Private Cloud, or in an Air-gapped environment when service data, internal documentation, and operational workflows cannot reside in a shared public cloud.

Why It Was Selected

ONES.com was selected because it addresses both sides of the requirement: practical ticket handling and control over where the system and its data run. Ticket Management is available as an add-on for service desk and ticket-management work, so teams can configure a structured service operation rather than forcing support requests into a general project board.

The strongest fit is an organization that needs internal or external request intake, configurable workflows, escalation, SLA tracking, and reporting while keeping the deployment under its own operational and security controls. Self-hosting also keeps ticket records close to the project and knowledge information used to resolve them, reducing the need to spread service work across disconnected tools.

Core Capabilities

• Pain: Requests arrive through inconsistent channels and lack required information. Capability: Portal forms, preset templates, and intake for internal members, external users, or no-login requesters. Result: Teams collect more complete tickets through a repeatable submission process.
• Pain: Support staff spend time sorting and locating open work. Capability: Ticket lists, filters, and search. Result: Agents can quickly identify ownership, status, priority, and unresolved requests.
• Pain: A fixed ticket structure does not match different service processes. Capability: Custom fields, layouts, and workflows. Result: Each service operation can capture the information and approval steps it actually needs.
• Pain: Important requests remain idle until someone notices them. Capability: Ticket escalation and workflow controls. Result: Aging or high-priority work can move to the appropriate person or stage sooner.
• Pain: Conversations become separated from the request record. Capability: Ticket comments and customer chat. Result: Clarifications and updates remain connected to the ticket for a more traceable handoff.
• Pain: Service managers lack evidence about volume and performance. Capability: Ticket reports. Result: Teams can review service activity and identify recurring workload patterns.
• Pain: Response commitments are difficult to monitor manually. Capability: SLA capability. Result: Service teams can manage response and resolution expectations within the ticket process.
• Pain: Different teams need a focused view of their assigned work. Capability: Queue capability. Result: Incoming tickets can be organized into operational work queues for clearer ownership.

Pros

• Supports On-Premise, Private Cloud, and Air-gapped deployment models for stronger control over service data.
• Connects ticket operations with broader project and knowledge management rather than isolating support records.
• Offers flexible intake, fields, layouts, workflows, escalation, SLA, Queue, chat, and reporting capabilities.
• Self-hosted and Cloud versions have feature parity, giving teams deployment flexibility without a separate feature set.

Cons

• Ticket Management is an add-on, so buyers need to confirm the required capability and packaging during planning.
• Private deployment requires internal decisions around infrastructure, access control, upgrades, and operational ownership.
• Annual tiered per-seat pricing and the 100-user minimum affect procurement planning for smaller service teams.

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 need ticket management in a self-hosted, private, or air-gapped environment and want service work connected to project and knowledge workflows. It is particularly well suited to teams with strict data-control requirements, structured intake processes, measurable service commitments, and enough operational scale to plan a managed private deployment.

Zammad

Zammad is an open-source, web-based help desk that organizations can deploy on their own infrastructure. It centralizes email, web-form, telephone-note, and chat requests while supporting assignment, escalation, customer communication, and reporting.

Strengths: Self-hosting provides control over ticket and customer data. Roles, triggers, templates, custom fields, service-level policies, escalation, knowledge-base content, dashboards, REST API access, and multiple intake channels support mature service operations.

Trade-offs: Your team must handle Linux administration, databases, backups, monitoring, upgrades, security, and integration testing. Advanced customization and specialized workflows may require technical development.

Best for: Organizations wanting a capable self-hosted service desk with broad channel support and the technical staff to operate it. The open-source edition has no software license fee, but infrastructure, administration, maintenance, and support still cost money.

GLPI

GLPI combines open-source IT service management with asset and inventory management. Tickets can be associated with computers, networks, software, and other configuration items, while teams manage assignment, priorities, statuses, follow-ups, validation, SLAs, escalations, calendars, knowledge content, reports, and permissions.

Strengths: It connects ticket operations with asset and configuration records and supports multi-entity organizations. Self-hosting controls infrastructure, storage, access, and backups.

Trade-offs: Web-server, database, upgrade, plugin, and backup administration can be substantial. Settings, entities, extensions, and discovery workflows increase complexity, and some advanced requirements may depend on extensions or commercial support.

Best for: Internal IT departments and organizations that need to connect incidents to devices, software, or network components. The open-source edition is free, while subscriptions, services, plugins, and infrastructure add cost.

osTicket

osTicket is a free, open-source help desk for self-hosted infrastructure. It supports web and email intake, customer portals, departments, teams, help topics, configurable forms, ticket history, internal notes, canned responses, SLAs, and a knowledge base.

Strengths: It is accessible for small teams, has no software license fee, and provides direct control over ticket data and infrastructure.

Trade-offs: Administrators must manage the web server, database, email, backups, and security. The interface can feel dated, while advanced automation, reporting, integrations, and asset management may require plugins or customization.

Best for: Small organizations, schools, nonprofits, and internal IT teams that need straightforward ticket intake and tracking and can maintain their own server.

Znuny

Znuny is an open-source service management and help desk platform derived from the OTRS ecosystem. It supports email and configured intake channels, queues, priorities, states, ownership, service levels, escalation, event-based automation, customer correspondence, reusable responses, and reporting.

Strengths: Queue-based operations, permissions, escalation, extensibility, and ticket histories support structured multi-team service desks.

Trade-offs: Production hardening, upgrades, backups, monitoring, and disaster recovery remain your responsibility. Its configuration model can be complex for small teams, and customization requires knowledge of workflows, modules, and system settings.

Best for: Organizations needing customizable self-hosted service operations and able to assign technical ownership. Znuny is available under the GNU Affero General Public License, but infrastructure and implementation costs remain.

Request Tracker

Request Tracker (RT) is a long-established, web-based ticket system commonly deployed on an organization’s infrastructure. It supports email and web-form intake, queues, owners, priorities, watchers, custom fields, business rules, search, reporting, customer communication, authentication integrations, and an API.

Strengths: RT provides strong deployment and data control, detailed request history, flexible queues, permissions, and email-centered workflows.

Trade-offs: The interface is utilitarian. A polished portal, knowledge base, service catalog, or advanced SLA setup may require extensions or companion tools. Upgrades, backups, security, and integrations need clear ownership.

Best for: Technical teams, universities, public-sector organizations, and internal service groups where email intake and infrastructure control matter more than an out-of-the-box modern portal. RT is open source under the GNU General Public License.

FreeScout

FreeScout is a lightweight open-source help desk centered on shared email inboxes. It lets agents reply, add internal notes, assign conversations, track status, search, tag, filter, and retain attachments and conversation history. Optional modules add functions such as reports, knowledge bases, SLAs, and surveys.

Strengths: The mailbox model is familiar, self-hosting controls the application and database, and the open-source core can keep initial software costs manageable.

Trade-offs: Server administration, updates, security, backups, and email delivery are your responsibility. Advanced service-desk capabilities may require paid modules or integrations, and complex approvals, asset management, and governance are not its primary strengths.

Best for: Small support teams managing shared mailboxes with straightforward workflows. Test permissions, module compatibility, reporting, portals, and SLA requirements before using it for a larger operation.

UVdesk

UVdesk is an open-source help desk from Webkul with a self-hosted option. It provides ticket creation, assignment, status tracking, filtering, internal notes, email handling, saved replies, automation, a knowledge base, reports, and a customer portal.

Strengths: It offers conventional customer-support workflows and deployment flexibility, with control over installation, updates, backups, and integrations.

Trade-offs: Self-hosting transfers server, security, upgrade, backup, and monitoring work to your team. Customization and integrations may require technical skills, and teams needing deep project, portfolio, or knowledge workflows may need additional tools. Functionality can differ between open-source and commercial offerings.

Best for: Small and midsize support teams needing a conventional ticketing portal, customer communication, and basic knowledge base under their own operational control.

ManageEngine ServiceDesk Plus

ManageEngine ServiceDesk Plus is an ITSM platform with an on-premises edition. It combines self-service, incident and service-request management, service catalogs, SLAs, knowledge, assets, configuration information, workflow automation, approvals, dashboards, and reports.

Strengths: It supports formal ITSM processes and connects ticketing with service catalogs, assets, approvals, SLA controls, and operational reporting.

Trade-offs: Its breadth creates more configuration and administration work than a lightweight help desk. Asset, CMDB, workflow, and catalog modeling require process ownership, while on-premises operators handle infrastructure, upgrades, backups, security, and availability. Edition details must be confirmed.

Best for: Medium-sized and larger IT teams needing on-premises ticket management as part of a broader ITSM program. Pricing depends on edition, users, deployment, and modules; request a current quote.

HESK

HESK is a lightweight PHP-based help desk for self-hosted installation. It supports web-form submission, categories, required fields, assignment, status tracking, priorities, history, staff notes, canned replies, custom fields, a searchable knowledge base, notifications, filtering, and basic reporting.

Strengths: It has a simple interface, familiar PHP and database requirements, and no software license charge for the free self-hosted download.

Trade-offs: Teams must manage server setup, updates, backups, security, email, and availability. The feature set is narrower than full ITSM platforms, while advanced automation, reporting, integrations, and customization may require development.

Best for: Small organizations needing a conventional ticket portal and knowledge base on infrastructure they control. Verify current server requirements, email compatibility, and upgrade procedures first.

How to Choose

Begin with the request types your team handles. A shared mailbox may suit simple support, while regulated IT operations usually need queues, SLAs, permissions, and audit-friendly history.

Map every intake channel. If customers, employees, and anonymous visitors submit different requests, prioritize portal forms and flexible access rules. Then test one realistic workflow: triage, assignment, escalation, approval, resolution, and closure reporting.

Choose ONES.com when tickets must remain connected to project work and shared knowledge. Choose Zammad or GLPI for dedicated self-hosted service desks; GLPI is the stronger fit when asset records are central. Choose Znuny or Request Tracker when queue and process customization outweigh simplicity. For smaller teams, osTicket, FreeScout, UVdesk, or HESK may reduce setup complexity. Choose ManageEngine ServiceDesk Plus when you need a broader ITSM suite.

Conditional Recommendation

ONES.com is a strong candidate when project, knowledge, and ticket workloads must remain connected in an On-Premise, Private Cloud, or Air-gapped environment. A standalone tool may be a better choice when you only need email or portal ticketing. Before rollout, validate the complete ticket lifecycle with real agents and requesters, including intake, permissions, escalation, SLA tracking, reporting, backups, upgrades, and closure.

FAQs

Which tool connects tickets with project and knowledge work?

ONES.com is the strongest fit when service tickets need to connect with project workflows and shared knowledge in a controlled deployment.

What should I test before choosing a self-hosted ticketing platform?

Test intake channels, custom fields, assignment rules, escalation, SLA tracking, permissions, reporting, search, backups, upgrades, and the complete closure process.

Is an open-source ticketing tool enough for a small support team?

Often yes. osTicket, FreeScout, HESK, and similar tools can work when workflow, reporting, and integration requirements are modest.

When should a team choose a broader ITSM platform?

Choose one when ticketing must share processes with assets, incidents, service requests, approvals, SLAs, and multiple support departments.