Tautulli
Plex's analytics companion has spent a year shipping CVE fixes faster than features.
A side-by-side editorial comparison of Omni and billboard.js — release velocity, themes, recent moves, and the top alternatives to consider.
Omni ships weekly, and this quarter every week added something to the AI layer.
Omni publishes a dated digest every week, each bundling a handful of unrelated changes. Across the current window the AI work is continuous rather than occasional: AI Hub and Markdown columns reached general availability in May, visualization annotations in June, semantic model generation in July, with AI Routines gaining Slack support and chat-based creation along the way. The non-AI half is connection and embedding plumbing — OAuth for database connections, GitHub App and HTTPS deploy-token authentication for dbt, AccessBoost for Apps, embed display and timezone controls.
billboard.js is adding a canvas renderer — an SVG chart library admitting SVG has a ceiling.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
Omni publishes a dated digest every week, each bundling a handful of unrelated changes. Across the current window the AI work is continuous rather than occasional: AI Hub and Markdown columns reached general availability in May, visualization annotations in June, semantic model generation in July, with AI Routines gaining Slack support and chat-based creation along the way. The non-AI half is connection and embedding plumbing — OAuth for database connections, GitHub App and HTTPS deploy-token authentication for dbt, AccessBoost for Apps, embed display and timezone controls.
Omni is putting AI underneath the modeling layer rather than beside the charts. Generating the semantic model is a different bet than generating a query: the semantic layer is where a BI tool encodes what its metrics mean, and automating it moves AI from answering questions to defining the vocabulary the answers use. The governance work is arriving in step — AI credit controls per embed entity group and per user, AI skills gated by required access grants, evals support — which is what a vendor builds when customers are embedding these features into products they resell.
Expect AI Routines to keep expanding their trigger surface after Slack and chat-based creation, and the credit controls to grow into fuller usage governance as embedded AI reaches more end users. The digest format means individually significant launches will keep arriving in the middle of a list of unrelated fixes.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
Two constraints are being addressed at once. Canvas is the answer to dataset sizes where per-point DOM nodes stop being viable, and the fact that three consecutive candidates are spent on parity fixes shows how much behaviour an SVG-native library has to re-implement to make the alternative renderer feel identical. Tree-shakable modules attack the other constraint — bundle weight — which matters to exactly the same teams choosing a chart library on performance grounds.
Expect further candidates before 4.0.0 stable, still weighted toward canvas parity in interaction and label placement, since that is where every candidate so far has landed.
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 Omni or billboard.js.
Plex's analytics companion has spent a year shipping CVE fixes faster than features.
Delta Lake is handing table authority to Unity Catalog — under a feed buried in Databricks build tags.
OpenCTI ships weekly and is rebuilding its connector catalog into a marketplace.
Mimir's feed is mostly bot-authored Helm bumps; the real release is 3.2, and it is query-engine work.
Fluent Bit runs a 4.2 and a 5.0 train side by side, both fed by the same backport pipeline.
Countly's core is in maintenance while every real feature lands in the enterprise journey engine.
See all Omni alternatives → · See all billboard.js alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Omni 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. Omni 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 Analytics products to evaluate alongside.
Top Omni alternatives in Analytics are ranked by recent ship velocity. Browse the "Omni alternatives" section above for the current picks, or visit /alternatives/omni for the full list with editorial commentary on each.
Top billboard.js alternatives in Analytics are ranked by recent ship velocity. Browse the "billboard.js alternatives" section above for the current picks, or visit /alternatives/billboard-js for the full list with editorial commentary on each.