A Practical Guide to Self-Hosted Ticket Management Tools

When requests arrive through email and web forms, ownership and status can be difficult to track. A self-hosted ticket system can give a team more control over its deployment, but it also means taking responsibility for operations such as maintenance, upgrades, backups, security, and availability.

The right choice depends on the work you handle: a shared support queue, internal IT requests connected to asset records, or a more structured IT service-management process. This guide compares the eight options listed in the source comparison across deployment, ticket handling, service-management fit, and operational effort.

Comparison table

Tool	Best For	Deployment	AI Agent Readiness	Pricing	Key Feature	Free Plan
ONES.com	Teams that want service requests handled within connected project and knowledge workflows	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 intake, configurable forms and workflows, ticket ownership, visible statuses, and customer replies	No — 30-day trial
Zammad	Teams evaluating self-hosted help-desk ticket handling	Self-hosted option	Not yet	See vendor pricing	Ticket management for support workflows	See vendor terms
GLPI	Internal IT teams that want ticketing alongside asset management	Self-hosted option	Not yet	See vendor pricing	Ticketing combined with IT asset inventory and service-management workflows	See vendor terms
osTicket	Small teams handling requests through email and web forms	Self-hosted option	Not yet	See vendor pricing	Email-to-ticket, web forms, queues, and SLAs	See vendor terms
Request Tracker (RT)	Technical and operations teams managing email-driven queues	Self-hosted option	Not yet	See vendor pricing	Flexible queues, permissions, and email-driven workflows	See vendor terms
FreeScout	Teams assessing a self-hosted shared-inbox support workflow	Self-hosted option	Not yet	See vendor pricing	Shared-inbox approach to support requests	See vendor terms
Chatwoot	Support teams considering self-hosted customer conversations	Self-hosted option	Not yet	See vendor pricing	Customer conversation handling	See vendor terms
ManageEngine ServiceDesk Plus	Organizations seeking commercial ITSM with an on-premises edition	On-premises edition	Not yet	See vendor pricing	Structured IT service-management workflows	See vendor terms

How to evaluate the options

• Deployment and edition terms: Confirm that the edition can run in the environment you control, and check applicable licensing, trial, and feature terms.
• Workflow fit: Decide whether you need a focused support queue, internal IT and asset workflows, or structured IT service management.
• Ticket handling: Trace how a request enters the system, reaches an owner or queue, changes status, and receives a response. Assess forms, email intake, permissions, SLAs, portals, and asset context as they apply to your work.
• Operating and budget fit: Include licensing as well as server upkeep, upgrades, backups, security, and availability planning. With self-hosting, operating capacity is part of the selection decision.

Shortlist by workflow

1. ONES.com: Consider it when requests need structured intake, an assigned owner, visible status, and customer replies. Its on-premises model runs in your data center, with infrastructure and upgrades managed by your team.
2. Zammad: Consider it for self-hosted help-desk ticket handling.
3. GLPI: Assess it when internal IT tickets need to sit alongside asset inventory and service-management work.
4. osTicket: Consider it for email-to-ticket and web-form intake, queues, and SLAs.
5. Request Tracker (RT): Assess it for email-driven requests organized through flexible queues and permissions.
6. FreeScout: Consider it when support work is organized around a shared inbox.
7. Chatwoot: Assess it when customer conversations are central to the support workflow.
8. ManageEngine ServiceDesk Plus: Evaluate it when commercial ITSM and an on-premises edition fit your organization.

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, ONES.com offers Ticket Management as an add-on, with a self-managed option that runs in your data center. Teams manage the infrastructure and upgrades themselves; the deployment page lists Kubernetes, bare-metal, and VM compatibility. Review ONES On-Prem deployment options.

Why It Was Selected

ONES.com stands out for organizations that need both control of the deployment environment and a practical way to receive, route, and work through service requests. In ONES Desk, someone submits a request or feedback through the ticket portal, the team assigns an owner and manages the ticket through a configured workflow, then replies and updates customer-visible status. The requester can return to the portal to follow progress and communicate with the team. That connected intake-to-response process makes ONES.com a strong first choice when a self-hosted service desk needs more than a place to log tickets. See ONES Desk portal and workflow details.

Core Capabilities

