What marketing automation really costs when you self-host Mautic
Mautic carries no licence fee for the software itself. The Mautic GitHub repository is licensed under GPL-3.0, and mautic.org states that the project has no paid edition of the software, offering the free self-hosted download alongside separately promoted managed and hosting services. That means the cost of a self-hosted build shifts to infrastructure, email sending, setup, CRM integration, migration and ongoing administration, while suites such as HubSpot Marketing Hub and Salesforce Account Engagement add recurring subscriptions priced by contacts or seats, and HubSpot also lists onboarding fees for its higher tiers. The comparison is therefore not a license line against a zero, but a set of recurring and one-time costs you pay to different people.
The total depends on four drivers: contact volume, send volume, the number of integrations and who operates the platform. Mautic's requirements page says it should not run on shared hosting and recommends a VPS or dedicated server, so server sizing follows contacts and campaign load. Cron jobs for segment updates, campaign triggers and broadcasts, plus a messenger consumer when email is queued, need capacity that grows with volume. Ask any partner to price each of these lines separately, including who pays for the sending service and who carries the monthly patch, minor and two-yearly major upgrades.
Before comparing totals, decide who will administer the platform after go-live. An internal team needs skills in PHP, database operations, mail deliverability and cron management. A partner quote should state what is one-time (installation, configuration, CRM connector work, data migration) and what recurs (hosting, sending, support, upgrades, testing). Build a three-year model with your actual contact counts, and compare it against the seat and contact tiers in the suite quote, including any onboarding fee and the cost of additional seats. Illustrative example: a team with few administrators and a modest contact base may find the recurring server and support cost small, while a team that must also run integrations and audits will see those costs grow.
Cost components across in-house, partner and SaaS delivery
This table compares the cost components of building Mautic in house, engaging an implementation partner and buying a commercial marketing suite. Read each row for who receives the payment and whether the cost is one-time or recurring. Mautic's software carries no license fee, so most of the spend sits in infrastructure, sending, setup and administration, which depends on your own environment.
| Cost component | In-house build | Implementation partner | Commercial SaaS suite |
|---|---|---|---|
| Servers and hosting | Your team or cloud provider is paid for VPS or dedicated servers, storage and backups, recurring. Cost depends on your own environment. | Usually billed to you as infrastructure at cost, recurring. Confirm whether the quote includes hosting or only the setup. | Included in the subscription, recurring. HubSpot Marketing Hub Professional is listed from $800 per month with 2,000 marketing contacts (HubSpot pricing page). |
| Email sending service | You pay a transactional or bulk email provider directly, recurring, priced by volume. | Same provider cost, passed through or billed separately. Ask who holds the sending account and its reputation. | Usually bundled, recurring, with sending limits tied to the contact tier. |
| Initial setup and configuration | Internal staff time for installation, cron jobs, email authentication and templates, one-time. | Fixed-scope project fee paid to the partner, one-time. Agree deliverables in writing before work starts. | Onboarding fees apply. HubSpot lists $3,000 for Professional and $7,000 for Enterprise (HubSpot pricing page), one-time. |
| CRM integration | Internal developer time for sync rules, field mapping and duplicate handling, one-time, with ongoing maintenance. | Partner project fee for integration build, one-time, plus support retainer if you want it, recurring. | Often included in the platform price or sold as an add-on. Confirm which CRM connectors are covered and at what tier. |
| Contact migration | Internal staff time for cleaning, consent mapping and import, one-time. | Project fee for mapping consent records and suppression lists, one-time. Ask how consent evidence is carried over. | Usually included in onboarding or charged as a service, one-time. Confirm import limits and who validates consent history. |
| Administration and upgrades | Ongoing internal staff time for patching, Mautic release upgrades and monitoring, recurring. | Optional retainer covering upgrades, backups and support, recurring. Confirm the upgrade cadence and responsibilities in writing. | Included in the subscription, recurring, but you pay through contact and seat growth. |
| Vendor subscription or seats | No Mautic license fee, since the software is free to download and self-host. Other tools in the stack still carry their own costs. | No software license fee for Mautic itself. Partner fees cover services, not a per-seat license. | Recurring fees per contact tier and per seat. HubSpot lists Professional core seats at $45 per month each (HubSpot pricing page), with 3 seats included in the base price. |
What HubSpot and Salesforce charge, and what their fees exclude
HubSpot publishes three paid tiers for Marketing Hub, and each tier's price depends on seats and marketing contacts. Starter starts at $7 per month per seat and includes 1,000 marketing contacts. Professional starts at $800 per month with 3 core seats and 2,000 marketing contacts. Enterprise starts at $3,600 per month with 5 core seats and 10,000 marketing contacts, according to HubSpot's Marketing Hub pricing page. The published terms also list a required onboarding fee of $3,000 for Professional and $7,000 for Enterprise, plus extra core seats at $45 per month (Professional) or $75 per month (Enterprise).
- Recurring subscription: The monthly fee is paid for the tier, the seats and the contact band. Growth in contacts moves you into a higher band, so the bill rises with list size even when the feature set does not change.
- One-time onboarding: The Professional and Enterprise onboarding fees are charged once at the start, before any campaign runs.
- Seat expansion: Each additional core seat adds a recurring charge, so a larger marketing and sales team increases the monthly figure directly.
- Excluded work: The subscription does not include migrating contacts from an existing system, building forms and landing pages, mapping data fields or writing sending rules. Your team or a partner pays for that labor separately.
- Integration and data work: Connecting HubSpot to your ERP, data warehouse or identity provider is outside the list price. Ask for the expected hours in writing.
Before comparing this to Mautic, ask HubSpot and any partner for a written statement of which features are included in each tier and what the contact count means for your database.
Salesforce sells its B2B marketing automation product as Account Engagement, formerly Pardot, in four editions. Salesforce lists Growth+ at $1,250, Plus+ at $2,750, Advanced+ at $4,400 and Premium+ at $15,000 per org per month, billed annually. Growth+, Plus+ and Advanced+ include 10,000 contacts, while Premium+ includes 75,000, according to Salesforce's Account Engagement pricing page. The per-org model means one price covers the org, but the sales-side Salesforce CRM licenses that Account Engagement depends on are a separate purchase.
- Annual commitment: The published price is per org per month and billed annually, so the commitment is multi-year in practice when you plan a budget.
- Contact inclusions: Contacts above the included count are a cost driver. Confirm the overage rate in your order form because it is not part of the published headline figure.
- CRM dependency: Account Engagement is designed to work with Salesforce CRM. The CRM licenses, the sync configuration and the admin roles are separate costs to size.
- Implementation and migration: Moving prospect history, custom fields, scoring rules and email templates from another system is project work, and the cost depends on the data quality you start with.
- Administration: Someone must own the org, the connectors, the sending domains and the reporting. Plan that role as a recurring internal or partner cost.
Before you compare Account Engagement to a self-hosted option, get the overage rate, the CRM license count and the implementation scope in writing from Salesforce or its partner.
Neither vendor's published price covers the work that makes marketing automation useful inside a regulated or multi-system organization. These costs appear in every option, including a self-hosted Mautic deployment, so they should be counted on both sides of the comparison. The published fees cover the software service only, and the rest of the budget is a matter of scope.
- Email sending: Both suites rely on sending infrastructure, and deliverability setup (SPF, DKIM and DMARC records, warm-up, bounce handling) is work you must plan for, whichever platform you use.
- Data migration: Contacts, consent history, suppression lists and campaign history have to be moved and checked. Consent records in particular should be reviewed before import.
- CRM and system integration: Sync rules, duplicate handling and field mapping are project work with recurring maintenance when the CRM changes.
- Compliance evidence: Retention of sent communications, consent records and access reviews require configuration and documentation that the subscription does not produce by itself.
- Internal staff time: Marketing operations, data and IT staff hours are a cost even when no invoice shows them.
Ask any partner to split their quote into one-time setup, recurring hosting and sending, and recurring administration so you can compare it fairly with the vendor figures.
What moves the cost up or down
Mautic's software is free, so the bill follows the work around it: how many contacts you hold, how much you send, how deeply it connects to your CRM, and how much compute the scheduled jobs need. Each driver below changes the server, setup and administration effort, and each one is worth pricing explicitly in a written scope.
Contact database size and growth
The size of the contact table drives database sizing, backup volume, segment query time and the hardware behind the VPS or dedicated server. Growth matters as much as the starting count, because a list that doubles in a year needs capacity planning, not a one-time sizing. Ask the partner how they model contact growth, how they plan database backups and restore tests, and what hosting tier they propose for your projected volume.
Send volume and mailbox provider work
Sending volume drives the cost of the outbound email service, the queue workers that deliver messages, and the ongoing work to keep sending domains authenticated and reputable with mailbox providers. Setup covers SPF, DKIM and DMARC records, bounce and complaint handling, and warm-up for new sending domains. Confirm who owns sender reputation after go-live and whether the quote includes monitoring of bounce and complaint rates.
CRM integration complexity
Each CRM connection adds field mapping, sync rules, duplicate handling and testing against real data, and the effort scales with the number of objects and fields that must agree. Mautic publishes HubSpot and Salesforce plugin documentation, but a plugin still needs configuration, a sync design and acceptance tests. Ask the partner to name every system of record, which direction each field syncs, and who signs off on the mapping before cutover.
Segments, campaigns and landing pages
The number of segments, multi-step campaigns, forms and landing pages sets the amount of build, testing and content administration work. Every campaign trigger and segment rebuild adds load to the scheduled jobs, so a larger catalog of automations also raises the compute needed. Scope these as counted items in the statement of work, and agree who writes the content and who maintains it after handover.
Cron and queue capacity
Mautic relies on cron jobs for segment updates, campaign updates and campaign triggers, and the project documentation says these should be staggered. Queued email also needs a messenger consumer running in the background, and broadcasts need their own command. More contacts and more automations mean longer job runs, so capacity planning and monitoring become a recurring cost. Ask how the partner sizes the host, sets job schedules and alerts on stalled workers.
Chosen release line and support window
The release line you standardize on sets how long you can run without a forced upgrade and how much upgrade work falls due. Mautic 7.2 receives security support until 30 September 2026, while Mautic 7.3 is planned as the long-term support release with security support through 31 December 2027. Choosing the LTS line lowers the frequency of major upgrades, but each upgrade still needs testing against your integrations, and PHP and database requirements must be checked at each step.
Why hosting, cron jobs and upgrade cadence are recurring costs
Hosting, scheduled jobs and upgrades are the costs of a self-hosted Mautic platform that keep arriving after launch, and they are easy to undercount when the software itself is free. The Mautic project states that it should not be installed on shared hosting and recommends a VPS or dedicated server instead. Ask your partner to price a server sized for your contact volume, with separate database and mail-related capacity, and to show which hosting account type they assume. Confirm who holds the server contract, who patches the operating system, and whether backups and monitoring sit inside the monthly figure.
Mautic also depends on cron jobs. Segment updates, campaign updates and campaign triggers run on schedule, the project advises staggering them, and a broadcasts command handles segment emails. If email is queued, a messenger consumer must run continuously. Each of these is a process someone must keep alive, monitor and fix when a job fails silently, so the operations hours belong in the recurring budget. Ask how job failures alert the team and how queue backlogs are measured before sign-off.
Upgrades are the largest recurring item. The project's stated cadence is monthly patch releases, minor releases every three months and major releases every two years, so the platform needs planned maintenance windows throughout the year. Mautic 7.2 receives active and security support only until 30 September 2026, while Mautic 7.3 is planned as the long-term support release with security support through 31 December 2027. Confirm which release you will run, since choosing 7.3 aligns with a longer support window, and ask your partner to quote the upgrade work for each cycle, including testing of campaigns and integrations. Review the Mautic releases page before you fix the version.
How to build your own marketing automation cost estimate
This sequence turns contact counts, send volume and integration needs into a three-year cost comparison that you can set against a suite's contact tiers and onboarding fees.
Count contacts and monthly send volume
Marketing lead counts the contacts you expect to store today and the number you expect in three years, then estimates how many emails each segment receives per month. Separate marketing contacts from customers and prospects who only receive transactional messages, because suite pricing and sending volume are often counted differently. The output is a short table of contacts by year and monthly sends by program, which every later cost line depends on.
List required integrations and access controls
Marketing operations and the IT architect list every system that must exchange data with Mautic, including the CRM, web forms and landing pages, the customer data store and single sign-on for staff. For each integration, record the direction of data flow, the trigger and the owner of the field mapping. The output is an integration register that shows which connectors are built, which are configured from existing plugins and which need custom development, since custom work is usually the largest variable in setup effort.
Decide who builds setup and migration
Leadership decides whether your own team, an implementation partner or a mix of both will install Mautic, configure sending, build the first campaigns and migrate contacts and history from the current tool. Each option carries different one-time costs and different skills to keep in-house after go-live. Ask the partner to separate fixed-scope setup from any later retainer. The output is a written split of responsibilities that names who performs each task and who signs off on it.
Price hosting and the sending service from vendor quotes
Infrastructure or procurement obtains written quotes for the server or cloud environment that will run Mautic, the database, backups and the sending service that delivers the email. Mautic is free to download, but the project states it should not run on shared hosting and recommends a VPS or dedicated server, so the server line is a real recurring cost. Confirm the sending service's pricing by contact count or volume and check how it handles bounces and complaints. The output is a monthly infrastructure and sending figure sourced from named vendors.
Budget administration with a named owner
The business sponsor names one platform owner and, where needed, a backup, then estimates the monthly hours that owner needs for cron monitoring, segment and campaign maintenance, user access, deliverability checks and reporting. Some organizations add an operations or security support retainer for patching and incident response. The output is a recurring administration line in hours per month, plus a note on who covers absences, so the estimate does not depend on one person's availability.
Plan the upgrade window and support horizon
The platform owner reads the Mautic release calendar and maps each planned upgrade to a test cycle, a change window and a rollback plan. Mautic publishes monthly patch releases, minor releases every three months and major releases every two years, and older versions move out of security support on published dates. The output is an upgrade calendar for the three-year horizon, with the partner or staff effort for each cycle recorded as its own line in the estimate.
Write the partner quote and compare three years
Ask each partner to state, in writing, the fixed-scope setup and migration deliverables, the integration list, the hosting assumptions, the administration hours, the upgrade effort and the support terms. Then place your own totals beside a suite's list prices across the same contact tiers, adding the suite's onboarding fees and additional seats for each year. Publicly listed HubSpot Marketing Hub pricing, for example, includes required onboarding fees of $3,000 for Professional and $7,000 for Enterprise, so those fees belong in year one. The output is a three-year comparison table with one-time and recurring lines for each option.
Questions buyers ask before hiring outside help
How much does self-hosted Mautic cost compared with HubSpot or Salesforce?
Self-hosted Mautic has no software license fee, so its cost is the infrastructure, the email sending service, setup, CRM integration, migration and ongoing administration. HubSpot's published Marketing Hub pricing starts at $7 per month per seat for Starter with 1,000 marketing contacts, and lists $800 per month for Professional and $3,600 per month for Enterprise, plus required onboarding fees of $3,000 for Professional and $7,000 for Enterprise. Salesforce lists Account Engagement editions from $1,250 to $15,000 per org per month billed annually. These are list prices that scale with contacts and seats, so compare them with a written estimate for your own contact volume and send frequency, using your own quotes for hosting, sending and services.
Is there a license fee for Mautic itself?
No. Mautic is licensed under GPL-3.0 and the project offers a free self-hosted download, so you do not pay the project for the software. The paid items are the services around it: a partner to plan and build the environment, a dedicated sending service, hosting, support contracts or managed hosting if you choose it. Confirm the license terms of any plugin or connector you plan to use, since third-party extensions may carry their own terms.
How long do setup and migration take, and what drives the timeline?
Duration depends mainly on the number of contacts to migrate, how many CRM and data sources must sync, how much consent history must be carried over, and how many campaigns and forms are rebuilt. Email sending setup, including SPF, DKIM and DMARC records and warm-up, often runs on a separate track that your domain and mail team must approve. Ask any provider for a written timeline with milestones tied to these inputs, and ask which items depend on your own teams, such as DNS changes or CRM admin access.
Can our team run Mautic without an outside partner?
Yes, many teams do, provided they staff the work. Running Mautic is a continuing job: the platform needs its PHP and database stack kept within supported versions, cron jobs and queue workers running reliably, security and patch releases applied, and a named owner for consent, suppression and deliverability. The project says Mautic should not be installed on shared hosting and recommends a VPS or dedicated server. Ask yourself whether you have in-house staff for systems administration, email deliverability and marketing operations, and whether they can cover the release calendar.
What do marketing, IT and the CRM owner each need to provide?
Marketing owns the segments, campaigns, templates, consent wording and the approval rules for each send. IT or platform engineering owns hosting, network access, backups, identity, monitoring and the cron and queue setup. The CRM owner must define the field mapping, the record of truth for each contact and the rules for duplicates and sync direction. Agree these roles in writing before work starts, because most delays come from unclear decisions rather than from the software itself.
What should a fixed-scope quote for Mautic include?
A fixed-scope quote should list the environment (hosting, database, mail routes), the number of contacts and sending domains in scope, the integrations and their direction of sync, the migration sources and volume, the consent and suppression approach, the cron and queue design, and the handover documentation. It should also name the deliverables, the acceptance criteria, what is excluded, who supplies access and approvals, and the support or upgrade arrangement after go-live. DeployOpen agrees scope, deliverables and timelines in writing before work starts, so ask any provider for the same level of detail.
What recurring costs should we expect after go-live with Mautic?
The recurring items are hosting, the email sending service volume, backups and monitoring, staff time for administration and deliverability checks, and any support or upgrade retainer. Mautic's stated cadence is monthly patch releases, minor releases every three months and major releases every two years, and each upgrade needs testing against your integrations. Ask for an upgrade plan that names the supported version window, since the project lists the end of security support dates for each release line.
How DeployOpen scopes and delivers a fixed-scope Mautic implementation
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted Mautic inside your own cloud account, data center or air-gapped network. Engagements are fixed-scope, so the cost components covered in this guide, from servers and sending service to CRM integration and migration, are agreed in writing before any work begins.
How we scope
- We list which costs are in the written scope: hosting, sending service setup, CRM integration, contact migration and handover.
- We document contact volumes, sending domains, CRM objects and cron capacity so the quote follows from known inputs.
- We state which costs remain with you, such as the sending service subscription and your internal administration time.
How we build
- We install Mautic on a VPS or dedicated server, not shared hosting, following the project's published requirements.
- We configure cron jobs, the broadcast command and the messenger consumer so scheduled sends run on time.
- We test the CRM sync and deliverability settings against the scope before any campaign goes live.
How we hand over
- We document the architecture, server sizing, cron schedule and sending configuration so your team can run it.
- We deliver an administration guide that explains how upgrades between Mautic release lines are planned and tested.
- We train your administrators on contact import, segments, campaigns and consent records as defined in the scope.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover.
- A retainer can cover moving between Mautic release lines before each security support end date.
- We confirm with you, in writing, which monthly, quarterly or long-term release line the retainer covers.
