Cvent
Cvent's assistant moves from answering support questions to answering data questions
A side-by-side editorial comparison of Bludit and Open Web Analytics — release velocity, themes, recent moves, and the top alternatives to consider.
A flat-file CMS with a long CVE history just wired its API up for MCP.
Bludit ships every few weeks, and almost every release carries a security fix: an authentication bypass and arbitrary file upload in 3.18.4, an authenticated RCE via file upload plus .htaccess bypass in 3.20.0, a path traversal in the API files endpoint in 3.21.0, and session invalidation for disabled users in 3.22.0. Around that, the work is editor and dashboard maintenance, theme additions and a plugin hook for injecting editor toolbar buttons.
After a fortnight of repairs, OWA finally ships features again: partitioning and a scheduler.
OWA published more releases in the last month than in the previous two years, and 1.11.0 is the first of them that adds rather than repairs. It brings two new subsystems that depend on each other: date partitioning for the fact tables, and a job scheduler driven by a single cron entry. Behind it sits the repair sequence — security hardening in 1.8.2 and 1.8.3, a PHP 8.2 floor and rebuilt JavaScript toolchain in 1.9.0, an emergency 403 fix in 1.9.1, the PSR-4 migration and a repaired updater in 1.10.0, and tightened REST responses in 1.10.1.
Bludit ships every few weeks, and almost every release carries a security fix: an authentication bypass and arbitrary file upload in 3.18.4, an authenticated RCE via file upload plus .htaccess bypass in 3.20.0, a path traversal in the API files endpoint in 3.21.0, and session invalidation for disabled users in 3.22.0. Around that, the work is editor and dashboard maintenance, theme additions and a plugin hook for injecting editor toolbar buttons.
Two threads run in parallel. One is a sustained security cleanup, largely driven by external reports and handled release by release. The other is a quiet repositioning of the API: 3.22.0 improved it specifically to support MCP, which points a file-based CMS at agent-driven authoring. The plugin hook work in 3.20.0 fits the same pattern of opening the editor to programmatic control.
Expect the MCP-facing API work to continue — the initial support arrived as API improvements rather than a documented server, which is the piece still missing.
OWA published more releases in the last month than in the previous two years, and 1.11.0 is the first of them that adds rather than repairs. It brings two new subsystems that depend on each other: date partitioning for the fact tables, and a job scheduler driven by a single cron entry. Behind it sits the repair sequence — security hardening in 1.8.2 and 1.8.3, a PHP 8.2 floor and rebuilt JavaScript toolchain in 1.9.0, an emergency 403 fix in 1.9.1, the PSR-4 migration and a repaired updater in 1.10.0, and tightened REST responses in 1.10.1.
The project has moved from making itself installable to making itself operable at volume. The upgrade design says the maintainers know who they are dealing with: the schema update is mandatory and the scheduler refuses every job until it runs, but partitioning an existing install is deliberately left as a manual, dry-runnable step with a published cost of roughly five seconds per million rows per table, because it rewrites each fact table twice under a write lock. The new cron requirement is the first time OWA has asked operators to run something periodic, and the admin nag until it exists suggests they expect people to miss it.
With partitioning in place but opt-in, expect the follow-up work to be retention and pruning on top of the partitions — the reason to partition fact tables is to drop old ones cheaply, and the scheduler is the piece that would do it. The 2.0 deprecation list flagged in 1.10.0 remains the other open thread.
Other Marketing 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 Bludit or Open Web Analytics.
Cvent's assistant moves from answering support questions to answering data questions
Publer's feed is mostly holiday calendars, with real features hiding in same-day pairs.
GMass adds an AI layer that explains campaign stats instead of just charting them.
Ten months of nothing but fixes, and the only movement now comes from an add-on rather than the plugin itself.
WP Tasty released all five plugins in one morning to split editor access from admin settings.
Metricool's feed is a content-marketing engine; the only product news is a LinkedIn partner badge.
See all Bludit alternatives → · See all Open Web Analytics alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Open Web Analytics is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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. Open Web Analytics is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Marketing products to evaluate alongside.
Top Bludit alternatives in Marketing are ranked by recent ship velocity. Browse the "Bludit alternatives" section above for the current picks, or visit /alternatives/bludit for the full list with editorial commentary on each.
Top Open Web Analytics alternatives in Marketing are ranked by recent ship velocity. Browse the "Open Web Analytics alternatives" section above for the current picks, or visit /alternatives/open-web-analytics for the full list with editorial commentary on each.