- Published on
Pathao Tickets: replacing Zendesk with a patched open source helpdesk

- Authors

- Name
- Nadim Tuhin
- @nadimtuhin
On this page
Support wanted live chat and automations. Zendesk could do both, for a lot more money. We went another way.
Pathao is Bangladesh's largest super-app for rides, food delivery, courier and payments. Think Grab or Gojek. Its customer support ran on Zendesk, and our plan only covered tickets.
Support wanted two more things:
- Live chat, so customers could get an answer without waiting on an email thread.
- Automations, so the same kinds of tickets didn't need a human to sort them every time.
Adding chat and automations at our volume would have cost a lot more than we were already paying.
The question that started it
Our CTO asked a simple question: can we have something simple instead?
Not a rebuild of Zendesk. Just something that did the three things support used every day, and cost a fraction.
The suggestion
My suggestion: stop shopping for vendors. Pick a solid open source helpdesk, self-host it, and patch it until it fits how Pathao support works.
The reasoning was plain. Ticketing, an agent inbox and a chat widget are a solved problem, and good open source projects already do them well.
What no project does out of the box is your company's routing rules, your internal tools and your edge cases. That last part is a much smaller job than building a helpdesk. And it's the only part that's really ours.
What we built on top
We called it Pathao Tickets. On top of the open source base we added or reworked:
| Capability | Hosted Zendesk | Self-Hosted Pathao Tickets |
|---|---|---|
| Monthly Cost | ~$18,000/mo at scale | ~$5,500/mo (roughly 69% cost reduction) |
| Live Chat | Paid add-on per seat | Built-in WebSocket engine holding message delivery under 80ms |
| Automations | Strict tier rate limits | In-process Redis tag worker processing ~5,000 tickets/hr |
| Data Residency | Third-party cloud | On-premise PostgreSQL within internal VPC |
- Ticketing that matched how support teams were split, so a ticket landed with the right team instead of a shared pile.
- Live chat for customers, feeding into the same agent inbox as tickets, so agents worked one queue, not two tools.
- Automations based on tags. A ticket gets tagged, by a rule or by an agent, and the tag drives what happens next: which team owns it, what priority it gets, which canned flow kicks in. Support leads could reason about tags. They couldn't reason about code.
Most of the work was monkey patching: small, targeted changes to the open source code instead of a long-lived fork that drifts. There were 14 targeted patch files, and each had one job. That kept upgrades possible and kept the surface area small enough for a few engineers to own.


The result
Pathao Tickets handled a very large volume of support conversations on modest infrastructure.
Its infrastructure cost roughly a third of the Zendesk bill for tickets alone, and it included the chat and automations that would have cost far more on Zendesk.

What I took from it
- Price the vendor quote against the boring version. We asked "what do our agents really click every day?" and the list was short.
- Buy the solved problem, own the specific one. Open source covered the inbox and the widget. Our time went only into routing, tags and integrations, the parts that were specific to Pathao.
- Patch small, not fork big. Small, single-purpose patches are cheap to review and cheap to carry through upgrades. A big fork turns into a second product you never meant to maintain.
- Give operators a lever they understand. Tags made automation something support leads could change themselves. That's why the automations got used.
If a SaaS quote is pushing you toward a number that's hard to justify, check what your team really uses. Often a well-maintained open source project and a handful of careful patches cover it for a fraction of the price.
Frequently asked questions
- Can you replace Zendesk with an open source helpdesk?
- Yes. Pathao self-hosted an open source helpdesk and patched it for ticketing, live chat and tag-based automations. Its infrastructure cost roughly a third of what Zendesk charged for tickets alone.
- How much does a self-hosted helpdesk cost compared to Zendesk?
- For Pathao, the self-hosted setup cost roughly a third of the Zendesk bill for tickets only, and it also covered live chat and automations, which would have cost far more on Zendesk.
- Should you fork an open source tool or patch it?
- Patch it with small, single-purpose changes. At Pathao, small patches stayed cheap to review and survived upgrades, while a big fork would have become a second product to maintain.
Related posts
- PathaoTalk: how we moved a whole company off Workplace Chat in a month
Workplace Chat had no markdown, snippets or integrations, and it charged per seat. Self-hosted Mattermost replaced it company-wide in about a month and cut our chat costs.
- Self-hosting CodiMD with company sign-in so engineers kept using it
Pathao engineers already liked a hosted markdown editor. I self-hosted the open-source CodiMD behind company sign-in, and the whole company moved to it.
- Replacing OpenLens: why I kept K9s, Headlamp, and Kubenav
OpenLens is no longer maintained. I tested 13 Kubernetes dashboards and kept three: K9s, Headlamp, and Kubenav.