FreeITSM
Run an entire IT service desk without paying per seat: FreeITSM turns email, chat, and portal requests into tickets and keeps assets, knowledge, changes, and projects in the same place. The inbox looks like Outlook, with folders by department or team, SLAs, canned replies, internal notes, time entries, and bulk actions. Messages arrive from Microsoft 365, Gmail, IMAP, WhatsApp, Telegram, Slack, Microsoft Teams, Mattermost, and an embeddable web chat widget. A Watchtower dashboard shows what needs attention across every module at a glance. Asset records collect hardware, software, storage, contracts, and lease dates, and a CMDB maps servers, databases, applications, and services. Change management tracks approvals and scheduled work windows, and a shared calendar covers on-call rotas and maintenance. Tasks run on a Kanban board with list, calendar, and timeline views, and projects add health rings and plans. Staff publish knowledge articles in folders with tags, and end users get a portal with a request catalogue. Optional AI features, using your own keys or a local model server, clean up replies and answer questions from the knowledge base. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
iTop
Keep every ticket tied to the servers, applications, and contracts it affects with iTop, an IT service management platform that joins a configuration management database (CMDB) to a helpdesk. Agents work user requests, incidents, problems, known errors, and changes through ITIL-style life cycles, and SLA targets for time to own and time to resolve move a ticket to an escalated status when a deadline passes. The CMDB models infrastructure, virtualization, end-user devices, software, and business applications, and its impact analysis graph shows what a failing server would take down. A service catalog of services and subcategories, backed by customer and provider contracts, feeds a user portal where employees and customers submit requests from a mosaic, tree, or list, follow progress, add comments and attachments, and reopen resolved tickets. Administrators bulk-load inventory from CSV, run consistency audits to catch data-quality problems, synchronize records from external sources, and connect other tools through REST web services. Sign-in works with local accounts, LDAP, or CAS, with optional two-factor authentication through authenticator apps, email codes, or recovery codes, and the console offers dark, high-contrast, and color-blind-friendly themes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
osTicket
With nearly 3,900 GitHub stars, over 1,800 forks, and continuous development since 2013 culminating in the v1.18.4 release in June 2026, osTicket remains one of the most deployed open-source help desk systems worldwide, trusted by organizations from small businesses to universities and government agencies. The PHP backend on Apache or IIS with MySQL stores every ticket, response, and attachment while the web interface provides separate agent and customer portal views with role-based access control across departments, teams, and individual agents. Customers submit tickets through web forms, email piping, or phone-entry by agents, and configurable ticket filters automatically route incoming requests to the correct department, assign agents or teams, set priority levels, apply SLA plans, and trigger canned responses based on matching criteria including custom field values. Agent collision avoidance locks tickets during response composition to prevent duplicate replies, while SLA plans with business hour schedules track due dates and escalate overdue tickets automatically. Custom forms and fields let organizations capture structured data specific to each help topic — from IT asset tags to billing account numbers — with configurable required and internal-only visibility. The advanced search system with saved queries and CSV export enables reporting across all ticket metadata and custom fields. The customer portal provides ticket tracking, profile management, and knowledge base access. OAuth2 plugin support enables modern email authentication with Microsoft 365 and Google. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0 licensed.
Windshift
Windshift packs boards, sprints, roadmaps, test runs, time tracking, and a customer portal into one open-source tracker that replaces Jira on a server you control. Epics, stories, and sub-tasks form a hierarchy you can view as a board, list, tree, or map, and backlog items drag into dated sprints. The roadmap stretches across weeks, months, or quarters, and milestone pages show completion percentage with a status breakdown. Each workspace defines its own item types, custom fields, screens, statuses, priorities, workflows with conditions and approvals, and permissions, while JQL-style queries save as shared views. Event-driven rules update fields, notify people, and create work. Customers file requests through a public portal, and your team works them through queues with SLAs and approvals. Reusable test cases roll into test runs with success rates, and timers log billable and internal hours against projects and customers. GitHub, GitLab, Gitea, and Forgejo connections put branches and pull requests on the work item, and the importer brings over Jira projects, comments, attachments, and worklogs. A knowledge base and an asset register keep documentation and inventory next to the work. The interface speaks nine languages, including right-to-left Arabic, and sign-in supports OIDC single sign-on and passkeys. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Request Tracker
Email-driven ticketing for IT, support, and operations teams: Request Tracker turns every message sent to support@, helpdesk@, or security@ into a tracked ticket with an owner, a priority, a due date, and a complete audit trail. Staff reply to customers and comment privately to colleagues from the web interface or straight from their inbox, while requestors follow their own tickets in a self-service portal. Lifecycles built in a visual editor define custom statuses, transitions, and rights per queue, and scrips fire notifications or automated actions whenever a ticket changes. Service level agreements honor business hours, escalations trigger as deadlines approach, and scheduled tickets recreate recurring chores such as monthly patch windows. A transaction query builder, saved searches, charts, and drag-and-drop dashboards turn ticket history into reports that export to CSV or arrive by email on a schedule. Asset catalogs track laptops, licenses, and servers beside the tickets that mention them, and an Articles knowledge base feeds canned answers into replies. Time worked is logged per ticket with a My Week timesheet, approvals route sensitive requests to the right people, and PGP or S/MIME protects email in both directions. A REST2 API, a command-line client, and more than 400 extensions connect RT to the rest of your tooling. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0 licensed.
GLPI
GLPI combines helpdesk ticketing, hardware inventory, license compliance, CMDB, and project management in a single PHP application with over 6,200 GitHub stars and 500,000+ Docker pulls, offering a unified ITSM platform that replaces ServiceNow, Freshservice, and ManageEngine without per-agent pricing. The ITIL-aligned service desk handles incidents, problems, changes, and service requests with configurable SLA management, approval workflows, satisfaction surveys, and business rules that automate ticket routing, escalation, and categorization. Native dynamic inventory through the GLPI Agent discovers Windows, Linux, and macOS endpoints with deep hardware profiling, while network discovery scans switches, printers, and infrastructure devices automatically. Software and license management tracks per-user and per-core license allocations with compliance reporting, expiration alerts, and financial cost tracking across the asset lifecycle from purchase through depreciation to disposal. Data center infrastructure management provides rack visualization with U-level positioning, PDU tracking, and connection mapping. The integrated forms editor builds custom request portals for end-users, while the self-service portal lets users submit tickets, browse the service catalog, and reserve assets. Webhooks trigger external HTTP calls on events, and the High-Level REST API v2 exposes every resource for automation. A plugin marketplace offers 90+ extensions for monitoring integration, advanced reporting, and authentication. Deploy via Docker with the glpi/glpi image alongside MySQL. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPLv3 licensed.
Django Helpdesk
Django Helpdesk is a complete support ticketing system that gives a small business one shared place to receive, assign, and resolve customer requests. Customers write to a support address and each incoming email becomes a ticket in the right queue, with replies threading back into the same conversation. Queues separate products, departments, or clients, and each queue can poll its own mailbox and carry its own settings. The staff dashboard surfaces unassigned tickets the moment they land, and agents claim work, reassign it, or hand it to a teammate. Every ticket holds its follow-up history, attachments, priority, due date, and custom fields your team adds for the details generic forms miss. Duplicate reports merge into a single ticket, and saved searches keep recurring questions one click away. Customers help themselves first through the built-in knowledgebase, then submit and track their own requests in a portal that hides internal notes. A REST API creates and updates tickets from other systems, and webhooks push ticket events into chat tools, CRMs, or billing scripts. An embeddable iframe form drops ticket submission into any existing website, and spam filtering keeps junk out of the queue. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. BSD-3-Clause licensed.
Peppermint
A deliberately simple ticketing system standing in for both Zendesk and Jira: Peppermint handles internal staff requests and external customer support alike. The stack is modern full-stack TypeScript: Next.js and React over Prisma and PostgreSQL, which makes it light to run and approachable for developers extending it. Ticket creation is straightforward - a markdown editor with file uploads, assignment, status tracking, and a logical workflow that new agents grasp without a manual. Mailbox integration converts email into tickets automatically: configure SMTP/IMAP per mailbox and incoming messages become trackable tickets. Each client accumulates an interaction history, giving agents context on every past request before replying. Two touches distinguish it from bare-bones ticketing: a built-in markdown notebook with todo lists for internal documentation and knowledge sharing, and OIDC authentication so agents sign in through your existing identity provider - Keycloak, Okta, Authentik, or Azure AD. Configurable webhooks and email notifications push ticket events to third-party services. The UI is responsive from mobile to 4K, and everything works fully offline in air-gapped environments. Docker-native and scalable via Kubernetes, with an active community of 3,000+ GitHub stargazers.
CompDesk
CompDesk is a self-hosted help desk that gives small organizations department-based ticket queues, role-based access control, and a public Help Center without a per-agent subscription. Tickets land in department inboxes where agents work searchable queues with templates, custom fields, tags, and internal notes that customers never see. SLA policies set response and resolution targets per queue, and escalation rules push overdue tickets upward before they go stale. Requesters follow their own tickets, join public comment threads, and browse Help Center articles in English or French; agents keep the full immutable timeline behind each case. Private attachments stay out of the public file space, pass signature validation and quota checks, and can be scanned by ClamAV before anyone downloads them. Sign-in works with local accounts, Microsoft Entra ID, or any OpenID Connect provider, and four roles (User, Agent, department Admin, Super Admin) decide exactly who sees which tickets. Email notifications flow through SMTP or Microsoft 365, signed webhooks announce ticket events to other systems, and department-scoped API clients give external tools a way to open and update tickets. Runtime branding restyles the portal with your organization name, logo, and colors, and a guided setup wizard creates the first Super Admin and locks itself away when finished. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
OTOBO
Email, phone, and portal requests become tickets with owners, queues, and deadlines in OTOBO, the open-source service management platform for IT, HR, and facility teams. Agents start on a dashboard of reminder, escalated, and new tickets, with a seven-day created-versus-closed chart and a list of upcoming escalations. Opening a ticket shows its service, service level agreement, owner, customer details, and a full article history where agents reply, forward, split, pin, or add notes. Queues, roles, and access control lists decide who sees what, while PostMaster filters sort incoming mail by sender, subject, or keywords. Dynamic fields attach custom data to tickets and can point at customers, services, and FAQ articles. Process management models multi-step workflows such as approvals with approve and reject buttons. Power search finds tickets and configuration items as you type, and a Similar Tickets widget surfaces related cases. Customers open and follow their requests in a white-label self-service portal. Optional add-on packages bring a CMDB whose configuration items link to tickets, an FAQ knowledge base, and customer satisfaction surveys. Team calendars handle recurring appointments, built-in statistics and reports measure service performance, and sign-on works through OpenID Connect, LDAP, or Active Directory. REST and SOAP web services connect OTOBO to other systems. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.
Znuny
Znuny turns every customer request into a ticket with an owner, a priority, a deadline, and a complete history, no matter whether it arrived by email, phone, web portal, API, or a monitoring alert. Agents work from a dashboard that lists open and new tickets, escalations, running processes, a seven-day created-versus-closed chart, upcoming events, and logged-in colleagues. Queues route tickets to the right team, and automation handles classification, escalation, notifications, and state changes, from simple email filters up to multi-step business processes. Service level agreements are tracked against every ticket, with alerts before deadlines pass and overdue items highlighted. Customers help themselves through a self-service portal and a searchable FAQ knowledge base, while agents opening a ticket immediately see who the customer is, which company they belong to, the services they are entitled to, and their full support history. Configuration items in the CMDB link assets and services to the tickets they affect, statistics and reports turn ticket data into decisions, and calendar appointments can create tickets on schedule. Administrators shape the system with over 2,000 configuration options, dynamic fields, and granular permissions. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.