Pimcore
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
A side-by-side editorial comparison of Craft CMS and Vero — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Craft CMS | Vero |
|---|---|---|
| Sector | Mkt Auto | Mkt Auto |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | cms, laravel, breaking-changes, plugin-api | marketing-automation, journeys, platform-migration, email |
| Last editorial update | 5d ago | 11d ago |
| Website | Visit → | — |
Craft 6 is being rebuilt on Laravel, and the alphas are breaking plugins to get there.
Craft runs two trains at once: a 6.0.0 alpha series rearchitecting the CMS, and 5.10.x patches that are single-bug fixes shipped within hours of each other. The alphas carry the work — queue jobs and dependency resolution moved onto Laravel's service container, control-panel serialization switched to Illuminate helpers, the imagine image library replaced with intervention/image, and a first-party control-panel component library added. Alpha 14 shipped with an explicit breaking-changes notice for plugin authors.
Marketing automation mid-migration, rebuilding Journeys branching on the 2.0 platform
Vero is running two platforms at once and the changelog reads that way. Vero 2.0 gained True/False and Exit nodes in Journeys — real conditional branching that routes customers on behavior, properties and actions — plus an SMS node, a Cmd+K command palette, Forms, and project-level reporting on the homepage summarizing messages sent, open, click and delivery rates. CC on emails shipped to Vero 1.0 campaigns with 2.0 support described as coming.
Craft runs two trains at once: a 6.0.0 alpha series rearchitecting the CMS, and 5.10.x patches that are single-bug fixes shipped within hours of each other. The alphas carry the work — queue jobs and dependency resolution moved onto Laravel's service container, control-panel serialization switched to Illuminate helpers, the imagine image library replaced with intervention/image, and a first-party control-panel component library added. Alpha 14 shipped with an explicit breaking-changes notice for plugin authors.
The direction is a Laravel-native Craft: Artisan command discovery, container-resolved queue jobs, Illuminate helpers, and plugins that no longer register through composer extra fields or automatic trait lifecycle hooks. The image pipeline swap brings libvips and formats like HEIC, JPEG XL and TIFF along with it. Meanwhile 5.10 receives nothing but same-day bug fixes, which is what a maintenance branch looks like once the team's attention has moved.
Expect further alphas to keep narrowing the plugin API surface ahead of a beta, with the 5.10 line continuing at one or two same-day patch releases a week.
Vero is running two platforms at once and the changelog reads that way. Vero 2.0 gained True/False and Exit nodes in Journeys — real conditional branching that routes customers on behavior, properties and actions — plus an SMS node, a Cmd+K command palette, Forms, and project-level reporting on the homepage summarizing messages sent, open, click and delivery rates. CC on emails shipped to Vero 1.0 campaigns with 2.0 support described as coming.
The work is about reaching parity and then passing it. Branching and exit nodes are table stakes for a journey builder, so shipping them in 2.0 marks the point where the new platform becomes usable for real lifecycle programs rather than linear sends. The CC entry shows the migration's awkward middle — a feature landing on the old platform first. Project-level reporting suggests the next concern is proving programs work, not just building them.
Expect CC and the remaining 1.0-only capabilities to close out on 2.0, since the entries explicitly flag that gap, and reporting to deepen now that a project-level summary exists.
Other Mkt Auto products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Craft CMS or Vero.
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
Three release lines running in parallel, all of them shipping nothing but fixes this week
OpnForm is turning its V2 platform into an automation surface, one integration at a time.
Zoho Social opens its management surface to AI assistants via MCP.
AWeber is moving the console out of the browser and into the chat window
Building an agent-drivable outreach stack — MCP, then OpenClaw, now an in-dashboard AI copilot.
See all Craft CMS alternatives → · See all Vero alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Craft CMS is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Craft CMS is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top Craft CMS alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Craft CMS alternatives" section above for the current picks, or visit /alternatives/craft-cms for the full list with editorial commentary on each.
Top Vero alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Vero alternatives" section above for the current picks, or visit /alternatives/vero for the full list with editorial commentary on each.