Open-source support ticketing, honestly reviewed. No marketing fluff, just what you get when you self-host the tool that 5 million users run their customer support on.

TL;DR

What it is: Open-source (GPL-2.0) support ticket system that converts customer inquiries from email, phone, and web forms into manageable tickets in a single interface [3].
Who it’s for: Small to mid-size businesses — IT administrators, help desk managers, and support coordinators at 5–200 person companies in education, nonprofits, government, and IT — who need solid ticketing without Zendesk pricing [1].
Cost savings: Zendesk Suite starts at $55/agent/month. osTicket self-hosted costs $0 in licensing fees on a $5–10/mo VPS. Even the hosted SupportSystem option runs at reported prices of $9–12/user/month [1][2].
Key strength: Genuinely free, genuinely full-featured for core ticketing. SLA management, automated routing, custom forms, and multi-department workflows that would cost hundreds per month on enterprise alternatives [3].
Key weakness: The UI is dated. The codebase is PHP and hasn’t been modernized significantly. There’s no native REST API to speak of, no built-in live chat, and no AI features. If you need modern UX or integrations, look elsewhere [1][2].

What is osTicket

osTicket is a web-based support ticket system built on PHP and MySQL. It takes customer inquiries arriving via email, web forms, or phone calls and turns them into tickets — assigned to agents, tracked through resolution, and organized by department, priority, and SLA. That’s the pitch, unchanged since its initial release over a decade ago.

The GitHub repository describes it plainly: “a widely-used open source support ticket system” that “seamlessly integrates inquiries created via email, phone and web-based forms into a simple easy-to-use multi-user web interface” [README]. The homepage claims 5 million users and 15,000+ businesses worldwide, which is plausible given how long the project has been around and how few competitors existed in the early years of self-hosted helpdesk software [homepage].

The company behind it runs a commercial hosted product called SupportSystem (supportsystem.com), which is essentially osTicket managed for you. The self-hosted version is GPL-2.0, meaning you can download, deploy, and modify it freely — but unlike MIT, you can’t embed it in closed-source commercial products without distributing your source [README].

As of January 2026, the latest stable version is v1.18.3, with active security patching still occurring [4][5]. The GitHub repository sits at 3,711 stars — modest compared to newer tools but not a dead project.

Why people choose it

The primary reason is the same today as it was fifteen years ago: it’s free, it works, and it covers the basics without requiring a subscription to a vendor whose pricing will triple in three years.

Versus Zendesk. This is the comparison that matters most for the target audience. Zendesk is polished, widely integrated, and comprehensively documented — but a 10-agent team on Zendesk Suite Professional pays north of $550/month. osTicket handles the same core workflows (ticket routing, SLAs, canned responses, customer portal) for the cost of a VPS. SaaSworthy rates osTicket at 96/100 in its scoring methodology and ranks it in the top 10 for most popular help desk software, which reflects how often budget-constrained teams reach for it as the Zendesk alternative [2].

Versus Freshdesk. Freshdesk has a free tier that’s competitive for very small teams. But osTicket wins when you need more agents, more custom fields, or more control over your data without hitting paywalls. SpotSaaS specifically calls it “the right choice for small business who require a feature rich system with enterprise level features” [1].

On the open-source premise. The TicketSellingSites review puts it directly: osTicket is flexible and scalable because it’s open source — you can modify the code, integrate with other systems, and it won’t be acquired and repriced by a private equity firm [3]. For government agencies, nonprofits, and schools that need to justify every line item, “free forever” is a real budget argument.

The catch that reviews don’t emphasize enough. osTicket’s competitive moat is almost entirely price and longevity, not feature velocity. The tool hasn’t meaningfully modernized its UI or added category-level new features in years. If you’re evaluating it against something like Freshdesk’s free tier or against newer self-hosted options, you’re trading polish and modern workflows for zero licensing cost and full data control.

Features

Based on the README, website, and third-party reviews:

Core ticketing:

Ticket creation via email, web forms, and manual entry [README][3]
Automated ticket routing to departments and agents based on configurable rules [1][3]
Ticket filtering and prioritization [homepage][3]
Internal notes, agent collision detection (ticket locking to prevent dual response) [2]
Canned responses and macros for templated replies [1]
Configurable help topics and custom fields [homepage][3]
File attachments and document storage [1]

SLA and escalation:

Service Level Agreement management with time thresholds and business hours [1][3]
Automatic alerts and escalation on SLA breach [1]
Priority-based routing and urgency tiers [3]

Customer portal:

Self-service portal where customers submit and track tickets [homepage][2][3]
Automated email responses on ticket submission [2]
Customer-facing knowledge base [1]

Reporting:

Dashboard with key metrics — ticket volumes, response times, agent performance [2][3]
Customizable reports for helpdesk operations [2]