• Pain: A request arrives without the information the team needs. Capability: Configure ticket forms and fields for different feedback or service-request needs. Result: The team can collect relevant details at intake and work from a more usable ticket. ONES Desk forms and workflows.
• Pain: Staff need one place to submit an internal service request. Capability: Provide a ticket portal for requests and feedback. Result: Employees can submit and revisit tickets through a shared entry point. ONES Desk ticket portal.
• Pain: A ticket is received but no one is clearly responsible for the next step. Capability: Assign a ticket owner. Result: The service team has a named person to move the request forward. ONES Desk ticket handling.
• Pain: The team’s internal workflow is hard for the requester to follow. Capability: Configure workflows and externally displayed statuses. Result: Staff can manage work while customers see an understandable ticket status. ONES Desk workflow configuration.
• Pain: Requesters have to ask staff for progress updates. Capability: Let portal users view tickets and track progress. Result: The requester can check the ticket’s progress directly. ONES Desk ticket portal.
• Pain: A status change alone does not answer the requester’s question. Capability: Reply to customers and communicate through the portal. Result: The team can provide a response in the context of the submitted ticket. ONES Desk customer communication.
• Pain: A self-hosted deployment needs to fit the organization’s infrastructure choices. Capability: Run ONES in the customer’s data center, with Kubernetes, bare-metal, and VM compatibility listed. Result: The organization can assess deployment against its own environment and manage infrastructure and upgrades directly. ONES On-Prem deployment.

Pros

• Supports an end-to-end ticket path from portal intake through ownership, status updates, and customer replies.
• Configurable forms and workflows let teams shape intake and handling around different service-request needs.
• Self-hosted deployment places infrastructure and upgrade management with the customer.

Cons

• The self-managed deployment requires the organization to operate its infrastructure and handle upgrades.
• Ticket Management is offered as an add-on, so buyers should include it in their package and deployment planning.

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 self-hosted ticket management and a clear service workflow: a requester submits a structured ticket, the team assigns ownership and works it through configured statuses, and the requester can follow progress and communicate through the portal. It is especially relevant when the organization can manage its own infrastructure and upgrades and wants configurable intake and handling alongside customer-visible follow-through.

Zammad

Zammad is a help desk and ticketing system with a self-hosted option. It suits teams that want to receive and manage support requests in a shared ticket workflow while operating the deployment themselves.

Its help-desk focus is a reason to consider it for customer-support queues, rather than assuming it covers a broader ITSM or asset-management program. The source describes its shared ticket handling but does not specify detailed feature or edition terms; verify those against your workflow.

• Advantages: Self-hosted deployment and a shared workflow for organizing requests and coordinating follow-up.
• Trade-offs: Your team must plan for maintenance, upgrades, backups, security, and availability. Include administrator effort and current licensing terms in the operating budget.

Best fit: Support teams prioritizing self-hosted ticket handling and able to maintain the service.

GLPI

GLPI combines ticket handling with IT asset management and service-management workflows. That combination is relevant to internal IT teams that need to consider the equipment or services involved in a request—for example, handling a laptop issue alongside equipment records.

Advantages: Connects tickets and asset inventory, supports structured IT service work, and has a self-hosted option.

Trade-offs: Its combined scope can require more setup and process ownership than a basic shared inbox. Confirm that the intended edition and configuration cover your required channels, queue rules, permissions, and service-level processes. Plan for server upkeep, backups, upgrades, and availability. GLPI is open-source, with paid services and options also available; verify current licensing and service costs.

Best fit: Internal IT teams that want asset-aware service management and can operate the self-hosted system.

osTicket

osTicket is an open-source help desk with email-to-ticket and web-form intake, queues, and SLAs. Those capabilities map to a direct workflow: capture a request, place it in a working queue, and monitor handling against a response target.

Advantages: Its cited intake and queue features address common support-desk tasks and can be assessed against a concrete request path.

Trade-offs: A self-managed installation requires server administration, upgrades, backups, security, and availability planning. The described feature set centers on ticket intake and handling, so teams with more complex service-management needs should verify workflow fit. Open-source software does not remove infrastructure and staff-time costs.

Best fit: Small teams that need email and web-form intake, queues, and SLAs, and are prepared to operate the deployment.

Request Tracker (RT)

Request Tracker (RT) is suited to technical and operations teams that manage email-driven requests. Flexible queues can separate work areas, while permissions help shape access and responsibility. For example, a team could route facilities issues and technical incidents into different queues.

Advantages: Flexible queue organization, permission controls, and an email-based ticket workflow support defined team handoffs.

Trade-offs: Its strongest fit is queue-based technical or operations work. If you need a customer portal, asset-management workflow, or a broad commercial ITSM package, assess those requirements separately. Self-hosting also makes your team responsible for operations, maintenance, backups, upgrades, and availability.

