GITNUXSOFTWARE ADVICE
Customer Experience In IndustryTop 10 Best Self Hosted Help Desk Software of 2026
Top 10 self hosted help desk software for IT teams, ranking tools like osTicket, GLPI, Znuny, and UVDesk with feature checks and tradeoffs.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
For most teams that want a self-hosted IT ticket system with email-first intake and configurable escalation, Znuny is the strongest pick, whereas UVDesk suits IT groups that need REST-integrated routing and consistent agent workflows, and Hesk is the simple low-cost entry if you’re a small team and just need manageable ticket intake.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Znuny
Customizable ticket lifecycle with configurable states and escalation steps for queue-driven workflows.
Built for fits when IT teams need email-first ticket intake and configurable escalation across departments..
UVDesk
Editor pickREST API access for managing tickets and automating workflow actions from external systems.
Built for fits when IT teams need REST-integrated ticket routing and consistent agent workflows from email intake..
GLPI
Editor pickGLPI’s tight coupling between asset management and the ticket lifecycle supports audits and troubleshooting context.
Built for fits when teams need ticketing plus asset tracking with extensible workflows and API access..
Comparison Table
Znuny
enterpriseOpen source IT service management platform forked from OTRS.
Customizable ticket lifecycle with configurable states and escalation steps for queue-driven workflows.
Znuny is a self hosted help desk built around a ticket lifecycle with queue routing, custom fields, and agent workspace controls for managing work per department. Ticket creation and updates can be driven by email ingestion paths, including email-to-ticket conversion and mailbox polling or piping, which reduces the need for custom connectors. Admin governance includes roles for agents and department boundaries plus workflow controls like escalation steps and canned responses. REST API access supports integrations that need ticket or record operations without screen scraping.
The tradeoff is that maintaining mail routing, identity bindings, and workflow configuration requires ongoing admin time, especially when multiple departments and inboxes are active. Znuny fits best when IT teams already run a LAMP style hosting environment and want email-first operations with deep configuration rather than a minimal SaaS-style workflow. A common usage pattern is centralized help desk intake for IT requests, with automated triage rules and escalation to specific queues based on content or metadata.
- +Rule-based triage and escalation flows tie inbox activity to queue outcomes
- +Department routing and custom ticket states support detailed lifecycle modeling
- +REST API enables ticket and configuration integrations without UI scripting
- +LDAP authentication supports centralized identity management for agents
- –Initial setup for mail parsing and routing demands careful admin configuration
- –Workflow tuning can become complex with many queues and custom fields
IT support teams
Automated triage to priority queues
Faster assignment and escalation
Managed service providers
Multi-client inbox aggregation
Lower operational overhead
Show 1 more scenario
Enterprise help desk admins
LDAP-based agent authentication
Consistent access control
Bindings and role-based access let agent onboarding align with directory governance.
Best for: Fits when IT teams need email-first ticket intake and configurable escalation across departments.
UVDesk
SMBOpen source SaaS-based helpdesk ticketing system built on Symfony.
REST API access for managing tickets and automating workflow actions from external systems.
UVDesk fits teams that want self-hosted operations with an automation-first ticket lifecycle and practical admin controls. The core setup supports ticket queues, department-based routing, and configurable escalation paths across a support ticket lifecycle. The product pairs inbox aggregation with email parsing so new requests can enter the same ticket workflow that agents manage.
A key tradeoff is that deep automation and system governance rely on configuration work across routing, responders, and workflow rules. UVDesk is a good fit when an IT or operations team needs centralized ticket handling and predictable agent triage from multiple mail channels, while integration work happens via the REST API.
- +REST API supports ticket and workflow integration with external systems
- +Department and queue routing keeps intake consistent across mail inboxes
- +Canned responses and custom ticket states help standardize agent actions
- +Knowledge base content reduces repeat ticket handling through guided replies
- –Advanced routing and escalation requires careful configuration and testing
- –Multi-channel inbox behavior depends on correct email parsing and relay setup
- –Agent workspace customization can add friction for large teams
- –Workflow edge cases need operational review during rollout
IT service desk teams
Route incidents from shared mailboxes
Faster assignment and escalation
Support operations teams
Standardize responses with knowledge content
Lower repeat contacts
Show 1 more scenario
Platform integration teams
Sync tickets with internal tools
Automated workflow coordination
REST API access enables bidirectional updates between UVDesk tickets and other systems.
Best for: Fits when IT teams need REST-integrated ticket routing and consistent agent workflows from email intake.
GLPI
enterpriseOpen source IT asset management and help desk platform.
GLPI’s tight coupling between asset management and the ticket lifecycle supports audits and troubleshooting context.
GLPI focuses on IT service operations where tickets must stay linked to computers, peripherals, software, and other tracked items. Ticket handling supports custom fields, canned responses, and approval or escalation patterns that reflect real operational steps. Authentication is designed to work with directory services through LDAP and Active Directory integration, and it can integrate with single sign-on in common enterprise setups. The plugin model adds missing channel adapters and reporting needs without replacing the core ticket engine.
A key tradeoff is that deeper customization usually requires PHP development or careful plugin configuration, which increases governance overhead for non developers. GLPI fits teams that need both a help desk queue and an asset source of truth, such as IT operations groups consolidating incident management and inventory tracking.
- +Asset inventory and ticket workflows share the same core data context
- +REST API supports programmatic ticket, user, and configuration automation
- +LDAP and Active Directory authentication fit enterprise identity models
- +Plugin system extends ticket forms, logic, and reporting without core rewrites
- –Workflow customization can require plugin work or developer support
- –Email ingestion setups add operational complexity around mail parsing and routing
- –UI configuration for complex departments and fields can feel dense
- –Operational scale depends on database tuning and PHP stack maintenance
IT operations teams
Incident handling with asset context
Faster resolution with traceability
Enterprise IT service desks
Directory-backed user access and routing
Reduced account management overhead
Show 2 more scenarios
Automation engineers
API-driven ticket and workflow automation
Consistent workflows at scale
The REST API supports scripted ticket creation, updates, and configuration tasks for integrations.
Support teams migrating help desks
Email-to-ticket and queue continuity
Continuity during migration
Mail driven ticket creation helps move inbound volume while teams map fields and states.
Best for: Fits when teams need ticketing plus asset tracking with extensible workflows and API access.
osTicket
SMBWidely deployed open source support ticketing system.
SLA escalation actions tied to ticket states and timing for queue-based service targets.
osTicket is a self hosted help desk system built around email-driven ticket creation and a configurable support workflow. It provides ticket queues, SLA timers, custom fields, canned responses, and department-based routing to manage case throughput.
The platform supports multi-inbox operation via email parsing and agent workspaces, with reporting focused on ticket status, backlog, and SLA compliance. osTicket also fits environments that need on-premise operations and controlled configuration rather than a hosted SaaS model.
- +Email-to-ticket conversion supports mailbox polling and routing into queues
- +SLA policy timers apply to ticket lifecycles with escalation workflows
- +Role-based access boundaries separate agents, managers, and department visibility
- +Canned responses reduce handling time for repeated request types
- –Workflow customization relies on configuration rather than a visual automation builder
- –Email parsing and routing need careful setup to avoid misfiled inbound tickets
Best for: Fits when IT teams need a self hosted ticket lifecycle with email intake, queue routing, and SLA timers.
FreeScout
SMBOpen source shared mailbox and help desk application.
Agent workspace supports ticket collaboration with reply actions that stay tied to the same conversation thread.
FreeScout routes inbound support conversations into a ticket list with email-first workflows. It can parse mail into tickets via built-in email handling and then move tickets through custom states, canned responses, and escalation steps.
Agents work inside a shared inbox view that links message threads to a single ticket lifecycle. The system stays self hosted on a LAMP-style stack with a MySQL or PostgreSQL backend and relies on IMAP polling and SMTP relay setup.
- +Email-to-ticket workflow centers operations on IMAP polling and SMTP relay delivery
- +Custom ticket states and canned responses support consistent ticket lifecycle handling
- +Multi-agent ticket assignment reduces handoff gaps inside shared inbox threads
- +Department-based routing supports different queues without separate instances
- –Email parsing depends on mail formatting and server configuration discipline
- –SLA policy engine coverage is limited compared with heavier ITSM tools
- –LDAP or Active Directory authentication needs careful setup for group mapping
- –No native extensibility surface for REST-style automation beyond typical UI actions
Best for: Fits when email-driven support needs a self hosted workflow with ticket states and routing.
Hesk
SMBPHP-based help desk software with a free self-hosted edition.
Email-to-ticket conversion with flexible IMAP polling and mail piping patterns for inbox aggregation.
Hesk is a self hosted help desk application that focuses on ticket handling via a web agent interface and email intake. Ticket workflows support categories, custom fields, and department-style separation, with SLA and escalation hooks tied to ticket state changes.
Administration centers on managing users, permissions, and email settings that feed ticket creation and notifications. Automation is primarily rule based through email handling and server-side job scheduling rather than a broad workflow designer.
- +Straightforward ticket lifecycle with custom fields and editable ticket metadata
- +Email-driven ticket intake works well for teams that run support through inboxes
- +Configurable canned responses for common answers and consistent agent replies
- +Admin tools cover queues, categories, and user access without extra modules
- –Workflow depth is limited compared with systems that offer state transitions per role
- –No public REST API for integrations beyond email and internal database access
- –Agent collision handling is minimal when multiple agents edit the same ticket
- –Scaling can require careful tuning of PHP and MySQL on busy inboxes
Best for: Fits when a small IT team needs simple, email-first ticket intake on self managed infrastructure.
Faveo Help Desk
SMBOpen source help desk software with SLA management and multi-channel support.
SLA policy engine that ties timer behavior to ticket events inside the support workflow.
Faveo Help Desk is a self-hosted help desk focused on workflow automation and support governance for multi-agent teams. It provides a ticket lifecycle with queue routing, SLA policy handling, and configurable ticket states.
Email support is handled through inbox polling and mail parsing so tickets can be created and updated from incoming messages. The admin surface includes role-based access and audit-friendly activity visibility to support structured operations.
- +Workflow rules cover ticket routing, escalation, and auto-responses
- +SLA policy engine supports timers tied to ticket events
- +Queue-based operations keep intake and reassignment predictable
- +RBAC and activity trails support agent governance in shared deployments
- –Initial setup depends on mail piping and server-side email parsing
- –Admin configuration takes time before complex routing is reliable
- –Advanced reporting needs careful data selection and filtering
- –Resource usage rises on busy queues and large knowledge sets
Best for: Fits when IT and support teams need queue routing plus SLA-driven workflows on-premises.
Cerb
enterpriseWorkflow automation and collaboration platform with help desk capabilities.
CERB automation workflows let administrators define multi-step escalation and queue transitions using rule triggers.
Cerb is a self-hosted help desk built around ticketing workflows expressed in configurable automation and actionable queues. Its core strength is extensibility through REST API access, plus an agent workspace that supports routing, SLA handling, and multi-step ticket lifecycle actions.
Email intake can be integrated with self-hosted mail parsing so inbox traffic becomes ticket activity without relying on a hosted mailbox service. For teams that need governance beyond a basic queue, Cerb supports authentication integration such as LDAP or Active Directory and role-based access control patterns for departments and agents.
- +Automation rules drive ticket queues and escalation paths without custom code
- +REST API access supports workflow integration with external systems
- +Agent workspace reduces context switching across ticket lifecycle actions
- +Authentication options support LDAP or Active Directory for centralized access
- –Workflow configuration and tuning take more admin time than simpler help desks
- –Some multi-channel aggregation paths require careful mail piping and relay setup
- –Advanced reporting needs active configuration to match internal SLA metrics
- –Migration tooling is not as streamlined as dedicated migration-focused products
Best for: Fits when teams need self-hosted ticket automation and API-driven integrations for IT support workflows.
Chatwoot
SMBOpen source customer engagement platform with ticketing and multi-channel inbox.
SLA policy engine rules apply timing and escalation logic across queues and departments, not just per agent.
Chatwoot turns inbound messages into ticket threads inside agent workspaces, and it groups conversations by inbox configuration. It supports ticket lifecycle management with custom ticket states so teams can reflect triage, investigation, and approval steps without external tooling.
Admin configuration covers queue routing behavior and SLA policy engine rules, so escalation can follow defined timing windows. It also supports department-based routing patterns so the same inbox can feed different workflows based on message attributes.
Chatwoot exposes REST API access for ticket creation and updates, which supports automation and integration with internal systems. Email-to-ticket conversion and self-hosted mail parsing cover inbound workflows, while outbound behavior depends on SMTP relay configuration.
Operationally, self-hosted deployments require attention to server resource requirements and background job throughput for polling, mail processing, and automation tasks. Teams should plan backup and restore procedures for the MySQL or PostgreSQL backend to protect ticket history and message logs.
- +REST API access supports ticket and message automation for integrations
- +Ticket queue routing and SLA policies support department-level escalation control
- +Multi-channel inbox aggregation keeps email and chat threads in one workflow
- +Custom ticket states fit staged approval and investigation workflows
- –Self-hosted mail parsing needs careful setup to avoid misrouted conversations
- –RBAC and governance controls require deliberate configuration for larger teams
- –Migration from other help desks can require mapping agent and workflow conventions
- –High inbox volume needs monitoring of background jobs and worker capacity
Best for: Fits when IT teams need a self-hosted help desk with API-driven automation and SLA-based escalation.
Helpy
SMBOpen source help desk software focused on knowledge base and email ticketing.
REST API access for ticket and workspace automation without requiring direct database edits.
Helpy is a self-hosted help desk that centers ticket handling, email-based workflows, and team collaboration in one install. Core capabilities include inbox ticket creation, ticket lifecycle states, internal notes, and canned replies for repeatable support.
It also provides API access for integrations and automation via external systems. Helpy targets IT teams that want operational control over deployment and mail processing while still standardizing support workflows.
- +Self-hosted deployment keeps ticket data under direct server control
- +REST API enables external automation for ticket status and agent actions
- +Canned responses reduce handling time for repeated requests
- +Configurable routing and assignment supports department-level intake
- –Email-to-ticket setup can become fragile when mail piping and relays differ
- –Workflow customization relies on limited state and field configurability
- –Advanced governance needs extra discipline for agent permissions and activity review
- –Scales best when ticket volume and inbox concurrency stay moderate
Best for: Fits when an IT team wants self-hosted ticketing with an API for automation and email intake.
Conclusion
After evaluating 10 customer experience in industry, Znuny stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right self hosted help desk software
Self hosted help desk software runs on an organization’s own infrastructure so ticket intake, queue routing, and support workflows stay under direct server control. This guide covers Znuny, osTicket, and eight additional self-host options chosen for IT use cases where inbox-driven support must map into controlled ticket lifecycles.
Across the reviewed tools, differences show up in ticket state modeling, escalation mechanics, and how automation is exposed through REST API access or configuration-first workflows. Znuny and osTicket anchor the IT-oriented shortlist with queue-driven escalation and SLA timing, while UVDesk and Cerb emphasize REST-driven ticket and workflow integration.
Self hosted help desk software that unifies inbox intake, ticket routing, and API-driven workflow automation
Self hosted help desk software centralizes email-to-ticket conversion, ticket lifecycle states, and queue routing so IT teams can turn incoming messages into tracked work. Tools like osTicket route email into ticket queues and apply SLA escalation actions tied to ticket states and timing, so response and resolution targets can be enforced inside the workflow.
Other options go deeper on extensibility and integration. Znuny models a configurable ticket lifecycle with custom ticket states and escalation steps for queue-driven workflows, while UVDesk provides REST API access for managing tickets and triggering workflow actions from external systems.
IT help desk requirements mapped to configuration, routing, and automation
Self hosted help desk software only becomes operational when ticket intake lands in the right queue and the ticket lifecycle enforces escalation timing consistently. For IT teams, that means email-to-ticket conversion must pair with queue-driven state changes and SLA escalation actions, not just basic ticket viewing.
The review set shows two distinct implementation styles. Znuny and osTicket focus on ticket lifecycle modeling with queue and timing controls, while UVDesk, Cerb, and Helpy emphasize REST API access so external systems can drive ticket status and workflow actions.
Queue-driven ticket lifecycle and escalation actions
Znuny supports configurable ticket lifecycle states and escalation steps that follow queue outcomes, which fits department workflows with controlled state transitions. osTicket ties SLA escalation actions to ticket states and timing, which suits queue-based service targets inside a classic help desk flow.
REST API access for ticket and workflow automation
UVDesk exposes REST API access for ticket management and workflow actions so external systems can route and update tickets after email intake. Cerb and Helpy also provide REST API access, with Cerb using automation rules for multi-step escalation and queue transitions.
Asset-context workflows for IT troubleshooting
GLPI connects asset inventory and ticket workflows in the same core data context, which reduces context switching during troubleshooting and audits. This tight coupling matters when ticket history must be cross-referenced with the asset impacted by the request.
Email intake pipeline behavior across parsing, polling, and relays
osTicket uses email-to-ticket conversion with mailbox polling and queue routing plus SLA timers that trigger escalation workflow actions. Hesk uses flexible IMAP polling and mail piping patterns for inbox aggregation, while Faveo Help Desk centers operations on IMAP polling and SMTP relay delivery for email-driven ticket collaboration.
Choose the workflow engine style that matches how IT teams escalate work
Selection starts with whether escalation logic must be configured around ticket states and timers inside the help desk UI, or whether escalation logic must be orchestrated from external IT systems through an API. Znuny and osTicket model the lifecycle and escalation inside ticket states, while UVDesk, Cerb, Chatwoot, and Helpy expose REST API access to drive routing and status changes from outside.
Next, the decision should match the operational reality of email intake. Several tools depend on correct mail parsing, relay configuration, and mailbox polling behavior, and misconfiguration shows up as misfiled inbound tickets or inconsistent multi-channel behavior.
Map escalation ownership to ticket states versus external automation
Choose Znuny when ticket lifecycle requires configurable states and escalation steps that follow queue outcomes across departments. Choose UVDesk or Helpy when workflow actions must be triggered from external systems using REST API access for ticket and workspace automation.
Test SLA timing logic against the service targets used by IT
Choose osTicket when SLA escalation actions must attach to ticket states and timing for queue-based service targets. Choose Faveo Help Desk or Chatwoot when SLA coverage can be lighter or when SLA policy rules must apply across queues and departments rather than only per agent.
Validate email intake routing with the same parsing and relay path used in production
Choose osTicket when the email-to-ticket workflow already aligns with mailbox polling, queue routing, and SLA timers that act on ticket lifecycles. Choose Hesk when inbox aggregation must follow flexible IMAP polling and mail piping patterns for a smaller team managing email-first intake.
Pick the data context model used during troubleshooting and audits
Choose GLPI when asset inventory must share core context with ticket workflows so troubleshooting can reference the impacted asset. Choose other tools when ticket lifecycle modeling and automation depth are the primary needs, since GLPI’s advantage concentrates on asset-context alignment.
Choose an automation configuration approach that matches admin capacity
Choose Cerb when multi-step escalation and queue transitions must be defined using automation workflows driven by rule triggers. Choose Znuny or osTicket when escalation tuning must stay configuration-first with well-defined ticket state and queue behavior, while accepting that workflow tuning can get complex with many queues and custom fields.
Who should run self hosted help desk software on internal infrastructure
Self hosted help desk software fits IT teams that route inbound messages into controlled ticket workflows and need escalation timing that stays governed by the organization. The tool set here supports that model through queue routing, ticket states, and API-driven automation for external systems.
IT teams running email-first intake and department routing
Znuny and osTicket support queue-driven escalation and ticket lifecycle states tied to inbox conversion, so inbound messages can land in the right department workflow with timing controls.
IT platforms that must orchestrate ticket status from external systems
UVDesk, Cerb, and Chatwoot provide REST API access for managing tickets and workflow actions, which supports integrations that update tickets without manual agent steps.
Teams that require asset-aware support workflows and audit context
GLPI’s tight coupling between asset management and the ticket lifecycle keeps troubleshooting context in the same core data context, which helps when audits require asset and ticket linkage.
Small support teams relying on mail piping and inbox aggregation
Hesk supports flexible IMAP polling and mail piping patterns that work well for simple email-first intake, while Faveo Help Desk centers operations on IMAP polling and SMTP relay delivery.
Organizations with governance needs that include agent roles and admin control
Chatwoot requires deliberate RBAC and governance configuration for larger teams, which makes it a better fit when admin capacity exists to set and test permissions.
Common self hosted help desk setup and operations pitfalls
Missteps usually show up in two places: the email intake pipeline and the workflow tuning path. Email parsing and routing problems lead to misfiled conversations, while overly ambitious queue and field customization can make escalation rules hard to reason about and hard to maintain.
Assuming email parsing and relay setup will not affect queue routing outcomes
osTicket and UVDesk rely on mailbox polling and correct email parsing to route into queues, so inbox misrouting shows up quickly when parsing rules and relay paths differ from production. Run a controlled test with the same mail piping or relay configuration before scaling intake.
Overbuilding ticket lifecycle complexity without a governance plan for state and escalation changes
Znuny supports configurable ticket lifecycle states and escalation steps, but workflow tuning can become complex with many queues and custom fields. Start with a small set of states and escalate steps, then add departments and custom fields only after routing behavior matches expectations.
Using a configuration-only workflow approach when external orchestration is the real requirement
Tools that emphasize REST API access such as UVDesk, Cerb, and Helpy are better aligned when external systems must update tickets and agent actions programmatically. If integrations are already designed around REST calls, choose an option that exposes ticket and workflow automation through that API surface.
Selecting an ITSM-style asset workflow without confirming the expected operational model
GLPI’s advantage comes from asset inventory and ticket workflows sharing the same core data context, but workflow customization can require plugin work or developer support. Confirm whether asset-first workflows and potential plugin additions align with the team’s operational capacity.
How We Selected and Ranked These Tools
We evaluated self hosted help desk tools by scoring feature coverage at 40% weight, then scoring ease of setup and ongoing administration at 30% weight, and scoring value at the remaining 30% weight. Znuny separated from the rest through configurable ticket lifecycle states and escalation steps that tie directly to queue-driven workflows, which matched IT-oriented escalation requirements more consistently than simpler ticket state models.
osTicket ranked highly for SLA escalation actions tied to ticket states and timing with email-to-ticket conversion into queues, which made SLA enforcement concrete inside the workflow. UVDesk and Cerb scored for extensibility because REST API access connected ticket management and workflow actions to external systems, which reduced the need for manual agent intervention in automated routing.
Frequently Asked Questions About self hosted help desk software
How does email-to-ticket ingestion differ between osTicket and Znuny?
When does an agent workspace matter for operations, and how do Znuny and Helpy implement it?
Which tool provides REST API access that is practical for automation of ticket workflows?
What breaks if an organization expects built-in asset management but chooses a ticket-only help desk?
How do Faveo Help Desk and Chatwoot differ in SLA behavior when escalations cross queues or departments?
When is IMAP polling with SMTP relay setup a key operational constraint?
Which authentication pattern supports enterprise identity, and how do Cerb and GLPI handle it?
How does extensibility via plugins or automation compare between GLPI and Hesk?
What tradeoff appears when a team wants ticket lifecycle governance versus minimal configuration overhead?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
- Customer Experience In IndustryTop 10 Best Self Hosted Helpdesk Software of 2026
- Technology Digital MediaTop 10 Best Hosted Help Desk Software of 2026
- Customer Experience In IndustryTop 10 Best Browser Based Help Desk Software of 2026
- Customer Experience In IndustryTop 10 Best Help Desk Services of 2026
- Technology Digital MediaTop 10 Best Hosted Web Services of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Customer Experience In Industry alternatives
See side-by-side comparisons of customer experience in industry tools and pick the right one for your stack.
Compare customer experience in industry tools→