Multi-department and multi-agent:

Unlimited departments, teams, and agents in the self-hosted version [3]
Role-based access with different permission levels [2]

Internationalization:

Fully translatable interface via Crowdin integration, with official language packs available [README]

What’s missing:

No native live chat [1]
No built-in REST API for external integrations [merged profile]
No AI-assisted responses or ticket classification
No native mobile app — browser-based only [2]
Community forums are not native; require third-party integration [1]

The feature set is solid for its category as of roughly 2018. It covers everything a small support team needs to not drown in email. What it doesn’t do is anything you’d describe as modern.

Pricing: SaaS vs self-hosted math

osTicket self-hosted (Community Edition):

Software license: $0 (GPL-2.0) [README]
Infrastructure: $5–15/month on a basic VPS

SupportSystem (their managed cloud):

Third-party aggregators report pricing starting around $9–12/user/month, with a free forever tier available [1][2]
The official website doesn’t publish transparent pricing — it pushes visitors toward a 30-day trial [homepage]

Zendesk for comparison:

Suite Team: $55/agent/month
Suite Growth: $89/agent/month
Suite Professional: $115/agent/month
A 5-agent team on Suite Team: $275/month, $3,300/year

Freshdesk for comparison:

Free tier: unlimited agents, basic features
Growth: $15/agent/month
Pro: $49/agent/month

Concrete math for a small support team:

A 5-agent support team on Zendesk Suite Team pays $275/month. On osTicket self-hosted, that same team pays approximately $10/month for a VPS plus zero in licensing. Over a year: Zendesk ≈ $3,300. osTicket self-hosted ≈ $120. That’s roughly $3,180 saved annually, which is the entire annual salary of a part-time support contractor in many markets.

Caveat: that math assumes someone on your team can deploy a PHP application and maintain a Linux server. If you’re paying a contractor to do it, add a one-time setup fee. If you’re running on SupportSystem instead of self-hosting, the savings are smaller but the operational overhead disappears.

Deployment reality check

osTicket runs on a traditional LAMP stack — Linux, Apache (or IIS), MySQL, PHP. The requirements are straightforward [README]:

HTTP server: Apache or Microsoft IIS
PHP 8.2–8.4 (8.4 recommended as of v1.18.3)
MySQL 5.5 or newer
PHP extensions: mysqli, plus ctype, gd, imap, intl, mbstring, and several others recommended

The install path is a git clone followed by a PHP deploy command:

git clone https://github.com/osTicket/osTicket
cd osTicket
php manage.php deploy --setup /var/www/htdocs/osticket/

Then point your web server at the deployment folder and run the web-based installer [README]. Upgrades follow the same pattern — git pull followed by php manage.php deploy.

What can go sideways:

Email authentication is now mandatory complexity. Microsoft and Google have deprecated basic auth (username/password) for SMTP. osTicket v1.17+ requires installing the OAuth2 Plugin separately to handle modern email authentication with Gmail and Outlook [4][5]. This is a real setup step that isn’t obvious from the install guide and has caught users mid-upgrade.
PHP version management. Each major osTicket release has specific PHP version requirements (v1.17+ requires PHP 8.2–8.4). If your VPS is running PHP 7.x or 8.0, you’ll need to upgrade PHP before you can upgrade osTicket [4][5].
No Docker-first experience. Unlike newer self-hosted tools that ship with a docker-compose.yml and a one-command install, osTicket’s primary deployment path is still the traditional Apache/Nginx + PHP-FPM stack. Docker deployments exist via community images but aren’t officially maintained [README].
The “pro” plugin ecosystem is thin. SpotSaaS notes that osTicket supports plugins for extensibility, but the plugin marketplace is community-maintained and inconsistent in quality [1].

Realistic time estimate for a technical user who has deployed PHP apps before: 1–2 hours to a working instance, plus another hour configuring email properly with OAuth2. For a non-technical founder following a tutorial: budget a full day, including SMTP debugging. If you’ve never configured a web server, seriously consider SupportSystem or hiring someone to deploy it once.

Pros and Cons

Pros

Actually free. GPL-2.0, self-hosted, zero licensing cost. No per-agent pricing, no per-ticket caps, no paywalled features after year one [README][3].
Core ticketing is genuinely solid. SLA management, automated routing, multi-department support, and custom forms cover the real workflow needs of most small support teams [1][3].
5+ million users. The project has been in production long enough that most edge cases have been hit and documented. The forum and community are real resources [homepage][3].
Actively maintained security patches. v1.18.3 shipped in January 2026 with security fixes — the project isn’t abandoned [4][5].
Fully translatable. Crowdin integration with official language packs for dozens of languages, which matters for non-English support teams [README].
Unlimited agents and tickets on self-hosted. No artificial caps [3].
Customizable at the source level. GPL means you can patch it, extend it, and integrate it however your team needs [3].

