Skip to content

Choosing an open source ticketing system

If your team needs the right to run, change and share its help desk software, start with osTicket or Zammad. If you need a queue you can use for free without running servers, Latch offers a hosted workspace.

For teams that need to inspect the code and operate their own installation, Latch Enterprise offers source access under a commercial agreement. The agreement defines modification and redistribution rights.

Latch task list showing the Accra router outage assigned for a field visit and the Copenhagen kiosk repair on hold for parts
Inside the Latch queue. These sample tickets show why two sites need different follow-up. Accra has a field visit scheduled. Copenhagen is waiting for parts.

osTicket and Zammad compared

Both projects publish their code under licences that permit modification and redistribution subject to their terms. Hosting and support are separate purchasing decisions. See the Open Source Definition.

osTicket

Licence and installation
GPL v2. A self-hosted installation uses PHP, a web server and MySQL. Project and requirements
When to shortlist it
Your team shares support mailboxes and a web form. osTicket accepts both and can route incoming mail by address to a department. Email routing guide
A first test
Send a request to your support address. Confirm which department receives it, reply as an agent, then check where the customer's follow-up lands.

Zammad

Licence and installation
GNU AGPL v3. The project documents self-hosted installations using system packages, Docker or Kubernetes. Installation guides
When to shortlist it
Your agents handle requests across channels such as email, chat and telephone. Zammad brings those channels into one help desk. Project, channels and licence
A first test
Have one agent take a chat and another handle a follow-up by email. Check which customer details and earlier messages the second agent can find.

When to consider Latch as a help desk alternative

You need a free queue that someone else hosts

Use the hosted workspace to receive a request, assign an owner and follow its history. It holds up to 100 tickets and 250 MiB of attachments. If agents need to email customers back from the ticket, budget for a paid plan. Free workspace features and limits

A ticket needs a second person's approval

In Latch, a plugin action can require an independent reviewer. For a transaction retry, the reviewer sees the requester, amount and reason before approving or rejecting it. Execution is a separate step. Plugin actions require a paid plan. Follow a request through approval

Your team needs to operate or inspect the application

With Enterprise, agree which code and releases you receive, where you may run modified versions, any redistribution rights, and who supports upgrades. Your team operates its own installation and backups. Self-hosted ticketing and deployment checklist

Latch approval dialog showing the saved transaction ID, KES 18,450 amount, retry reason and reviewer decision buttons
Reviewing a payment retry in Latch. Maya requested another attempt after a network timeout. The reviewer can see exactly which transaction would run. This example uses synthetic transaction data.
FAQ

Questions about open source and free ticketing

Use these answers to check hosting costs, source rights and what you can test in Latch.

Which open source help desks can I install myself?

osTicket and Zammad both publish their source and installation instructions. osTicket uses PHP and MySQL and can route incoming email to a department. Zammad handles channels including email and chat, and documents installation with Docker, system packages or Kubernetes.

What should I budget for when self-hosting a free ticketing system?

Include the server, database, attachment storage, mail delivery, backups and the time someone spends applying updates. For a realistic estimate, restore a ticket with its attachment to a second installation and time the work.

Is Latch open source?

No. Latch supplies source code to Enterprise customers under a commercial source licence. The agreement defines which releases you receive and what you can inspect, modify, deploy or redistribute.

What can I test in the free hosted Latch workspace?

You can receive requests, assign owners and keep a history for up to 100 tickets with 250 MiB of attachment storage. Latch operates the workspace. Outbound ticket replies, acknowledgments, notifications and plugin actions are excluded. Account activation, invitation and password-reset emails are available.

Do we need source access to customize a Latch workflow?

You can configure ticket fields, tags and evidence requirements in the application. On a plan with plugin actions, a service your team maintains can run an operation after independent review. For a change to the application itself, agree modification rights and responsibility for testing future upgrades under Enterprise.

Try Latch

Test a ticket in a hosted workspace

Give a sample request an owner, add an attachment and follow its history. For a customer-operated installation, review the Enterprise deployment options.