Layer 5 · self-hosting reality check
What it actually takes to self-host UVdesk
The docs say 4 GB (vendor README and system-requirements page). In practice you want 4 GB. That is the vendor's own floor, and there is no lighter documented setup.. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Freshdesk alternatives, where UVdesk is one of the picks.
Wondering whether you need to at all? Is Freshdesk free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 4 GB (vendor README and system-requirements page) |
|---|---|
| RAM — what it really needs | 4 GB. That is the vendor's own floor, and there is no lighter documented setup. |
| CPU | The vendor asks only for a 1 GHz processor; 2 vCPU is what comes with a 4 GB plan |
| Disk | MySQL plus attachments on local disk. Modest for a small team; grows with ticket attachments. |
| Monthly cost | $12–24/mo for a 5-agent instance on a 4 GB VPS |
| Setup time | 2–3 hours on a LAMP box; longer if the IMAP and Mailparse extensions fight your PHP version |
| How you install it | composer create-project uvdesk/community-skeleton (or the release zip) on Apache or nginx with PHP, MySQL 5.7.23+ and the IMAP and Mailparse extensions, then the web installer wizard. A cron job runs the mailbox-refresh command that turns email into tickets. |
| Ongoing maintenance | You maintain PHP and its IMAP and Mailparse extensions yourself, keep the mailbox cron running, and upgrade through Composer. There have been no releases to apply since September 2025. |
| Where it stops scaling | No published sizing beyond the 4 GB floor. It is a Symfony app on MySQL, so MySQL moves off-box first. At its current maintenance pace, do not plan a large deployment on it. |
The thing that catches people out
Development has stalled. The last release, v1.1.8, shipped in September 2025, and neither the app nor its core framework has had a commit since early October 2025, with about 80 open issues and pull requests. The README still names PHP 8.1, which no longer gets security fixes, and the docs list PHP 8.2 at most, whose security support ends on 31 Dec 2026. Mail-to-ticket depends on PHP's IMAP extension, which PHP 8.4 removed from core. So you will soon choose between an unsupported PHP and an untested one. If you run it anyway, pin PHP 8.2 or 8.3 and plan your way out.
When not to self-host UVdesk
You want a helpdesk you will still be patching in two years. FreeScout (releases several times a month) and Zammad are actively maintained and cover the same ground.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does UVdesk actually need?
- 4 GB. That is the vendor's own floor, and there is no lighter documented setup. in practice. The documented minimum is 4 GB (vendor README and system-requirements page), which is the figure at which the process starts rather than the figure at which it works under real use. The vendor asks only for a 1 GHz processor; 2 vCPU is what comes with a 4 GB plan alongside it.
- What does self-hosting UVdesk cost per month?
- $12–24/mo for a 5-agent instance on a 4 GB VPS This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for you maintain PHP and its IMAP and Mailparse extensions yourself, keep the mailbox cron running, and upgrade through Composer. There have been no releases to apply since September 2025.
- How long does it take to set up UVdesk?
- 2–3 hours on a LAMP box; longer if the IMAP and Mailparse extensions fight your PHP version, via composer create-project uvdesk/community-skeleton (or the release zip) on Apache or nginx with PHP, MySQL 5.7.23+ and the IMAP and Mailparse extensions, then the web installer wizard. A cron job runs the mailbox-refresh command that turns email into tickets..
- When should I NOT self-host UVdesk?
- You want a helpdesk you will still be patching in two years. FreeScout (releases several times a month) and Zammad are actively maintained and cover the same ground.
- What is the most common mistake when self-hosting UVdesk?
- Development has stalled. The last release, v1.1.8, shipped in September 2025, and neither the app nor its core framework has had a commit since early October 2025, with about 80 open issues and pull requests. The README still names PHP 8.1, which no longer gets security fixes, and the docs list PHP 8.2 at most, whose security support ends on 31 Dec 2026. Mail-to-ticket depends on PHP's IMAP extension, which PHP 8.4 removed from core. So you will soon choose between an unsupported PHP and an untested one. If you run it anyway, pin PHP 8.2 or 8.3 and plan your way out.