Does self-hosting Front cost less than FreeScout or Chatwoot in practice?
On license fees alone, self-hosting is where the difference is starkest. FreeScout's README describes unlimited agents, tickets and mailboxes, and its paid modules are sold as one-time lifetime licenses for a single instance. Chatwoot's Community Edition is listed at $0 on its self-hosted plans page, while Premium Support is $19 per agent per month and Enterprise Edition is $99 per agent per month, adding SSO with SAML and SLA policies. Front's per-seat prices are not published in the sources used for this page, so the comparison has to start from your own contract: seat count, plan tier, API usage and any add-ons on your current renewal invoice.
License savings do not equal total savings. Self-hosting moves cost into servers, which for Chatwoot means at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, plus Redis 7.0 or higher, PostgreSQL and at least 1 GB of swap. Email deliverability is a recurring cost of its own: SPF, DKIM and DMARC records, a sending domain with reputation, and monitoring of bounces. Migration takes staff time, and so does patching, backups and upgrades. Ask any implementation partner for a written quote that separates one-time setup from recurring operations, and ask your own team to estimate hours per month against the skills it has today.
The answer therefore depends on three things. Seat count matters most: per-seat pricing grows with headcount, while FreeScout's unlimited agent model does not, so a large team gains more from it. Module needs matter next, because a FreeScout deployment that needs SAML SSO or workflows pays for those modules once, while a Chatwoot deployment that needs SSO or SLA policies moves to the Enterprise tier. Operations skills decide the rest. A team that already runs Linux, PostgreSQL and mail infrastructure may find the running cost small, while a team without that capacity should price in managed support or a retainer before choosing self-hosting on cost grounds.
Which cost components change when you move from Front
This table compares each cost component of running Front with the same component under self-hosted FreeScout or Chatwoot, and marks whether it is one-time or recurring. Read it as a checklist: ask Front for your current seat count, API usage and plan terms, then price each row for the open-source option you are evaluating. The main takeaway is that the software line is only one of several recurring costs.
| Cost component | Front today | FreeScout or Chatwoot self-hosted | One-time or recurring |
|---|---|---|---|
| Subscription or license | Per-seat plan (Starter, Professional or Enterprise) with seat caps; confirm current seat and plan terms in writing | FreeScout: free core with one-time lifetime module licenses per instance. Chatwoot: free Community edition, or paid self-hosted plans per agent per month | Front: recurring. FreeScout: mostly one-time. Chatwoot: free or recurring |
| Paid API and integration capacity | Paid API capacity may be needed for higher volumes; confirm limits and overage terms with Front | FreeScout API and webhooks are a paid module; Chatwoot API access is included in the self-hosted build; confirm the modules you need | Front: recurring. FreeScout: one-time per module |
| Servers and hosting | None on Front's side | Virtual machines or containers for web, workers and database; Chatwoot needs PostgreSQL, Redis and at least 4 cores and 4 GB RAM for moderate volume | Recurring |
| Email sending and deliverability | Included in the plan; Front manages sending infrastructure | You run SMTP or IMAP mailboxes, plus SPF, DKIM and DMARC records, bounce handling and a relay provider if needed | Recurring |
| Migration | Export from Front and map shared inboxes, rules and contacts; confirm export formats with Front | Import into FreeScout or Chatwoot, mailbox setup and testing; effort depends on history volume and integrations | One-time |
| Implementation and customization | Mostly configuration inside Front; customization is limited to its own features | Installation, hardening, module setup, channel connections and workflow design, often fixed scope with a partner | One-time |
| Support | Included in the plan; higher tiers or added support may cost more | Community forums for Community editions; paid support tiers or a retained partner for production | Recurring |
| Upgrades, patching and backups | Handled by Front | Your team or partner applies releases (FreeScout releases roughly weekly), patches OS and database, and runs backups and restore tests | Recurring |
| Internal skills | Admin time for seats and rules | Staff or contractors who know PHP or Ruby, PostgreSQL, mail routing and Linux operations | Recurring |
What moves the comparison most
Front is priced per seat, so the total cost of a self-hosted replacement depends on who answers, how much they handle, and which channels and controls they need. The six drivers below decide whether FreeScout or Chatwoot stays cheap, and each one should be priced against the written Front plan you are comparing.
Agent and seat count
Front charges per seat, so every agent added to the shared inbox adds a recurring line. FreeScout and Chatwoot Community Edition carry no per-agent software fee, but Chatwoot's Premium Support and Enterprise Edition are priced per agent per month. Count named agents, occasional responders and supervisors separately, because each group may need a different seat type or role in the replacement.
Conversation volume
Chatwoot's published requirements scale the server with load: 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, and 8 cores and 8 GB for up to 20,000. Your monthly conversation count, attachment volume and peak hours decide which tier you provision. Measure your current peak day before you size hardware, and ask whether the vendor's figures assume a particular database and Redis setup.
Channels needed
An email-only shared inbox is the simplest case for FreeScout, which connects mailboxes over SMTP, IMAP and POP3 with OAuth for Microsoft 365 and Google Workspace. WhatsApp, Facebook, Instagram, Telegram, Line and SMS are native to Chatwoot's inbox. Each added channel brings its own provider account, fees and approval process, which the replacement will not remove, so list every channel your Front plan carries today.
Paid FreeScout modules
FreeScout's modules are sold as one-time lifetime licenses for a single instance, and the list includes LDAP Integration, SAML SSO, API and Webhooks, Knowledge Base, Satisfaction Ratings, Time Tracking and Workflows. The AI Integration and S3 Storage modules are free. Identify which Front features you rely on, such as SSO or rules, and price those modules up front, since each one is a separate cost that recurs only through updates you choose to buy.
Availability expectations
A self-hosted inbox runs on your servers, so uptime depends on your load balancer, database, Redis, backups and failover design. Chatwoot documents Kubernetes with a Helm chart for larger high-availability deployments, while a single-server FreeScout install is simpler but offers less redundancy. Ask what outage window the business accepts, and whether that expectation is priced into the hosting plan or left to on-call staff.
In-house operations skills
Chatwoot requires Ruby 3.2 or later, recommends Node.js 20.x, supports only PostgreSQL, and lists Ubuntu 20.04 as its only officially supported Linux distribution. FreeScout runs on PHP with Nginx, Apache or IIS. If your team does not already run these stacks, the cost of training, a managed hosting provider or a implementation partner becomes the largest line item, so confirm who will patch, back up and upgrade the platform.
How to build the comparison with your own numbers
This sequence turns your Front contract and your actual channel usage into a like-for-like total for Front, FreeScout and Chatwoot over the same period, so the comparison rests on your figures rather than on list prices.
Export your Front baseline from the contract
Your finance or procurement owner pulls the current Front order form or renewal notice and your admin console reports for seat count by role, plan tier (Starter, Professional or Enterprise), contract term and renewal date. Record the API usage you pay for, including any paid capacity beyond what the plan includes, and note whether any seats are shared inboxes, admin-only or inactive. Done when one sheet lists every paid line item with its billing period and the vendor's own wording for each cap.
Inventory the channels and modules you use
Ask the support lead and two or three daily agents which channels actually carry customer conversations: shared email addresses, website chat, WhatsApp, Facebook, Instagram, Telegram, SMS or Slack. Then list the features your team depends on, such as rules, saved replies, analytics, a help center, CSAT, SSO or API-driven automation. Compare that list against FreeScout's module catalog and Chatwoot's plan tiers, marking each item as included, paid, or not offered. Done when every feature you need has one of those three marks against each option.
Price two or three scenarios per option
Build a small model with at least a current-size scenario and one or two growth scenarios, varying agent count and modules. For FreeScout, add one-time lifetime license costs for each module instance you need, noting that the lifetime license covers one FreeScout instance and that some modules are free. For Chatwoot, use the free Community Edition as the base case, then add Premium Support or Enterprise Edition per agent per month for any feature that only those plans include, using the published per-agent figures. Done when each scenario shows the Chatwoot per-agent cost multiplied by agent count and the FreeScout module cost is shown once per instance.
Size the servers for each option
For Chatwoot, use the requirements page: at least 4 CPU cores and 4 GB RAM for up to 10,000 conversations a day, 8 cores and 8 GB for up to 20,000, plus at least 1 GB of swap, and note that Sidekiq can use more than 1 GB on a very active server. Estimate your daily conversation volume from the Front analytics or inbox counts. For FreeScout, which states no minimum CPU or RAM requirements, deploy a test instance on a small VM with your real mail connectors and measure load before sizing production. Add the hosting cost for each option in your own cloud account or data center, and ask your infrastructure team for the monthly figure. Done when each option has a server line with a size, a hosting cost source, and a note on which cloud or data center it runs in.
Add migration and mail deliverability lines
Add a one-time line for exporting Front data, mapping mailboxes and teams, configuring SMTP, IMAP or OAuth for Microsoft 365 or Google Workspace, and testing inbound and outbound mail. Confirm with the implementation partner or your own engineers what Front exports cover, including conversations, attachments and contacts, and what must be rebuilt by hand. Include a line for sending-domain work such as SPF, DKIM and DMARC records and any warm-up of a new sending address. Done when the migration line has a named owner, a scope statement, and a written list of items that will not transfer automatically.
Add a recurring operations role line
For each option, add a recurring line for the people who keep it running: patching the operating system and PHP or Ruby runtime, managing PostgreSQL or MySQL backups, watching queue workers and mail delivery, and applying FreeScout or Chatwoot upgrades. FreeScout publishes releases roughly weekly, so ask who applies them and how they are tested. Use your own staff rate or an outside retainer quote, and state the hours per month you expect. Done when each option has a named recurring role, an hour estimate from your own team, and a note on who covers on-call.
Compare totals over the same period
Place every option on one timeline, for example the same 36-month window, and separate one-time costs from recurring costs. Show the Front total with its seat tiers and any paid API capacity, the FreeScout total with lifetime module licenses and hosting, and the Chatwoot total with its plan choice, hosting and operations. Check that each scenario uses the same agent count and channel list, then record which assumptions move the result most. Done when a single table shows the three totals per scenario, the largest cost driver for each, and the open questions to resolve before a decision.
Request written quotes and confirmations
Ask Front in writing for the renewal price at your seat count, the cost of any additional seats or API capacity, and the effect of changing tier. Ask Chatwoot for confirmed per-agent pricing and whether your billing period changes it. For FreeScout, confirm module license prices, whether they apply per instance, and what updates are included. Request a written scope and fixed-price proposal from any implementation partner, covering server build, migration, mail setup, backup, upgrades and handover. Done when every number in the model is either backed by a written quote or marked as an assumption to confirm.
What migration and email delivery add to the bill
Moving history out of Front is the cost most often underestimated, because it is paid in staff time and vendor fees rather than in licenses. Start by deciding which history must come across: open conversations, closed threads, attachments, contacts, tags and saved replies. Then confirm what Front can export and in which format, since that determines how much transformation your team or a partner must do before import. Confirm the migration scope in writing with the vendor or partner you choose, including whether attachments, internal notes and assignment history are included. FreeScout offers a migration service for moving data from other help desks, and Chatwoot's data import path depends on your own tooling and conversation volume. Chatwoot requires PostgreSQL, Redis 7.0 or higher and Ruby 3.2 or later, so the platform itself carries a runtime and database footprint that must be installed, patched and backed up before any data moves. Plan a cutover window in which mailboxes are connected, forwarding is changed and a rollback path exists until the new inbox is trusted. Each of these steps is one-time effort, but the cutover window itself can run longer than expected if mailboxes are numerous.
Email deliverability is the recurring cost that most teams miss. Once FreeScout or Chatwoot sends replies from your domain, recipients judge those messages against SPF, DKIM and DMARC records, so you must publish and verify all three for the sending domain and keep them correct when your mail provider changes. The initial setup is one-time work for your DNS and mail administrators, but DMARC reports need someone to read and act on them every month. If you send through your own mail server rather than a relay, IP reputation becomes your responsibility as well, including blocklist monitoring, bounce handling and warm-up of new addresses. Relay services usually carry a per-message or per-volume charge that recurs, so ask for that figure in any quote that includes outbound mail. When you request a quote from a partner, ask for the migration scope, the export and import steps for each mailbox, the DNS and deliverability checks, and who owns the rollback. Ask how mailbox passwords and OAuth connections for Microsoft 365 or Google Workspace are handled during cutover.
Questions buyers ask before comparing costs
How much total effort does moving off Front take?
Total effort depends on four things: the number of shared mailboxes, the channels you need to connect, the amount of conversation history you must carry over, and how many people need retraining. Setup of the server and the help desk application is only one part. Mail routing, mailbox authentication, rules, saved replies, and user roles all need to be rebuilt and tested before agents rely on them. If you plan to use Chatwoot, website chat, WhatsApp, Facebook, Instagram, Telegram, and SMS each add configuration work. Ask for the effort split by these items so you can see which parts drive the total.
How long does a self-hosted help desk migration take?
The duration depends on the agreed scope, and no fixed timeline applies across all teams. The biggest schedule factors are the number of mailboxes, the channels in use, how clean your current data is, and how many approvals your mail and security teams require. Most DeployOpen engagements are fixed-scope, so the scope, deliverables, and timeline are agreed in writing before work starts. Ask for milestones tied to testing, cutover, and a parallel-run period, and ask who signs off each milestone on your side.
Can our own team run FreeScout or Chatwoot without a partner?
A team with Linux and mail administration skills can run either product, but the requirements differ. FreeScout runs on Nginx, Apache, or IIS with PHP 7.4 to 8.x and MySQL, MariaDB, or PostgreSQL. Chatwoot requires Ruby 3.2 or later, recommends Node.js 20.x, supports only PostgreSQL, recommends Redis 7.0 or higher, and lists Ubuntu 20.04 as its only officially supported Linux distribution. Recurring work includes patching, backups with tested restores, mail deliverability checks, and upgrades. Confirm whether your team can cover these tasks on a fixed schedule, since gaps in any of them create operational risk.
What does a fixed-scope implementation from DeployOpen include?
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents, and supports self-hosted open-source platforms inside your own cloud accounts, data centers, or air-gapped networks. For a help desk move, the written scope should name the platform, the mailboxes and channels, the integrations, the hardening baseline, the backup and restore approach, the documentation, and the handover. Ongoing support, upgrades, and continuous testing are available as retainers and are priced separately from the initial scope. DeployOpen does not publish a price list, so a quote follows from the written scope.
How does seat growth change the cost comparison?
Front is sold per seat, so each added agent adds recurring license cost, and the seat cap of your current plan determines when you must upgrade. Confirm current Front pricing and seat terms with Front, since this page does not list them. FreeScout states unlimited agents, tickets, and mailboxes, so its license cost does not grow with headcount. Chatwoot's Community Edition is free, while its paid self-hosted plans are priced per agent per month, so agent growth still affects Chatwoot's cost if you buy paid tiers. Server cost grows with conversation volume in both cases. Chatwoot's requirements page recommends 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day.
When are Chatwoot's paid self-hosted plans worth it?
Chatwoot's paid plans are worth comparing when you need features that the free Community Edition does not include. Its self-hosted plans page lists Premium Support at $19 per agent per month, which adds Captain AI, voice calls, custom branding, agent capacity, roles and permissions, and priority support. The Enterprise Edition at $99 per agent per month adds SSO with SAML and SLA policies. Compare each feature against the way your team works today. If you only need the shared inbox, automation, and reports, the Community Edition may cover the need, but confirm the feature set against your own requirements before you decide.
Do FreeScout module licenses recur every year?
FreeScout's modules page sells lifetime licenses for a single FreeScout instance, with lifetime updates, so the purchase is one-time per instance. Modules listed there include LDAP Integration, SAML SSO, API and Webhooks, Knowledge Base, Satisfaction Ratings, Time Tracking, and Workflows. The AI Integration and S3 Storage modules are free. Before you buy, confirm the license terms for each module, including whether a second instance, such as a test environment, needs its own license. Also confirm any charges for DeployOpen work to install or configure modules, since those are separate from the license.
What should we request in a quote before comparing costs?
Ask for a quote that separates one-time and recurring costs and names who is paid for each item. Request these items in writing:
- Scope: mailboxes, channels, integrations, and user counts in scope
- Software: which licenses are one-time, which are recurring, and the term of each
- Infrastructure: server sizing, hosting location, backups, and who pays the cloud bill
- Migration: which data moves from Front, what is excluded, and how cutover and rollback work
- Operations: upgrade policy, support hours, monitoring, and retainer terms
- Compliance inputs: documentation and evidence you will receive, noting that an independent auditor issues any audit report
Compare each quote on the same scope, and confirm Front's current export options with Front.
When self-hosting the help desk is the wrong choice
Staying on Front is often the cheaper and safer option for a very small team with low conversation volume. A self-hosted help desk has costs that do not shrink with volume: a server, a database, a mail setup, backups and someone's time for updates. Chatwoot's own sizing guidance starts at 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, which is far more capacity than a team handling a few dozen conversations a week will use. Illustratively, if a three-person team pays for a few seats and spends a few hours a month on the shared inbox, the fixed cost of running infrastructure can exceed the subscription. Before deciding, total the hours and infrastructure spend for the self-hosted option and compare them with the Front plan you would actually renew, including the seat count you need and any paid API capacity.
Self-hosting also assumes an operations capacity that many organizations do not have. Chatwoot requires Ruby 3.2 or later, recommends Node.js 20.x, supports only PostgreSQL and recommends Redis 7.0 or higher. Its documentation lists Ubuntu 20.04 as the only officially supported Linux distribution, so confirm the current supported platform before you plan the build. FreeScout is lighter, but email deliverability is its own discipline: outbound SPF, DKIM and DMARC records, bounce handling and IMAP or OAuth mailbox connections all need an owner. If nobody on the team can own patching, restores and mail configuration for the life of the system, a hosted service is the safer choice. An implementation partner can help you build the system, but the ongoing ownership still sits with your team unless you contract for support.
Two other situations favor staying put. The first is heavy reliance on Front features you have not mapped yet, such as specific rules, integrations, reporting or collaboration habits that your staff use every day. Each one needs a replacement, a test and a training plan, and a feature you discover late in the migration can change the budget. Ask Front for a written export of your current configuration and list every feature in use. The second is a short planning horizon. Setup, data migration and retraining are one-time costs that only pay back over time, and FreeScout module licenses, which are one-time per instance, help most when the system runs for years. If you expect to change tools or restructure support within a year or two, the migration effort may not be worth it.
How DeployOpen scopes a fixed-price implementation
DeployOpen plans and implements self-hosted FreeScout or Chatwoot inside your own cloud accounts, data centers or private networks, and agrees the scope in writing before work starts. Each engagement is fixed-scope, so the cost of the migration and first operating period is known before the build begins.
How we scope
- We inventory your Front seats, shared mailboxes, channels, integrations and API usage before recommending FreeScout, Chatwoot or both.
- We record which paid modules or Chatwoot plan features your workflows need, so license costs are explicit in the written scope.
- Engagements are fixed-scope: deliverables, timelines and exclusions for the Front migration are agreed in writing first.
How we build
- We size servers and PostgreSQL, Redis or MySQL and MariaDB components against your conversation volume and mailbox count.
- We configure SMTP, IMAP and OAuth for Microsoft 365 or Google Workspace mailboxes and test outbound deliverability before cutover.
- We test migrated conversations, attachments, users and permissions in a staging instance before any production switch.
How we hand over
- We document the architecture, installation steps, mailbox configuration, backup procedure and per-component cost ownership for your team.
- We deliver runbooks for agent onboarding, module updates and rollback, so your staff can operate the help desk without us.
- We provide a handover session covering the Front export scope, retained records and any items left out of the migration.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after the fixed-scope handover.
- We can apply FreeScout and Chatwoot releases in a staging environment before they reach production, on the schedule you agree.
- Ask us to confirm the scope, exclusions and retainer terms in writing before any work begins.
