Marketo vs Mautic cost comes up the moment a Marketo renewal quote lands. For a database of about 100,000 contacts, a year of Mautic with hosting, Amazon SES sending, a dedicated IP and a care plan with consulting hours costs roughly 80 percent less than typical Marketo pricing. Public benchmarks put the gap at 80 to 90 percent. Here is how the math works.
Where does the 80 percent come from?
We compared two things for the same database size. On one side, the negotiated Marketo price that independent benchmarks report for up to 100,000 records. On the other, a full year of running Mautic the way we run it for clients: an EU server, Amazon SES for sending, a dedicated IP address and a monthly care plan that includes consulting hours for the marketing team.
The Mautic year comes out at about a fifth of the low end of the Marketo range. Against the high end, it is closer to a tenth. That is where “80 to 90 percent cheaper” comes from.
Two caveats. Adobe does not publish Marketo prices, so every Marketo number below is a third-party estimate, and your contract may differ. And the comparison covers running costs. The one-off migration comes on top, and we cover it separately below.
This is the same setup we run for a German B2B distributor we moved from Marketo to Mautic, with about 95,000 contacts, a weekly newsletter, shop automations and a CRM integration. So the configuration is real. The Marketo side comes from benchmarks, not from one client’s invoice.
How does Marketo price its licence?
Every Marketo contract is a quote. The structure behind the quote is public, though, and it explains why costs climb.
Per 1,000 contacts
Adobe’s Marketo Engage product description lists every package (Select, Prime, Ultimate and their Performance variants) with the licence metric “Per 1,000 Contacts”. You do not pay per user or per email. You pay for the size of the database.
What counts as a contact
The same document defines a contact as any person record “for whom Customer has a point of contact”, which covers email, a social profile or a postal address. It also states that the customer is responsible for keeping the number of contacts below the amount in the sales order.
Whether unsubscribed, bounced or inactive records count depends on your contract wording. Stackcut reports that Marketo bills on total database records, inactive ones included. VendorBenchmark says unsubscribed and test contacts are typically excluded, but warns that teams with old databases often find their billable count much higher than their mailable list. Read your own contract before you trust either view.
Packages and entitlements
The package decides what is included. According to Adobe’s product description, Select has no sandbox, no lifecycle modeler and no workspaces. Prime adds a sandbox. Only Ultimate includes Marketo Measure attribution. Each instance comes with 50,000 API calls per day and 25 marketing users.
Adobe calls these limits entitlements and states that if you exceed one, you “may be obligated to pay additional fees or license additional capacity”.
Annual true-up
VendorBenchmark describes an annual true-up: if your database grows past the contracted tier during the year, the overage arrives as one invoice at the annual review. It also reports standard annual price increases of 5 to 7 percent and a typical renewal notice period of 90 days.
Which Marketo add-ons and side costs add up?
The licence is the start of the bill. Adobe’s product description lists more than 25 add-ons. The ones mid-sized B2B teams meet most often:
- Sandbox (priced per 1,000 contacts, not included in Select)
- Predictive Content, Website Personalization, Website Retargeting (per 1,000 contacts)
- Marketo Measure attribution (separate licence below Ultimate)
- Sales Insight for the CRM side (per pack of 5 users)
- Additional API Calls (per pack of 10,000)
- Dedicated IP Addresses (per IP)
- Additional landing page and tracking link domains (per domain)
- Deliverability packages (per 1,000 contacts)
The dedicated IP needs a closer look. Adobe’s terms say a standalone purchase of dedicated IPs requires a coterminous Deliverability Enhanced or Deliverability Plus package unless Adobe agrees otherwise. So one IP address can pull in a second contract line.
VendorBenchmark puts typical yearly add-on costs at $15,000 to $45,000 for Sales Insight and $20,000 to $60,000 for Web Personalization. It also notes that Web Personalization is often bought and then used on only one or two pages.
Then come the people. Stackcut reports a median US salary of about $85,000 for a dedicated Marketo administrator, and $15,000 to $50,000 for a partner implementation. Not every team hires a full-time admin. Most pay someone, in house or at an agency, to keep Marketo running.
What do you pay for when you run Mautic?
Mautic is open source. There is no licence and no price per contact. You pay for five things.
Hosting
A server sized to the database. For 100,000 contacts, a virtual server with 4 vCPUs and 16 GB of RAM in an EU data center handles the load, including segment rebuilds and campaign processing. Growth in the database changes the server size, not a licence tier.
Sending
Mautic hands email to a sending service. We use Amazon SES. The AWS SES pricing page lists à la carte outbound email at $0.10 per 1,000 emails. New accounts start on the Essentials plan at $0.16 per 1,000 emails for the first 10 million per month. Four sends a month to 100,000 contacts means about 400,000 emails, which costs well under $100 a month at either rate.
Dedicated IP
Optional below roughly 100,000 emails a month, recommended above it. AWS lists a standard dedicated IP at $24.95 per month. The managed option costs $15 per month per account plus $0.08 per 1,000 emails, and SES warms the IP up for you. Our post on Amazon SES and dedicated IP warm-up for Mautic covers the setup.
Care plan
Security updates, monitoring, backups, deliverability checks and monthly consulting hours. This is the largest line on the Mautic side. It replaces most of what a Marketo admin or agency does for the platform itself.
Migration (one-off)
Contacts with consent history, templates, forms, landing pages, automations and integrations. A standard migration on our public price list is scoped at about 40 hours. Accounts with many programs, a second brand or a custom integration, like the distributor in our example, take considerably longer, and we scope those after a paid discovery. Our guide on how to plan a Marketo to Mautic migration describes that audit.
Worked example: 100,000 contacts for one year
The table puts the cost lines side by side. Marketo figures are third-party estimates. Mautic lines are shown as a share of the total, because the split matters more than the exact sum.
| Cost line | Marketo, up to 100,000 contacts | Mautic, 100,000 contacts |
|---|---|---|
| Licence | $45,000 to $90,000 a year, negotiated (VendorBenchmark) | none |
| Add-ons | $15,000 to $60,000 each for common modules (VendorBenchmark) | none; missing features become plugins, paid once |
| Platform admin | in-house admin (~$85,000 median, Stackcut) or agency | consulting hours inside the care plan |
| Hosting | included | about 16 percent of the Mautic year |
| Sending | included within the send allowance | about 5 percent (Amazon SES) |
| Dedicated IP | add-on, may require a deliverability package | about 3 percent |
| Care plan | not applicable | about 75 percent |
| Running cost vs Marketo licence | 100 percent | about 20 percent of the low end, about 10 percent of the high end |
Against the Stackcut average contract of $112,544 a year (Vendr data across 117 deals), the Mautic year is under 10 percent.
The table leaves the Marketo admin out of the totals on purpose. If you pay one, the real gap is wider than 80 percent.
When does the migration pay back?
Take the low end of the Marketo range. Mautic saves about 80 percent of that licence every year, so each quarter returns about a fifth of the licence value. A standard 40-hour migration costs less than half of one quarter’s savings. It pays back within the first months.
Larger migrations shift that point by weeks, not years. The deadline matters more than the payback: if the Marketo contract renews before Mautic goes live, you pay another year of licence.
What changes at 250,000 and 500,000 contacts?
Here the two models split hard.
Marketo moves up a tier. VendorBenchmark reports these negotiated ranges:
| Database size | Typical Marketo edition | Negotiated yearly cost |
|---|---|---|
| Up to 100,000 | Growth / Select | $45,000 to $90,000 |
| 100,000 to 250,000 | Select / Prime | $85,000 to $175,000 |
| 250,000 to 500,000 | Prime | $150,000 to $280,000, plus $20,000 to $60,000 for add-ons |
Mautic moves up a server. A database of 100,000 to 300,000 contacts runs on 8 vCPUs and 32 GB of RAM. Up to 500,000, we use 16 vCPUs and 64 GB. Sending grows in line with the emails you send, at the same price per 1,000. The care plan stays the same unless you add custom plugins and integrations that need more hours.
In our calculations the gap widens with size. With the same care plan, Mautic costs 85 to 95 percent less than the Marketo range at 250,000 and 500,000 contacts. At 500,000 contacts, even a larger care plan for a heavily customized setup keeps the saving above 80 percent.
One more effect. On Marketo, growing the database raises the licence, so marketing success shows up as a cost. On Mautic, it shows up as a bigger server.
Which hidden costs sit on each side?
Both platforms have costs that do not appear on the first quote.
On the Marketo side
- True-up invoices when the database passes the contracted tier.
- Database definition. Old records you never email can still be billable, depending on the contract.
- API limits. 50,000 calls a day is the default. Heavy CRM syncs or enrichment tools can hit it, and extra calls are sold in packs of 10,000.
- Price increases. VendorBenchmark reports 5 to 7 percent a year as standard. Stackcut reports that Adobe raised the entry package from $895 to $1,295 a month in 2025.
- Professional services. VendorBenchmark puts Adobe’s own rates at $200 to $350 an hour.
- Bundle pressure. Renewals often come with an upgrade offer to the next edition.
On the Mautic side
- Care is not optional. Someone has to apply security updates, watch the cron jobs and keep backups. Plan it from day one.
- Deliverability is yours. SPF, DKIM, DMARC, bounce and complaint handling and the IP warm-up need setup and monitoring. In Marketo, Adobe does part of this.
- Some features need building. Native Mautic covers newsletters, forms, landing pages, segments, campaigns and scoring. Some logic needs a small plugin. On a recent project we built a campaign condition that compares two date fields, which native Mautic cannot do.
- Team time. Your marketers will learn a new email builder and a new campaign editor. Plan a few training sessions.
- The cutover window. Run both systems in parallel until Mautic sends are validated. That overlap needs a few weeks of Marketo still under contract.
None of these come close to a licence line. They still belong in the comparison, because a cheap platform that nobody looks after gets expensive fast.
What do you give up, and what do you need to plan, with Mautic?
Price is the reason most teams look at Mautic. Check these before you decide.
Account-based marketing and predictive modules. If you use Marketo’s Target Account Management or Predictive Content daily, map each use case to Mautic first. Many teams pay for these modules and use them lightly. Some depend on them.
Attribution. Marketo Measure has no direct Mautic equivalent. Mautic tracks UTM tags, page visits and form submissions per contact, and you can send that data to your BI tool. Multi-touch revenue attribution needs a separate tool or a custom report.
Program membership. Marketo programs keep member status and program member fields. Mautic has no program membership. We plan event history differently, for example with a tag per event, and keep old program data in an archive export.
Engagement programs. Marketo streams with cadence become Mautic campaigns with conditions and waits. The logic carries over. The structure changes, so the rebuild needs a plan.
CRM integration. Mautic has plugins for common CRMs and a REST API for everything else. If your middleware team owns the integration, they will need API documentation and test calls. Budget their time too.
In return you get a platform you own. The database sits on a server you choose, in the EU if you want, with full export at any time. Missing features become plugins you keep. Our Marketo to Mautic migration guide shows how that rebuild looks in practice.
How to prepare a cost comparison for your own renewal
You can build a solid comparison in one afternoon. Gather these items:
- Your current Marketo invoice, every line item, not just the total.
- The contact definition in your contract and your current count. Check whether unsubscribed and bounced records are billable.
- Your database trend. Where will the count be at the next true-up?
- Add-ons you pay for, and for each one, who used it in the last three months.
- API usage. Daily calls from the Marketo admin console, against your entitlement.
- Admin cost. The share of an employee’s time or the agency hours spent on Marketo itself.
- Send volume. Emails per month, which sets the Amazon SES line and the dedicated IP decision.
- Integrations. CRM, ERP, shop, webhooks. Each one needs a plan in Mautic.
- The renewal notice date. Often 90 days before the contract ends.
- The contract end date. Plan the migration backwards from it.
With these numbers you will see your own percentage, not a benchmark. Teams with heavy add-on use usually land above 80 percent. Teams on a deeply discounted Adobe bundle may land a bit lower.
FAQ
Is Mautic really free? The software is. Running it is not. You pay for hosting, sending, care and the one-off migration. For 100,000 contacts that adds up to about 10 to 20 percent of a typical Marketo licence.
Does the 80 percent include the migration? No, it compares yearly running costs. A standard migration pays back within the first months of saved licence fees.
Can Mautic handle 100,000 contacts or more? Yes. A 100,000-contact database runs on a single mid-sized server. Larger databases move to bigger servers, and above a million contacts we use multiple instances with a managed database.
Do I need a dedicated IP with Mautic? Below roughly 100,000 emails a month, a shared SES pool works well. Above that, a dedicated IP gives you control over your own reputation. It costs about $25 a month at AWS.
How long does a migration take? A standard migration takes a few weeks. We moved a German B2B distributor with about 95,000 contacts and many automations in two months, before the Marketo contract ended.
Can I keep my Marketo data after leaving? Export everything before the contract ends: contacts, activity history you want to keep, email HTML and program data. Some items, such as smart campaign flow steps, are only visible in the Marketo UI, so the audit has to capture them early.
Want the same comparison for your Marketo contract?
We moved Meesenburg, a German building hardware distributor, from Marketo to Mautic before its contract ran out: about 95,000 contacts with consent history, the weekly newsletter, shop automations and the SAP integration. Mautic now runs on an EU server with Amazon SES and a care plan. Read the Marketo to Mautic migration case study.
Send us your database size, your add-ons and your contract end date. We will put a year of Mautic next to your Marketo invoice and estimate the migration. Talk to us about leaving Marketo.
Tags
Written by
Mautomic Team
Mautic experts sharing insights on marketing automation, custom development, and open-source technology.