← Back to home
Comparison · Marketing

Open Web Analytics vs Neos CMS

A side-by-side editorial comparison of Open Web Analytics and Neos CMS — release velocity, themes, recent moves, and the top alternatives to consider.

Open Web Analytics vs Neos CMS: at a glance

FeatureOpen Web AnalyticsNeos CMS
SectorMarketingMarketing
Velocity score6.35.0
Sparks · 30d10
Top themesweb-analytics, self-hosted, php-modernization, security-hardeningcontent management, content repository, workspace roles, dual branch releases
Last editorial update3d ago5h ago
WebsiteVisit →Visit →

What is Open Web Analytics?

Open Web Analytics went from one release a year to six in a fortnight.

OWA published more releases in the last two weeks than in the previous two years. The sequence runs security hardening (1.8.2, 1.8.3), then a modernization release that raises the floor to PHP 8.2 and rebuilds the JavaScript toolchain (1.9.0), an emergency patch for a 403 that blocked every fresh install (1.9.1), a structural release completing the PSR-4 migration and repairing the updater (1.10.0), and a cleanup pass that tightens REST responses (1.10.1).

Read the full Open Web Analytics trajectory →

What is Neos CMS?

Neos is finishing the 9.x content-repository rebuild while 9.2 adds editorial roles.

Maintenance releases go out to two branches at once, with 9.1.7 and 9.0.14 carrying an identical set of fixes minutes apart. The substance sits in the 9.2 beta line: a workspace module with role assignments, a grace period for soft-removal garbage collection, a backend document node link in the workspace breadcrumb, and a bump of the minimum PHP version to 8.4. The recurring bug fixes cluster around the content repository, dimension space points, projections, and publishing selected changes.

Read the full Neos CMS trajectory →

Open Web Analytics vs Neos CMS: editorial side-by-side

O6.3

Open Web Analytics went from one release a year to six in a fortnight.

◆ Current state

OWA published more releases in the last two weeks than in the previous two years. The sequence runs security hardening (1.8.2, 1.8.3), then a modernization release that raises the floor to PHP 8.2 and rebuilds the JavaScript toolchain (1.9.0), an emergency patch for a 403 that blocked every fresh install (1.9.1), a structural release completing the PSR-4 migration and repairing the updater (1.10.0), and a cleanup pass that tightens REST responses (1.10.1).

◆ Where it's heading

This is a self-hosted analytics project being brought back from stagnation in a compressed burst, and the order of the work says how bad the starting position was: patch the security holes, then make it run on a supported PHP, then fix the fact that installing and updating were themselves broken, then start on structure. Backwards-compatibility shims for modules, templates and themes indicate the maintainers are trying to modernize without stranding the existing installed base. The REST API is where that promise is thinnest — 1.10.1 narrows responses to documented properties, which is correct but will break clients that were reading internals.

◆ Prediction

With the runtime, installer and updater repaired and PSR-4 finished, the next work is most likely to continue on the API and the reporting layer, where 1.10.0 already flagged a cluster of e-commerce bugs.

N
Neos CMS
MARKETING
5.0

Neos is finishing the 9.x content-repository rebuild while 9.2 adds editorial roles.

◆ Current state

Maintenance releases go out to two branches at once, with 9.1.7 and 9.0.14 carrying an identical set of fixes minutes apart. The substance sits in the 9.2 beta line: a workspace module with role assignments, a grace period for soft-removal garbage collection, a backend document node link in the workspace breadcrumb, and a bump of the minimum PHP version to 8.4. The recurring bug fixes cluster around the content repository, dimension space points, projections, and publishing selected changes.

◆ Where it's heading

The 9.x line is still settling the event-sourced content repository introduced with it, judging by how many fixes touch projections, tag inheritance across dimensions, and partial publishing. On top of that, 9.2 is adding editorial governance, with workspaces gaining explicit role assignments rather than implicit access. The PHP 8.4 requirement signals the project is willing to move its floor rather than carry compatibility.

◆ Prediction

The 9.2 betas keep adding to workspaces, roles first and now garbage-collection controls; expect the release to land with workspace administration as its headline rather than any change to the editing interface.

Alternatives to Open Web Analytics and Neos CMS

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 Open Web Analytics or Neos CMS.

See all Open Web Analytics alternatives → · See all Neos CMS alternatives →

Recent activity from Open Web Analytics and Neos CMS

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoOpen Web AnalyticsRelease 1.10.1
  2. 6d agoOpen Web AnalyticsRelease 1.10.0
  3. 9d agoOpen Web AnalyticsRelease 1.9.1
  4. 11d agoOpen Web AnalyticsRelease 1.9.0
  5. 15d agoOpen Web AnalyticsRelease 1.8.3
  6. 17d agoOpen Web AnalyticsRelease 1.8.2
  7. 22d agoNeos CMS9.0.14: maintenance backport of the 9.1.7 fixes
  8. 22d agoNeos CMS9.1.7: dimension tag inheritance and partial publishing fixes
  9. 23d agoNeos CMS9.2.0-beta2: no release notes in the feed
  10. 1mo agoNeos CMS9.2.0-beta1: workspace roles and a PHP 8.4 floor

Frequently asked questions

What is the difference between Open Web Analytics and Neos CMS?

They serve adjacent needs but don't currently overlap on shipped themes. Open Web Analytics is currently shipping more aggressively (velocity 6.3 vs 5.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.

Is Open Web Analytics better than Neos CMS?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Open Web Analytics is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.

What are the best alternatives to Open Web Analytics?

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.

What are the best alternatives to Neos CMS?

Top Neos CMS alternatives in Marketing are ranked by recent ship velocity. Browse the "Neos CMS alternatives" section above for the current picks, or visit /alternatives/neos-cms for the full list with editorial commentary on each.