PostHog
PostHog is filling in Logs and the mobile SDKs while quietly growing a support product.
A side-by-side editorial comparison of Shynet and OpenObserve — release velocity, themes, recent moves, and the top alternatives to consider.
Shynet went silent for two and a half years and a security audit is what woke it up.
Shynet's most recent release closes two externally reported vulnerabilities: a wildcard ALLOWED_HOSTS default enabling password reset poisoning, and stored XSS in two template filters, both credited to an outside security firm. It arrived after a gap of roughly two and a half years, and the release before it was a temporary dependency install workaround. The dashboard features people associate with the project — the annotated world map, the map-versus-table toggle — all date from 2021.
OpenObserve is running a stabilization train on 0.91 while 0.92 gathers features in RC
Two branches are moving at once. The 0.91 line has taken four patch releases since the start of July, each carrying two or three fixes — memtable rotation, RBAC migration for metric stream names, PagerDuty integration bugs, an anomaly-detection threshold that no longer forces a retrain. In parallel, 0.92 is accumulating in release candidates: agent-level filters, an option to disable default index fields via ZO_FEATURE_DEFAULT_INDEX_FIELDS_ENABLED, and parallel zstd compression. The substantive 0.91.0 release itself — Super Org multi-tenancy, org-level ingestion tokens, and a round of Tantivy search performance work including a footer cache and bloom-filter pruning — sits just outside the recent window.
Shynet's most recent release closes two externally reported vulnerabilities: a wildcard ALLOWED_HOSTS default enabling password reset poisoning, and stored XSS in two template filters, both credited to an outside security firm. It arrived after a gap of roughly two and a half years, and the release before it was a temporary dependency install workaround. The dashboard features people associate with the project — the annotated world map, the map-versus-table toggle — all date from 2021.
The arc is a project that had real community momentum and then stopped. In 2021 releases were arriving monthly and were, by the maintainer's own note, driven entirely by contributors; by 2023 the content was dependabot bumps and build workarounds; after that, nothing until a security report forced a response. Nothing in the recent entry suggests development resumed more broadly — it is a targeted fix release, not a return to cadence.
These entries give no basis for expecting feature work to resume; the realistic expectation is that the next release, whenever it comes, is again driven by an external security report or a dependency that stops installing.
Two branches are moving at once. The 0.91 line has taken four patch releases since the start of July, each carrying two or three fixes — memtable rotation, RBAC migration for metric stream names, PagerDuty integration bugs, an anomaly-detection threshold that no longer forces a retrain. In parallel, 0.92 is accumulating in release candidates: agent-level filters, an option to disable default index fields via ZO_FEATURE_DEFAULT_INDEX_FIELDS_ENABLED, and parallel zstd compression. The substantive 0.91.0 release itself — Super Org multi-tenancy, org-level ingestion tokens, and a round of Tantivy search performance work including a footer cache and bloom-filter pruning — sits just outside the recent window.
The shape here is a project consolidating after a large release rather than chasing new surface area. The 0.92 RC contents point at operator control over ingest and index cost — letting users switch off default index fields is a storage-and-write-amplification lever, and parallel compression is the same concern from the CPU side. Agent-level filters suggest the collector-side story is being tightened too.
A 0.92.0 general release is the near-term move, carrying the index-field control and compression work, with the 0.91.x patch train tapering once it lands. Whether multi-tenancy from 0.91 gets follow-on quota or billing controls is not yet visible in the RC contents.
Other Analytics 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 Shynet or OpenObserve.
PostHog is filling in Logs and the mobile SDKs while quietly growing a support product.
Mixpanel is becoming a component other tools provision, not a destination users visit.
Polars is teaching its engine to spill, stream, and read the lakehouse.
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
With Interfaces, NocoDB stops being a database view and starts being an app builder.
Holistics keeps converting GUI-only BI objects into code, one class at a time.
See all Shynet alternatives → · See all OpenObserve alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenObserve is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. OpenObserve is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Shynet alternatives in Analytics are ranked by recent ship velocity. Browse the "Shynet alternatives" section above for the current picks, or visit /alternatives/shynet for the full list with editorial commentary on each.
Top OpenObserve alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenObserve alternatives" section above for the current picks, or visit /alternatives/openobserve for the full list with editorial commentary on each.