Best fit: Teams that need email intake, separate queues, and permissions to organize internal work, and can maintain the supporting infrastructure.

FreeScout

FreeScout is a self-hosted help desk and shared-mailbox application for customer-support conversations. A team can handle messages sent to a support address as tickets in a shared interface, keeping the conversation available to multiple agents.

Advantages: The shared-inbox model provides a straightforward place for email-based teams to manage and answer customer conversations.

Trade-offs: The organization is responsible for server setup, updates, backups, and availability. Its email-first approach may not suit workflows that depend on broad ITSM processes or asset records. Check current licensing and any paid add-ons; infrastructure and administration remain separate costs.

Best fit: Support teams whose primary workflow is email and shared conversation handling, with staff available to maintain the deployment.

Chatwoot

Chatwoot focuses on customer conversations in a shared workspace and has a self-hosted option. Agents can coordinate responses to incoming conversations, making it relevant when customer-facing communication is the core support workflow.

Advantages: Shared conversation handling and self-hosting may fit teams that want to operate their support system on their own infrastructure.

Trade-offs: A conversation-centered workflow may not provide the structure of a dedicated ITSM system. Before adopting it for complex ticket operations, confirm queue, automation, permissions, SLA, and reporting controls. Include server operations, upgrades, backups, security, and availability in the cost comparison. Pricing and plan terms depend on the edition.

Best fit: Customer-support teams prioritizing shared conversation ownership and able to support the self-hosted service.

ManageEngine ServiceDesk Plus

ManageEngine ServiceDesk Plus is a commercial service desk and ITSM product with an on-premises edition. It is an option for organizations evaluating structured service management alongside ticket handling on infrastructure they manage.

Advantages: An on-premises deployment option and commercial ITSM positioning distinguish it from help desks focused on simpler queues.

Trade-offs: Licensing requires budget and edition review. Its broader scope may call for a closer workflow-fit assessment than a simple ticket inbox, and an on-premises installation adds responsibility for maintenance, upgrades, backups, security, and availability. Pricing depends on edition and deployment terms.

Best fit: Organizations seeking commercial ITSM with an on-premises edition and able to budget for licensing and local operations.

A practical selection process

1. Set the deployment boundary: Decide where the system must run and who owns maintenance, upgrades, backups, security, and availability. Check the terms for the relevant edition.
2. Map a representative request: Trace an employee or customer request from submission through assignment, status updates, and resolution. Include asset context or formal service-management steps if they matter.
3. Check handoffs: Confirm how channels, queues, permissions, SLAs, and customer-facing updates affect the next action.
4. Assess practical fit: Test the forms, ownership, statuses, and replies your team needs, while accounting for recurring operating and licensing costs.

For ONES Desk, the documented workflow lets a requester submit a form, track ticket progress, and communicate with internal team members; the service team can configure workflows, assign owners, manage visible statuses, and reply. See the ONES On-Premises version 7.33 documentation.

Which option fits your situation?

Consider ONES.com if you need self-hosted ticket management with portal intake, assigned ownership, visible statuses, and replies, and your organization can manage infrastructure and upgrades. GLPI is worth evaluating when asset inventory is central to internal IT work. osTicket may fit a small team centered on email, web forms, queues, and SLAs; RT is more aligned with email-driven queues and permissions. FreeScout and Chatwoot focus on shared customer conversations, while Zammad is a help-desk ticketing option and ManageEngine ServiceDesk Plus is a commercial ITSM choice with an on-premises edition.

These are workflow distinctions, not substitutes for checking edition terms and operational capacity. A representative request and an honest estimate of ongoing administration are useful checks before choosing.

FAQs

What should I compare first when choosing self-hosted ticket management software?

Start with deployment and edition terms, then trace a typical request through intake, ownership, status updates, and response. Account for who will maintain the server, upgrades, backups, security, and availability.

Which option suits internal IT teams that also manage assets?

GLPI is relevant to evaluate because its described fit combines ticketing with IT asset inventory and service-management workflows.

How does ONES Desk handle request follow-up?

For ONES On-Premises version 7.33, users can submit requests, track progress, and communicate with internal team members through the ticket portal. Teams can configure forms and workflows, assign owners, manage customer-visible statuses, and reply.

What are the ONES.com self-hosted trial terms?

The source states that ONES.com offers a free self-hosted trial for up to 20 users for 30 days, with the full ONES platform and no feature limits during the trial. It does not specify ongoing edition or feature limits.