osTicket vs Zammad: Which Helpdesk to Self-Host?

Quick Verdict

osTicket is the better choice for small teams (1-5 agents) who primarily handle email-based tickets and want something that runs on minimal hardware. Zammad is the better choice for growing teams (5-50+ agents) who need multi-channel support, powerful full-text search, and a modern interface.

Overview

osTicket has been the go-to open-source helpdesk since 2003. It’s PHP-based, mature, and runs on a $5/month VPS. Zammad launched in 2016 as a modern alternative with a Ruby on Rails backend, Elasticsearch-powered search, and support for email, chat, phone, Twitter, and Facebook channels. Both are free and open-source.

Feature Comparison

FeatureosTicketZammad
LanguagePHPRuby on Rails
DatabaseMySQL/MariaDBPostgreSQL
SearchMySQL full-textElasticsearch (instant, full-text across everything)
Multi-channelEmail, web form, phone (manual)Email, chat, phone, Twitter, Facebook, Telegram
Knowledge BaseBuilt-in FAQBuilt-in knowledge base
SLA ManagementYesYes
Ticket Triggers/AutomationBasic filtersAdvanced triggers + macros + overviews
Customer PortalYes (web form + ticket tracking)Yes (with live chat option)
APIREST APIREST API + GraphQL (partial)
LDAP/AD IntegrationPluginBuilt-in
Two-Factor AuthPluginBuilt-in
Mobile AppNo (responsive web)No (responsive web, PWA-ready)
Docker ImageCommunity (tiredofit/osticket)Official (ghcr.io/zammad/zammad)
LicenseGPL v2AGPL v3
First Release20032016
GitHub Stars3,200+4,700+

Installation Complexity

osTicket runs as 2 containers: app (PHP-FPM + Nginx) + MariaDB. Configuration is via environment variables, and the first startup auto-creates the database and admin account. Total time to running: ~5 minutes.

Zammad runs as 8-10 containers: Rails server, WebSocket server, scheduler, Nginx, init, backup, PostgreSQL, Redis, Memcached, and optionally Elasticsearch. First startup takes 2-3 minutes for database migrations. Total time: ~10-15 minutes, plus the vm.max_map_count kernel parameter for Elasticsearch.

Winner: osTicket. Dramatically simpler stack.

Performance and Resource Usage

MetricosTicketZammad
Idle RAM~400-600 MB~3-4 GB (with Elasticsearch)
Minimum viable RAM1-2 GB6 GB (10 GB with Elasticsearch)
CPU (idle)Very lowMedium
Docker containers28-10
Disk (application)~500 MB~2 GB
Cold start time~10 seconds~60-120 seconds

This is the biggest practical difference. osTicket runs comfortably on a Raspberry Pi 4 or a $5/month VPS. Zammad needs a dedicated server with at least 6 GB RAM — realistically 8-10 GB for a smooth experience with Elasticsearch.

Winner: osTicket. Runs on one-fifth the hardware.

Community and Support

MetricosTicketZammad
Community SizeVery large (20+ years)Growing (8+ years)
DocumentationGood (official docs + large forum)Excellent (detailed, well-organized)
Paid SupportYes (from SupportSystem Inc)Yes (from Zammad GmbH)
Plugin EcosystemModerate (community plugins)Limited (apps/webhooks)
Update FrequencyQuarterly releasesMonthly releases
Commercial VersionosTicket Cloud ($12-39/agent/month)Zammad Enterprise ($5-35/agent/month)

osTicket has a larger installed base and more community solutions for common issues. Zammad has better official documentation and more frequent updates.

Use Cases

Choose osTicket If…

  • Your team has 1-5 support agents
  • Email is your primary support channel
  • You have limited server resources (1-2 GB RAM)
  • You want the simplest possible setup
  • You’re running on a budget VPS
  • You don’t need real-time chat or social media integration

Choose Zammad If…

  • Your team has 5+ agents and is growing
  • You need multi-channel support (email + chat + social)
  • Full-text search across all tickets is important
  • You want modern trigger-based automation
  • You have 8+ GB RAM available
  • You need LDAP/Active Directory integration for agents

Final Verdict

These are not competing products — they serve different scales. osTicket is for small operations that need reliable email-to-ticket conversion on minimal hardware. It’s the Toyota Corolla of helpdesks: not exciting, but it starts every time and costs almost nothing to run.

Zammad is for teams that have outgrown simple email-based ticketing. Its multi-channel support, Elasticsearch-powered search, and modern automation make it feel like a self-hosted Zendesk. The price you pay is RAM — Zammad’s stack needs 5-10x more resources than osTicket.

For solo operators and micro-teams: osTicket. For teams building a proper support operation: Zammad. If you want something in between — modern UI but lighter than Zammad — also consider FreeScout.

Comments