This page is for people who use or are evaluating Mautic and collect leads to pass on to lenders, insurers, energy suppliers or telecom operators. That is where Markmatix comes from: our first publisher will use it to replace Mautic, one function at a time. The two products do not do the same job, though, and for many uses Mautic remains the right choice.
What we say about Mautic comes from its documentation, website and code, with sources listed below. Everything about Markmatix is coming soon.
What Mautic is
Mautic is open source marketing automation software, released under the GNU GPL, version 3 or later. You install it on your own server, with your own database: the project's README recommends Composer for production installs and offers self-hosting "completely free, forever".
The 7.2 documentation covers contacts and companies, segments, campaigns with a visual builder, email, SMS, focus items, forms, landing pages, dynamic web content, points and stages to track engagement, and reports. Mautic is extended with plugins and has a REST API with OAuth2 or Basic authentication, plus webhooks sent in real time or queued.
It is a community project: the Mautic Council is elected by the General Assembly for three-year terms, and the trademark is held on the project's behalf by Open Source Collective, its fiscal host. On 3 November 2026 the latest release on GitHub is 7.2.2, published on 26 October 2026.
What Markmatix will be
Markmatix will be a subscription platform for publishers who earn from leads and affiliate programmes. At its centre is not the newsletter but the request, the lead itself: vertical fields, source, a snapshot of consent at collection, quality score, status, partner and revenue. The request is what gets passed on, paid for and reversed.
The differences, point by point
| Mautic | Markmatix Coming soon | |
|---|---|---|
| Purpose | Marketing automation: email, campaigns, segments, landing pages | Managing leads that are passed on to partners |
| Licence and hosting | Open source (GPL v3), on your server | Subscription, on servers in the European Union; no installation on customer servers |
| Consent | Contact fields, preference centre, "Do Not Contact" per channel | A record that is never edited: exact wording, fingerprint, version, date, IP address and page for every consent |
| Towards third parties | Webhooks and integration plugins | Delivery blocked to anyone consent does not cover, proof attached to the lead |
| Routing | Campaigns with conditions and actions | A cascade by vertical, area, score, caps and partner hours |
| Scoring | Points for interactions and behaviour | Data quality and authenticity, never creditworthiness |
| Measurement | Reports on campaigns, emails, forms and pages | Postbacks per network, revenue ledger, reconciliation |
| Segments | Kept current by a cron job | Computed when needed, with a snapshot of recipients at each send |
| Newsletters | Included: email to groups of contacts, with templates | Marketing email and newsletters as a paid plugin |
| API | REST with OAuth2 or Basic, webhooks | REST described in OpenAPI, signed webhooks, Mautic-compatible API in the "From Mautic" plugin |
Each Markmatix function has its own page: consent, quality, routing, revenue and postbacks.
When Mautic is the better choice
If your work is sending newsletters and building marketing automation for your own list, Mautic is made for it, with a visual builder for campaigns, emails and landing pages. Markmatix will not be: marketing email and newsletters will arrive as a paid plugin, and so will the visual email editor.
If you want open code that you can read, change and install wherever you like, Mautic is open source. Markmatix will be a subscription service, and installation on customer servers is outside the project.
If you do not want to pay for a licence, Mautic does not charge for one. Markmatix will have a subscription per publisher, in tiers of monthly leads, with plugins and AI usage billed separately.
If you want an ecosystem of extensions, Mautic has a plugin marketplace and community forums. No third-party code will run inside Markmatix: integrations will go through the API and webhooks. And if you pass no leads on, you will not need most of Markmatix.
Mautic and GDPR
Mautic's documentation describes several privacy tools: a setting that stops it storing full IP addresses, which the documentation says helps customers meet the GDPR; a preference centre for each contact; a "Do Not Contact" status per channel; and contact export to CSV and Excel. In forms, a consent tick box stores a value: the documentation gives the example of a GDPR checkbox whose label is the consent sentence, while the database stores "Yes" or "1".
Whether an installation meets the GDPR depends on how it is configured and used, for Mautic as for any tool, Markmatix included.
Markmatix will start from a different unit: the single consent. Every consent or withdrawal will be a new row, with purpose, exact wording and its fingerprint, version, date, IP address, page and form. Purposes will be kept apart: the publisher's own marketing, profiling, passing data on per recipient or per category, and open and click tracking. Withdrawals will reach the partners that received the lead on their own.
From Mautic to Markmatix
The "From Mautic" plugin will offer an API compatible with Mautic's and import contacts, consents and forms, so code that calls Mautic today will not have to be rewritten all at once. The move will follow the strangler fig pattern: one function at a time. At our first publisher the planned order is:
- Collection. The main form will write to Markmatix first and then to Mautic, so existing campaigns keep working.
- Postbacks. Network conversions will move to Markmatix without touching Mautic.
- Links in emails. Unsubscribe, web version and redirects, including emails Mautic has already sent.
- Other forms. Only the submission address will change, and Markmatix will answer in the format Mautic forms expect.
- Automations. Active campaigns will become versioned flows.
Mautic will be switched off after 30 days with no calls, with a full encrypted export kept in an archive. Live contacts and their consents will move across; the statistics history will stay in a read-only encrypted archive. For other publishers the plugin will remain as a migration path.
Sources
- Mautic on GitHub: README and licence
- Releases on GitHub and release policy
- mautic.org and governance
- Documentation 7.2: overview, cron jobs, settings, forms, contacts, preference centre
- Developer documentation: API authentication, webhooks
Updated 3 November 2026