A $6 VPS Can Host Your 2026 Help Desk: We Tested Three Free Options
At FreeSoft Labs, we like a simple test: take three open-source tools that promise to replace paid software, put them on the cheapest hardware that still makes sense, and see which one survives a normal Monday. For this round, the tools were osTicket, Zammad, and UVdesk. The hardware was a single $6/month VPS with 2 vCPU, 4 GB RAM, and 80 GB SSD. The users were imaginary. The tickets were not.
The Test Bench: One VPS, Three Clean Snapshots
We used Ubuntu 24.04 LTS and started each system from a fresh snapshot so no leftover database could cheat the results. osTicket and UVdesk ran on a LEMP stack. Zammad ran on Docker Compose because that is the supported path, and that choice mattered. On 4 GB RAM, Zammad needs swap to stay polite. We added 2 GB after the first install nearly stalled. Screenshot note: the Zammad dashboard looked modern, but Elasticsearch was still warming up when we first logged in.
Setup Time: The Installer Is the Easy Part
| System | Install time | First ticket | Main gotcha |
|---|---|---|---|
| osTicket | 38 min | 52 min | PHP IMAP extension and cron |
| Zammad | 55 min | 70 min | Elasticsearch memory; swap needed |
| UVdesk | 47 min | 64 min | File permissions and mailer config |
| Times include OS packages and a coffee refill. None of these installs is hard if you have built a LAMP server before. All three are annoying if you have not. The gotchas are boring in the way that costs an afternoon: a missing PHP module, a cron job that never runs, a permissions error that only shows up when a ticket arrives. |
Email Ingestion: The Make-or-Break Test
We sent 40 messages to one support mailbox: plain text, HTML, attachments, duplicate Message-IDs, and reply chains. osTicket fetched reliably, but it is cron-driven, so the first pull took about five minutes. Zammad handled threading and channel setup best; it felt like the system understood that email is not a special case. UVdesk worked, but polling felt slower and the mailer settings took more poking. Screenshot note: our osTicket email log showed the first failed IMAP login in red, which is exactly the kind of thing you want to see before go-live. Use an app password for Gmail or Google Workspace. If you insist on OAuth, budget extra time.
Routing, SLA, and the After-Hours VPN Ticket
We built three scenarios: an after-hours VPN problem, a billing question, and a password reset. osTicket handled departments, help topics, and filters well, but SLA tracking felt like a due-date field with extra steps. Zammad was the clear winner for triggers, groups, and SLA behavior; it is the only one that felt like it wanted the job. UVdesk has workflows and SLA features, but the UI made us click more than we wanted. For a US small shop with one IT person, fewer clicks matter.
Upgrades and the Failed-Update Drill
osTicket upgrades are manual: back up files and the database, replace the code, run the upgrade. It was slow but predictable. Zammad upgrades through Docker until they do not. Our first pull ran out of memory during migration, which is a polite way of saying the VPS went quiet. We restored the snapshot, added swap, and retried. Total downtime: 18 minutes. UVdesk composer update broke file permissions and took 25 minutes to recover. This is the part free-software roundups skip: recovery is a feature. Snapshot before every update, even on a $6 VPS.
The $6/Month Verdict: Pick This If
Pick osTicket if you want email-first ticketing, low RAM use, and a PHP/MySQL stack you already understand. It is the safe boring pick for a solo tinkerer. Pick Zammad if SLA tracking, routing, and a team inbox are real requirements. Give it 4 GB RAM plus swap and do not expect it to be light. Pick UVdesk if you want a more modern interface and can tolerate update quirks. It is not the one to choose if you hate fixing permissions. The license is $0 on all three. The VPS is $6/month. The real cost is the afternoon you lose to email settings. For most US small shops, osTicket is the lowest-drama start; Zammad is the one to choose when tickets are customer-facing and SLAs are not optional.
