Mautic vs Stensul
Side-by-side trajectory, velocity, and editorial themes.
Mautic hardens security across three branches and lines up a feature-heavy 7.2.
Mautic is in a maintenance-and-hardening phase. The standout is a coordinated security release across three supported branches (7.1.2, 6.0.9, 5.2.11) fixing seven CVEs, including SQL injection in API contact filtering and an API v2 authorization bypass. In parallel, 7.1.3 cleans up campaign and email reliability bugs, and a 7.2.0 release candidate stages the next feature line.
The project is balancing three commitments: keeping older branches (5.2, 6.0, 7.0/7.1) patched for security, steadily fixing campaign and GrapesJS-builder reliability, and building 7.2 around transactional email, better bot detection, and PHP 8.5 support. It reads as the cadence of a mature open-source platform serving a broad installed base, not one chasing new categories.
The 7.2.0 RC points to a stable 7.2 GA next, carrying truly transactional emails, Matomo-based bot detection, and the GrapesJS builder improvements out of pre-release.
Stensul is betting its roadmap on governing AI-generated marketing content before it ships.
Stensul sells a governance layer that sits between AI-assisted content creation and the send platforms marketers already run, chiefly Salesforce Marketing Cloud and Pardot. Its recent moves — an MCP server, an Accessibility QA agent, and now a July release spanning Figma, WRITER, and Salesforce Marketing Cloud Next — all push one thesis: generation is solved, approval and compliance are the bottleneck. The blog cadence leans heavily on regulatory-risk thought leadership (FTC, FDA, SEC, EU AI Act), which doubles as demand-gen for that positioning rather than reflecting shipped product.
Stensul is expanding from an email-creation tool into a control plane for AI content across more surfaces — first email, now design via Figma and AI writing via WRITER — with governance 'agents' like Accessibility QA as a repeatable product primitive. The MCP server signals it wants to be the compliance checkpoint wherever generation happens rather than a destination app. Expect the 'Governed Creation' framing to keep absorbing adjacent creation tools instead of competing on generation itself.
The next move is likely more Governance Agents (brand, regulatory, localization checks) and broader MCP coverage beyond email, extending the same approve-before-send gate to the newly added Figma and WRITER surfaces.
See more alternatives to Mautic →
See more alternatives to Stensul →