Where self-hosting Help Scout's replacement costs less, and where it costs more
A buyer weighing a Help Scout renewal or add-on increase should know that self-hosted FreeScout has no per-agent license fee for core use, and its paid modules are one-time lifetime licenses for a single instance. Chatwoot Community is also free to self-host, but its paid self-hosted plans start at $19 per agent per month for Premium Support, and the Enterprise Edition is $99 per agent per month, according to the Chatwoot self-hosted plans page. The savings depend on your agent count, hosting, email setup and migration effort. Per-agent pricing grows with headcount, so a team of five and a team of fifty face very different comparisons.
Hosting is where the self-hosted figure is easiest to underestimate. FreeScout runs on Nginx, Apache or IIS with PHP and MySQL, MariaDB or PostgreSQL, and its README says it has no minimum CPU or RAM requirements, but a shared inbox with many mailboxes still needs a server you can patch, back up and monitor. Chatwoot is heavier: it requires Ruby 3.2 or later, supports only PostgreSQL, and recommends Redis 7.0 or higher, with 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. Email is the other recurring item. Shared mailboxes depend on SMTP, IMAP or POP3, and Microsoft 365 and Google Workspace accounts use OAuth, so confirm your sending domain's SPF, DKIM and DMARC records before cutover. Staff time for upgrades and monitoring recurs too, and it belongs in your comparison.
The one-time costs sit at the start. Migrating conversations means exporting from Help Scout through its API within plan rate limits, then importing through FreeScout's migration service or an API import, re-creating mailboxes and saved replies, and buying any modules you need for parity, such as SAML SSO or Knowledge Base. Confirm the current lifetime price of each module and how many instances it covers on the FreeScout modules page. Before you accept a Help Scout renewal, ask for the per-user and add-on lines in writing, then build a multi-year total for each option using your agent count, hosting, email work and migration effort. Any implementation partner should provide a fixed-scope quote that lists those items separately.
Which cost components move on each side
This table lists each cost component of a move from Help Scout to self-hosted FreeScout or Chatwoot, who pays for it on each side, and whether it is one-time or recurring. Help Scout prices are not included because none were supplied, so confirm them on your own order form before comparing. The main takeaway is that the software license is only one line, and hosting, deliverability, migration and internal skills usually decide the total.
| Cost component | Who pays on Help Scout | Who pays on self-hosted FreeScout or Chatwoot |
|---|---|---|
| Software subscription or license | Your organization, per user on Help Scout's plan, plus any add-ons you buy | FreeScout: none for the core, one-time per-instance fees for paid modules. Chatwoot Community: none. Chatwoot paid plans: per agent per month, recurring |
| Hosting and infrastructure | Included in the subscription | Your organization, for servers or a VM, storage, backups and monitoring. Recurring |
| Email deliverability | Help Scout handles sending infrastructure within its service | Your organization, for SMTP or IMAP setup, SPF, DKIM and DMARC records, and any relay service. Partly one-time, partly recurring |
| Implementation and configuration | Mostly internal staff time for mailboxes and saved replies | Internal staff or an implementation partner, for installation, mailboxes, modules and integrations. One-time, sized by the written scope |
| Migration of past conversations | Export effort through Help Scout's API within plan rate limits | Internal staff or a partner for extraction, import, attachment handling and validation. One-time |
| Security and compliance evidence | Largely covered by the vendor's own controls and documentation | Your organization, for hardening, access control, patching and evidence collection. Recurring |
| Support and upgrades | Included in the subscription at the tier you buy | Chatwoot paid support is per agent per month. FreeScout modules are lifetime updates. Otherwise your staff or a retainer covers upgrades. Recurring |
| Internal skills and on-call time | Minimal for administration | Your staff for PHP, Ruby, PostgreSQL or MySQL, Redis and mail operations. Recurring, and the largest hidden line |
How FreeScout and Chatwoot license their paid tiers
FreeScout is licensed under AGPL-3.0, and its core help desk, with unlimited agents, tickets and mailboxes, is free to self-host. Paid functionality arrives as modules. The official modules page sells lifetime licenses that cover a single FreeScout instance and include lifetime updates, so the cost is a one-time purchase per module rather than a recurring seat fee.
- Paid modules: LDAP Integration, SAML SSO, API and Webhooks, Knowledge Base, Satisfaction Ratings, Time Tracking and Workflows are sold as lifetime licenses.
- Free modules: The AI Integration and S3 Storage modules are listed as free on the modules page.
- Scope of a license: Each lifetime license covers one FreeScout instance, so a second instance, such as a staging copy, needs its own license.
- Updates: The modules page describes lifetime updates, which should be confirmed against the current license terms before purchase.
- Vendor relationship: Modules are bought from FreeScout's vendor, so the team should confirm invoicing, tax handling and what support, if any, comes with each module.
Before you budget, list every module your support, identity and reporting requirements depend on, then confirm the current price and license terms on the modules page.
Chatwoot's Community Edition is listed at $0 and free forever on its self-hosted plans page. The source is MIT Expat licensed, except content in the enterprise/ directory, which falls under a separate license, and third-party components keep their own licenses. A team that runs Community Edition pays no per-seat software fee, but it carries all infrastructure, operations and upgrade work itself.
- Included in Community: The omnichannel inbox, Help Center portal, automation, teams, labels, canned responses, campaigns and reports are part of the open core, according to the README.
- Infrastructure: Hosting requires PostgreSQL, Redis 7.0 or higher, Ruby 3.2 or later and Node.js 20.x, so you pay for servers or cloud resources and the staff to run them.
- Support: Community use relies on the public documentation and community channels rather than a contracted support commitment.
- Sizing: Chatwoot's requirements page recommends 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, which drives the compute line of the budget.
- Licensing check: Confirm that any feature you plan to use sits outside the enterprise/ directory before assuming it is MIT Expat licensed.
Check the LICENSE file and the requirements page against the version you plan to deploy.
Chatwoot sells two paid self-hosted tiers priced per agent. Premium Support is listed at $19 per agent per month and adds Captain AI, voice calls, custom branding, agent capacity, roles and permissions, and priority support. The Enterprise Edition is listed at $99 per agent per month and adds SSO with SAML and SLA policies. Both prices recur and scale with the number of agents, so the total depends on headcount.
- Premium Support at $19: Adds Captain AI, voice calls, custom branding, agent capacity, roles and permissions and priority support, according to the plans page.
- Enterprise at $99: Adds SSO with SAML and SLA policies, according to the plans page.
- Recurring cost: Both tiers are billed per agent per month, so adding agents raises the monthly total in direct proportion.
- Captain AI: Captain is an AI agent that automates responses to common queries, and access to it begins at the Premium Support tier.
- Quote questions: Ask whether the agent count is based on named or concurrent users, how changes mid-term are billed and what SLA terms the Enterprise tier includes.
Confirm the current per-agent prices on the self-hosted plans page, since the figures here come from the plans page at the time of research.
What moves the Help Scout comparison most
Six variables decide whether self-hosting FreeScout or Chatwoot costs less than staying on Help Scout. Several of them, such as seat counts and SSO needs, change the arithmetic more than the license price does, so model them before comparing totals.
Agent count and seat pricing
Help Scout and Chatwoot both price some tiers per agent, while FreeScout's base product has no per-agent fee. Count named agents, occasional users and contractors separately, because a per-agent quote scales with each one. Ask Help Scout how it counts users on your plan, and check whether Chatwoot's per-agent tiers apply to every agent you need in the inbox. Illustrative: a team of 12 agents on a per-seat plan pays for all 12 every month, while a self-hosted base install does not add a line per agent.
Mailboxes and channels in use
FreeScout's README lists unlimited agents, tickets and mailboxes, so mailbox count does not change its license cost. Chatwoot's extra channels, including live chat, WhatsApp, Facebook and Instagram, add integration work and third-party account fees. List every mailbox, widget and social account you run today, then confirm which channels each platform supports on your plan before you assume parity.
Conversation volume and server sizing
Chatwoot's requirements guidance recommends at least 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. Pull your daily conversation counts from Help Scout reporting before you size a VM. Sizing drives the recurring cloud or hardware bill, so a higher volume tier moves the hosting line more than any license fee.
SSO and compliance controls
SAML SSO and LDAP are paid FreeScout modules sold as lifetime licenses for a single instance. Chatwoot places SSO with SAML and SLA policies in its Enterprise Edition at a per-agent price. Help Scout gates HIPAA and some security features to higher plans or add-ons. Write down which of these controls your auditors or security team require, because they often determine whether the self-hosted option needs a paid tier at all.
Internal skills for the stack
Chatwoot needs Ruby 3.2 or later, Node.js 20.x, PostgreSQL only, and Redis 7.0 or higher. FreeScout runs on PHP 7.4 to 8.x with MySQL, MariaDB or PostgreSQL. Ask who on your team can patch Ruby or PHP runtimes, tune PostgreSQL backups and operate Redis. If nobody can, the cost of an implementation partner or a managed retainer belongs in the comparison, and it recurs for as long as you run the platform.
Email deliverability and migration effort
Self-hosting moves outbound mail onto your domain, SPF, DKIM and DMARC records, and your SMTP provider's fees. Help Scout handles this for you today. Budget time to verify sending reputation before cutover, and plan the one-time migration of past conversations, attachments and customers from the Help Scout Inbox API. Ask any implementation partner for a written scope that names both the deliverability checks and the migration steps.
How to build the cost model with your own numbers
This sequence turns a Help Scout renewal into a three-year cost model with your own seat counts, hosting rates and written quotes, so the comparison with self-hosted FreeScout or Chatwoot rests on your figures rather than list prices.
Export current Help Scout seats and add-ons
Pull the current Help Scout invoice and plan details from the account owner or finance team. Record the number of billable users, the plan tier, and every add-on line, such as extra mailboxes, workflow or reporting features, and any HIPAA or security options. Confirm the plan terms, included features and renewal dates directly with Help Scout, because pricing and packaging can change. You are done when every recurring line has a source document and a named owner.
List mailboxes, channels and integrations
Inventory every shared inbox, email alias, live chat widget, social channel and connected tool that feeds or reads from Help Scout. Include the knowledge base, saved replies and any API or webhook integrations, since each one either needs a module, a connector or a rebuild on the target platform. Note which items are used daily and which are legacy. You are done when you have a table of mailboxes and channels with an owner and a required feature for each.
Choose the target edition and module set
Map the inventory to a target. For FreeScout, check which lifetime modules cover your needs, such as SAML SSO, LDAP, knowledge base, API and webhooks, and confirm them against the official modules page. For Chatwoot, compare the Community Edition with the paid self-hosted plans and check which features, such as SSO with SAML or SLA policies, sit in each tier. Record the chosen edition and every paid module or plan as a line item. You are done when the target configuration is written down and each feature gap has a decision.
Price hosting from your own rates
Estimate the server footprint from the platform's published requirements, then price it with your own cloud account or data center rates. For Chatwoot, the requirements page sets out CPU, RAM and swap guidance by conversation volume, along with PostgreSQL and Redis. For FreeScout, confirm the PHP, database and web server stack and any backup storage. Include staging, backups and monitoring, which recur. Ask your infrastructure team to confirm the rates and the internal labor for patching and upgrades. You are done when the hosting line has a monthly figure from your own price sheet, with its assumptions listed.
Quote email delivery and migration as written work
Request written quotes for outbound and inbound email setup, including SPF, DKIM and DMARC records, mailbox connections and deliverability testing, and for migrating past conversations, threads, attachments and customers. Ask each provider or your internal team to state the scope, the data volume assumptions and the deliverables. Keep one-time and recurring items separate, and ask whether any transactional email service is a monthly cost. You are done when each migration and deliverability item has a quote with a defined scope.
Build the three-year view
Create a spreadsheet with one row per cost line and three yearly columns. Mark each line as one-time (setup, migration, module licenses, deliverability work) or recurring (seats or plan fees, hosting, support contracts, maintenance time). Run the Help Scout line on the same three-year timeline using the seat and add-on counts from the first step, and add any planned seat growth as a separate scenario. Label the sheet's assumptions clearly. You are done when both options show a total for each year and the one-time and recurring subtotals are visible.
Review the model with decision owners
Walk the finance, support leadership, security and infrastructure owners through the model. Check that the seat counts match the invoice, the hosting rate matches the infrastructure team's price sheet, and every migration or email item has a written quote behind it. Record the sensitivities that move the result most, such as seat growth, plan tier changes and hosting rates. You are done when each owner has signed off on their lines and the open questions are assigned to named people.
Why email deliverability and hosting need their own line
A self-hosted shared inbox is only as good as its mail flow, and that flow is a line item you will own. FreeScout pulls and sends mail over SMTP, IMAP or POP3, or authenticates through OAuth for Microsoft 365 and Google Workspace. Your team must configure the sending domain's SPF, DKIM and DMARC records, keep the OAuth application registrations current, and watch bounce and authentication reports after go-live. Help Scout handles this for you today, so the time spent on it after migration is new labor, not a hidden fee. Confirm with your mail provider the current sending, rate and connection limits for the accounts that will back each mailbox, because these vary by plan and tenant and can change.
Hosting costs follow the chosen product. FreeScout runs on Nginx, Apache or IIS with PHP and MySQL, MariaDB or PostgreSQL, and its README describes no minimum CPU or RAM, so a small deployment can start on modest hardware. FreeScout also offers a Docker image and one-click installs through Softaculous and Cloudron, which shorten setup but still leave backups, patching and certificate renewal with your team. Chatwoot is heavier: it requires Ruby 3.2 or later, supports only PostgreSQL, recommends Redis 7.0 or higher, and lists Ubuntu 20.04 as its only officially supported Linux distribution. Confirm with your platform team whether that distribution is still acceptable under your own support policy before you size the server, and budget for the swap and memory headroom Chatwoot's requirements page recommends.
What migrating past conversations adds to the bill
Moving past conversations is usually the largest one-time cost in this move, larger than the software itself. Every conversation, thread, attachment and customer record has to leave Help Scout and land in FreeScout or Chatwoot with its history intact. Two routes exist. The first is pulling data through the Help Scout Inbox API 2.0, which is subject to the rate limits of your Help Scout plan, so a large archive can take many days of throttled requests before any import starts. The second is FreeScout's migration service, which the FreeScout README links as a way to move data from other help desks. Either route needs someone to write or run the extraction, map Help Scout fields to FreeScout or Chatwoot fields, and check the result.
The effort scales with history volume and attachment size. Ten years of threads with large PDFs and images costs far more to move than a few months of short email exchanges, and attachments usually dominate storage and transfer time. Ask whether the scope covers attachments, customer merges, mailbox mapping, saved replies and the threads themselves, and whether the migration is run once or in passes. Also confirm how the target handles a customer who appears under two email addresses, because duplicate records are the most common reason support teams review imported history by hand.
Request a written scope before you commit to a date or a budget. The scope should name the source data sets, the target instance, the test import you will review, the cutover window, and what happens to conversations that arrive during cutover. Ask who holds the Help Scout API credentials during the work and when they are revoked. A quote that lists only the software licenses and not the extraction, mapping and verification work leaves the largest cost unpriced.
Questions buyers ask before comparing Help Scout costs
How much effort does self-hosting FreeScout or Chatwoot take?
The effort depends on the platform and on the skills already in your team. FreeScout runs on Nginx, Apache or IIS with PHP 7.4 to 8.x and MySQL, MariaDB or PostgreSQL, and its README states there are no minimum CPU or RAM requirements, although production sizing still matters. Chatwoot needs Ruby 3.2 or later, Node.js 20.x, PostgreSQL as its only database and Redis 7.0 or higher. Its requirements page recommends at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day. Ongoing work includes patching, backups, mail configuration, monitoring and upgrades. Ask for sizing based on your own conversation volume and agent count.
Can our team run a self-hosted help desk without outside help?
Many teams can, provided they already operate Linux servers, a web tier, a database, mail routing and backups. Teams without that depth usually need help with the initial build, hardening, backup testing and runbooks. Chatwoot documents installation on a Linux VM with an install script, Docker, and Kubernetes with a Helm chart for larger high-availability deployments. DeployOpen plans, implements, customizes, hardens, backs up, upgrades and documents self-hosted platforms inside your own cloud accounts, data centers or air-gapped networks. Most engagements are fixed-scope, with scope and deliverables agreed in writing before work starts, and ongoing support is available as a retainer. Confirm your internal capacity before you choose an operating model.
How long does migrating Help Scout conversations take, and what does it need?
No migration duration has been established for this comparison, so confirm timing in a written, fixed-scope plan. The main drivers are the number of conversations, threads and attachments, the number of mailboxes, saved replies, customer records and the modules you need at go-live. On the Help Scout side, you need an account with API access and a way to pull data within its plan rate limits. The migration also needs a cutover window for changing mail routing, a decision on how open conversations move, and staff time to check threads and attachments after import. The FreeScout README links a migration service, and the sibling migration page covers the API route in more detail.
Are FreeScout modules a one-time cost?
FreeScout's modules page sells lifetime licenses for a single FreeScout instance, with lifetime updates, so the module fee is generally one-time per instance and per module. Modules listed 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. Because licenses are tied to a single instance, check whether staging, test or additional instances need their own licenses. Recurring costs still apply to hosting, email services, storage, backups, staff time and any support retainer. Confirm current module prices and license terms on the FreeScout modules page before you build a budget.
How much do Chatwoot's paid self-hosted plans cost per agent?
Chatwoot's self-hosted plans page lists the Community Edition at $0, free forever. Premium Support is listed at $19 per agent per month and adds Captain AI, voice calls, custom branding, agent capacity, roles and permissions, and priority support. The Enterprise Edition is listed at $99 per agent per month and adds SSO with SAML and SLA policies. These are recurring charges that scale with the number of agents, so the total depends on how many seats you need on each tier. As an illustrative example only, 20 agents on Premium Support would be 20 multiplied by $19, or $380 per month, before hosting. Check the Chatwoot self-hosted plans page for current terms.
What hosting and email costs should we plan for?
Hosting cost is driven by server size, database and Redis capacity, storage growth, backup retention and the number of environments you run. Chatwoot recommends at least 8 cores and 8 GB of RAM for up to 20,000 conversations a day, plus at least 1 GB of swap, and notes that Sidekiq can use more than 1 GB of memory on a very active server. Email deliverability is often the hidden task. You will need correct SPF, DKIM and DMARC records, a sending path that your provider trusts, and a plan for bounces and spam complaints. FreeScout supports SMTP, IMAP and POP3, along with OAuth for Microsoft 365 and Google Workspace. Ask any quote to price hosting, email relay and monitoring as separate line items.
What should a self-hosting quote include before we compare it with Help Scout?
A useful quote starts from a written scope. It should list the hosting environment, the number of agents, mailboxes and expected conversation volume, the migration scope and the data sources, the modules or add-ons, the testing and handover steps, and the support you need after go-live. It should separate one-time costs, such as setup, migration and module licenses, from recurring costs, such as hosting, email relay, Chatwoot seats if you choose that route, and a support retainer. Ask for assumptions, exclusions and a change-control process, since these set the real boundaries of the work. DeployOpen does not publish a price list. A quote follows from the written scope, so compare offers on the same scope and timeline.
How DeployOpen scopes a fixed-price comparison and implementation
DeployOpen plans, implements and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For Help Scout cost vs self-hosted FreeScout and Chatwoot, we start with a written scope that prices the real cost components, so the comparison and any migration are agreed before work begins.
How we scope
- We inventory your current Help Scout plan, add-ons, mailboxes, agent count and channels before comparing costs.
- We model hosting, email deliverability, backups and migration effort as separate line items in the written scope.
- We confirm which FreeScout modules or Chatwoot plan tiers your required features depend on, with the vendor.
How we build
- We install FreeScout or Chatwoot in your environment and configure SMTP, IMAP or OAuth mailboxes for your domains.
- We test inbound and outbound mail delivery, SPF, DKIM and DMARC alignment, and notification routing before cutover.
- We run a trial migration of a sample of past conversations and attachments to check fidelity before the full move.
How we hand over
- We document the architecture, sizing, backup and restore steps, and the configuration of each mailbox and module.
- We deliver a cutover runbook covering DNS changes, forwarding from the old Help Scout addresses and rollback steps.
- We train your support leads on administration, agent roles and the day-to-day tasks your team will own.
How we support
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- Ongoing support, upgrades and patching of the help desk stack are available as a retainer.
- Ask any provider, including us, to show the license terms and per-agent or per-module fees in the quote.