Cons

The UI is dated. Every modern alternative — Freshdesk, Zoho Desk, Linear, even Zammad — looks more contemporary. osTicket’s interface hasn’t been redesigned in years and it shows.
No REST API. Programmatic access to tickets, agents, and data is limited. This matters if you want to build dashboards, feed data to a CRM, or automate workflows outside the system [merged profile][1].
No AI, no modern integrations. No GPT-powered ticket classification, no Slack integration out of the box, no Zapier connector in the community edition. You’re on your own for anything beyond email and web forms.
OAuth2 is a required extra step for email auth, not bundled. If you’re not technical, this is a genuine deployment blocker [4][5].
No native live chat. If you want real-time customer support chat, you need a separate tool [1].
Docker experience is not first-class. Community-maintained Docker images exist, but the official deployment path is the traditional LAMP stack, which is more friction in 2026 [README].
Commercial cloud pricing is opaque. The SupportSystem site pushes you into a trial rather than showing a clear pricing page [homepage]. Aggregators report $9–12/user/month but these may be outdated [1][2].

Who should use this / who shouldn’t

Use osTicket if:

You’re running a support operation at a school, nonprofit, local government, or small IT firm where licensing costs are genuinely a constraint.
You have a technical person who can handle a PHP deployment and won’t need hand-holding on server maintenance.
Your support workflow is email-first — customers email in, agents respond, tickets get closed. No fancy AI needed.
You want data sovereignty — tickets stay on your server, not inside a vendor’s cloud.
You have 5–50 agents and don’t need SSO, SCIM, or enterprise audit logs.

Skip it (consider Zammad or Peppermint) if:

You want a self-hosted option with a modern UI and a real REST API. Zammad is GPL-licensed, actively developed, and visually contemporary.
You need live chat alongside ticketing — Zammad and Chatwoot handle this natively.

Skip it (consider Freshdesk free tier) if:

You have fewer than 10 agents and want zero infrastructure overhead. Freshdesk’s free tier is legitimate and costs nothing.
Your team has no one comfortable with server management.

Skip it (stay on Zendesk) if:

You need deep CRM integrations, Salesforce sync, or a curated app marketplace.
Your compliance team requires a vendor with SOC 2 certification and formal SLAs on the support tool itself.

Skip it (consider Freshdesk Growth) if:

You need live chat, phone integration, and AI-suggested responses, and you’re willing to pay $15/agent/month for hosted convenience.

Alternatives worth considering

Zammad — also open source (GPL), actively modernized, has a real REST API, and includes live chat and Elasticsearch-powered search. The UI is substantially more contemporary than osTicket. If self-hosted is the constraint and UI matters, Zammad is the comparison to make.
Peppermint — newer, minimalist, MIT-licensed, Docker-first. Less mature than osTicket but actively developed with a modern React frontend.
Freshdesk — closed SaaS with a genuinely usable free tier for small teams. No self-hosting, but the zero-infrastructure cost is real.
Zoho Desk — more comprehensive than Freshdesk’s free tier, integrates with the broader Zoho suite. SaaSworthy lists it as the top osTicket alternative [2].
Zendesk — the incumbent. Best integrations, most polished, most expensive. The reason most people are looking for alternatives.
Chatwoot — open source, modern, live-chat-first with ticketing added. Better fit if your support is chat-heavy rather than email-heavy.

For a non-technical founder escaping Zendesk costs and comfortable with a VPS, the realistic shortlist is osTicket vs Zammad. Pick osTicket if you prioritize stability and an enormous community with documented solutions to every edge case. Pick Zammad if you want something that looks like it was built in the last five years.

Bottom line

osTicket is the Toyota Corolla of open-source help desk software: not exciting, not modern, but reliable, well-documented, and nearly free to run. If your support operation is email-driven, your team is 5–50 agents, and you’re currently paying $200–$500/month for Zendesk or a similar SaaS, the math is hard to argue with. Self-hosted on a basic VPS, you eliminate that bill entirely for the cost of an afternoon of setup and occasional maintenance.

The honest trade-offs are real: the UI hasn’t aged gracefully, there’s no REST API worth building against, OAuth2 setup is a required extra step that the install docs undersell, and there’s no AI or live chat in the box. If any of those are requirements, osTicket will frustrate you and you should look at Zammad or Freshdesk instead.

But for the audience this is actually built for — IT administrators at nonprofits and schools, operations teams at small manufacturers, anyone running a ticket queue on a constrained budget — osTicket has been solving this problem for fifteen years, has the community threads to prove it, and costs nothing to find out if it fits.

If the deployment is the blocker, that’s what upready.dev handles for clients. One-time setup, you own the infrastructure, no recurring SaaS bill.