Layer 5 · self-hosting reality check
What it actually takes to self-host FreeScout
The docs say not stated by the vendor. Its wiki says there are no minimum requirements and that the cheapest $5/mo server, including an EC2 t2.nano with 512 MB, is enough. Cloudron runs it under its default 256 MB app limit, with MySQL as a separate service.. In practice you want 1–2 GB. The vendor says the cheapest VPS works; 2 GB gives MySQL and the queue worker room as mailboxes and history grow.. 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 FreeScout 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 | not stated by the vendor. Its wiki says there are no minimum requirements and that the cheapest $5/mo server, including an EC2 t2.nano with 512 MB, is enough. Cloudron runs it under its default 256 MB app limit, with MySQL as a separate service. |
|---|---|
| RAM — what it really needs | 1–2 GB. The vendor says the cheapest VPS works; 2 GB gives MySQL and the queue worker room as mailboxes and history grow. |
| CPU | 1 vCPU; the vendor publishes no requirement |
| Disk | MySQL plus attachments on local disk. Both grow with email volume, attachments being most of it. Remote storage support arrived in September 2026. |
| Monthly cost | $5–12/mo for a 5-agent instance on a 1–2 GB VPS, plus one-time paid modules if you need features like workflows, tags or a knowledge base |
| Setup time | 1–2 hours by hand on a LEMP stack; less with the community Docker image |
| How you install it | Manual install on nginx or Apache with PHP-FPM and MySQL/MariaDB (or PostgreSQL), then the web installer and a per-minute cron, as the official Installation Guide describes. Or the community-maintained Docker image FreeScout's site links to, which bundles nginx, PHP-FPM and cron; you bring the database. |
| Ongoing maintenance | Small releases arrive often (three in eight days in September 2026) and are applied with the built-in updater, which needs the web user to own every file. On top of that come paid module updates and keeping IMAP fetching healthy: a 2026 release broke it for some Gmail users. |
| Where it stops scaling | No published ceiling. It is one PHP app on MySQL, so you grow it with a bigger box first, then a separate database host. |
The thing that catches people out
Fetching mail, sending replies and notifications all run from one cron line: `php artisan schedule:run` every minute as the web user, which also starts the background queue:work process. Add `--no-interaction` and the queue worker never starts. Run it as another user and file ownership breaks. Lose cron in a container and mail silently stops. The web UI keeps working throughout, so nobody notices until a customer chases. Copy the cron line exactly from the Installation Guide, and check System » Status after every change.
When not to self-host FreeScout
You want workflows, reports and a knowledge base included rather than bought one module at a time, or live chat and social messaging are your main channels. Zammad or Chatwoot fit those better.
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 FreeScout actually need?
- 1–2 GB. The vendor says the cheapest VPS works; 2 GB gives MySQL and the queue worker room as mailboxes and history grow. in practice. The documented minimum is not stated by the vendor. Its wiki says there are no minimum requirements and that the cheapest $5/mo server, including an EC2 t2.nano with 512 MB, is enough. Cloudron runs it under its default 256 MB app limit, with MySQL as a separate service., which is the figure at which the process starts rather than the figure at which it works under real use. 1 vCPU; the vendor publishes no requirement alongside it.
- What does self-hosting FreeScout cost per month?
- $5–12/mo for a 5-agent instance on a 1–2 GB VPS, plus one-time paid modules if you need features like workflows, tags or a knowledge base This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for small releases arrive often (three in eight days in September 2026) and are applied with the built-in updater, which needs the web user to own every file. On top of that come paid module updates and keeping IMAP fetching healthy: a 2026 release broke it for some Gmail users.
- How long does it take to set up FreeScout?
- 1–2 hours by hand on a LEMP stack; less with the community Docker image, via Manual install on nginx or Apache with PHP-FPM and MySQL/MariaDB (or PostgreSQL), then the web installer and a per-minute cron, as the official Installation Guide describes. Or the community-maintained Docker image FreeScout's site links to, which bundles nginx, PHP-FPM and cron; you bring the database..
- When should I NOT self-host FreeScout?
- You want workflows, reports and a knowledge base included rather than bought one module at a time, or live chat and social messaging are your main channels. Zammad or Chatwoot fit those better.
- What is the most common mistake when self-hosting FreeScout?
- Fetching mail, sending replies and notifications all run from one cron line: `php artisan schedule:run` every minute as the web user, which also starts the background queue:work process. Add `--no-interaction` and the queue worker never starts. Run it as another user and file ownership breaks. Lose cron in a container and mail silently stops. The web UI keeps working throughout, so nobody notices until a customer chases. Copy the cron line exactly from the Installation Guide, and check System » Status after every change.