Every month we publish an Open Startup Report showing where Mautic’s money comes from and where it goes, and I spend a fair bit of time with those numbers (probably more than is healthy!). What the monthly reports don’t do very well is show the bigger picture, so this year we’ve pulled January to June together into one place, our first H1 report.
You can download the Mautic H1 2026 report here, and I’d love it if you gave it a read. Here’s a flavour of what’s inside.
A tough start to the year
2026 started pretty tough. Income we’d planned for from memberships and an Extended Long Term Support licence didn’t arrive, and in January we put a hold on all non-essential spending. In that same month we shipped Mautic 7, the Columba Edition, which says a lot about the folks who keep this project going!
When we asked for help, you answered. In February 67 gifts came in to our community fundraiser, which meant we could settle three months of deferred invoices. Then in March TYPO3, the open source content management project, gave $10,000 through the fundraiser, arranged by Daniel Fau, making March our strongest fundraising month at $12,235. One open source project funding another is pretty rare, and I’m so grateful to Daniel and everyone at TYPO3 for standing beside us.
Let’s look at the numbers!
Between January and June we brought in $93,898 and spent $95,229, a gap of about $1,300. Spending ran a little ahead of income because by the end of June we’d caught up on every deferred payment. Our support came from
- $41,000+ from corporate members
- $26,070 given to our community fundraiser
- $11,058 in Mautic World Conference sponsorship
- $5,608 from monthly sponsors
- $3,614 from a new share of trials revenue with Dropsolid
- $2,644 from individual members
On the community side, 89 people made their first contribution to Mautic across code, documentation, translation, design and support, and 276 new community members joined us in Slack, the forums, GitHub and our other channels. There were 2,205 sign-ups for a Mautic trial too, with India, the United States and Brazil leading the way.
Two releases, and a third on the way
We shipped Mautic 7.0 on 20 January and Mautic 7.1, the Canis Major Edition, on 1 April. Between them they brought projects for organising campaigns, a new API built on API Platform, inline text editing in the email and page builders and bot detection that filters out more than 500 known bots, along with lots more. By June, 44% of the instances checking in with our updates server were running Mautic 7 (and that’s a floor, as the data undercounts!).
The release candidate for Mautic 7.2 went out for testing on 2 June, and the general release followed on 2 September. Also in June, Tomas Votruba, who created the Rector refactoring tool (it automates upgrading and tidying up PHP code), started volunteering his time to modernise our codebase. His work laid the foundations for the 322 refactoring pull requests that went into 7.2 – huge thanks, Tomas!
A big thank you as well to every organisation that gives its people time to contribute, especially Acquia, Leuchtfeuer Digital Marketing and Dropsolid, our three biggest contributing organisations in the first half of the year.
Getting together in Berlin
On 17 and 18 June around 20 contributors got together in Berlin for our community sprint, with lots more joining remotely. They closed open pull requests, chipped away at our PHPStan baseline (a long list of known code quality issues we’ve been carrying for a while), brainstormed ideas for Mautic 8 and talked about how we fund the project long term. Thank you to Sven Döring for getting VML to host us, to Ekke for organising it all and to Stephan Luckow for looking after the evenings! I couldn’t be there this time, but it was so lovely to see all the photos come through.
Next up is the Mautic World Conference in London on 4 and 5 November, and sponsorship is already helping it fund itself. I can’t wait to see many of you there!
Where we are now
I want to be really clear about where we are. Our recurring income still doesn’t cover the cost of running Mautic. Since June two more months of invoices have had to wait, and we’ve had to make even deeper cuts, which means less hands-on support to keep Mautic moving forward. Growing steady, recurring membership is the most important thing we can do next, so that good months become a bonus rather than a lifeline.
If you’d like to help, here are the best ways in.
- Become a member – corporate and individual memberships give us income we can plan around
- Sponsor the conference and put your organisation in front of around 200 people who care about open source marketing
- Contribute your skills – docs, translation, design, testing, support, events or code, there’s a way in for everyone (no coding needed!)
- Give what you can – every gift goes straight into the work and shows up in our reports
Read the full report
The report has all of this and more, including charts of our monthly income and spending, who’s choosing Mautic and where every number comes from. Download the Mautic H1 2026 report, and please do share it with anyone who cares about Mautic.
Over to you
I’d love to hear what this report brings up for you. What would make it easier for your organisation to support Mautic? I’m also curious whether a half-year report like this is useful, or whether you’d rather we stuck with the monthly Open Startup Reports – do let me know!
