FreeScout

Last reviewed Sep 13, 2026 · 783 words

FreeScout gives a team of 3 to 20 people a shared inbox with assignment, private notes, canned replies and a customer history, for the cost of a 1 GB VPS, where Help Scout would charge per seat per month. The core is genuinely free under AGPL-3.0. The catch is that dozens of the things you will eventually want, from a knowledge base to Slack notifications to SLA timers, are paid modules bought once per installation, at last check mostly in the 10 to 40 dollar range each. Price that in honestly: a fully fitted FreeScout costs a few hundred dollars once rather than a few hundred dollars a month, and that is still the best deal in self-hosted support.

It is email, all the way down

FreeScout is a Laravel application with MySQL or MariaDB behind it. A mailbox in FreeScout is an IMAP account it polls plus an SMTP account it sends through. Every incoming message becomes a conversation, replies go out from the shared address with the agent's name, and threading works because FreeScout tracks message IDs rather than trusting subject lines. There is no live chat, no phone, no social inboxes in the core. It is a help desk for people whose support arrives as email, and it is unashamed about that. If your support is chat-first, Chatwoot is the tool, and a heavier one.

Because it is IMAP, any mailbox works: a Google Workspace address (with OAuth configured in the mailbox settings), Microsoft 365, Fastmail, your own Postfix. One mailbox per queue (support@, billing@) is the pattern, and agents can belong to several.

Two things the install guides underplay

The first is cron. FreeScout fetches mail, sends queued replies and runs cleanups from a scheduler that must be called every minute:

* * * * * php /var/www/freescout/artisan schedule:run >> /dev/null 2>&1

Forget it and the inbox looks fine but nothing ever arrives. In Docker the image's supervisor handles this; on bare metal it is the step people skip. The second is the app URL and the reverse proxy: set APP_URL to the public HTTPS address and make sure the proxy passes X-Forwarded-Proto, or attachment links and notification emails point at http:// and break.

For the install itself, the project publishes a bare-metal guide for Ubuntu with PHP 8, nginx and MariaDB that takes about 30 minutes, and there is a well-used community Docker image (tiredofit/freescout) that bundles PHP, nginx and cron. Either way the memory floor is around 1 GB with the database included, a fraction of what Zammad needs once Elasticsearch is in the picture.

Modules: buy the three that matter, ignore the rest

The module ecosystem is where FreeScout grows into a real help desk. The ones I consider table stakes for a team: Knowledge Base (public help articles that also deflect tickets), Workflows (if-this-then-assign automation), and Time Tracking or SLA depending on whether you bill or promise. Slack and Teams notifications, Custom Fields, and Satisfaction Ratings are the next tier. All install by uploading a zip on the Modules page and entering a licence key tied to your domain; moving domains means contacting the developer, a mild annoyance rather than a blocker.

What you cannot buy: a mobile app that is more than the responsive web UI, or per-mailbox branded customer portals in the core. If those are hard requirements, Zammad has both and costs you an Elasticsearch node and about 4 GB of RAM for the privilege.

Who actually runs it

Small SaaS companies, agencies, web shops and open-source projects with a support@ address that more than one person reads. It is also popular inside IT departments as a low-ceremony internal ticket queue because staff already know how to send an email. That is the sweet spot: below it a shared Gmail label is enough, above it, at 30-plus agents with phone and chat, you are in Zammad or commercial territory.

What I'd do

For a small business or a project with a support@ address that two or more people read, FreeScout in Docker on a 2 GB VPS, one IMAP mailbox per queue, cron verified on day one by sending yourself a test ticket, and the Knowledge Base and Workflows modules bought in the first month. Back up the database and the storage directory nightly. If support arrives through a website chat widget rather than email, or you need branded portals and phone, choose Zammad or Chatwoot from the communication category and accept the heavier box; the Help Scout switching guide has the fuller comparison.