Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
A side-by-side editorial comparison of NetObserv and Tinybird — release velocity, themes, recent moves, and the top alternatives to consider.
NetObserv is layering TLS visibility and health alerting on top of its eBPF flow pipeline.
NetObserv ships roughly monthly as a coordinated bundle — operator, eBPF agent, flowlogs-pipeline and console plugin move together in each release. The functional work over these six releases splits three ways: a TLS visibility feature that arrived as a knob in 1.11.3 and has been extended with metrics and alerts since, a Network Health layer built on Prometheus recording rules rather than alerts alone, and steady hardening of the agent-to-pipeline path (mTLS, hot-reload filters, packet translation and sampling fixes). Prometheus is now on by default.
Tinybird is retiring Classic on a clock while stacking capability into Forward
Releases arrive weekly and the through-line is the migration from Classic to Forward. Classic is now scheduled for sunset on Free and Developer plans by September 15, following the BI Connector's end of life and the earlier migrate-to-forward CLI command. Forward is where capability accumulates: DynamoDB connectivity, PREWHERE, lightweight deletes in beta, arm64-native local runs and a ClickHouse bump from 25.3 to 25.8.
NetObserv ships roughly monthly as a coordinated bundle — operator, eBPF agent, flowlogs-pipeline and console plugin move together in each release. The functional work over these six releases splits three ways: a TLS visibility feature that arrived as a knob in 1.11.3 and has been extended with metrics and alerts since, a Network Health layer built on Prometheus recording rules rather than alerts alone, and steady hardening of the agent-to-pipeline path (mTLS, hot-reload filters, packet translation and sampling fixes). Prometheus is now on by default.
The project is moving from flow collection toward opinionated health signalling — recording rules, runbook links in alerts, ingress 5xx and latency templates, health metadata driving console plugin config. That is the shape of a tool trying to answer 'is the network healthy' rather than only 'what traffic occurred'. In parallel, supply-chain and workflow security is getting real attention: SBOM generation and artifact signing, SHA-pinned GitHub Actions, pwn-request workflow checks and a pprof exposure fix all landed in the last two releases. The operator was also renamed from network-observability-operator to netobserv-operator.
Expect the TLS thread to keep extending — the sequence so far is fields, then metrics, then alerts, so dashboards and health rules built on TLS data are the natural next step. Continued investment in the Network Health rule set is the other safe bet, since it is where the last three releases have concentrated their non-dependency commits.
Releases arrive weekly and the through-line is the migration from Classic to Forward. Classic is now scheduled for sunset on Free and Developer plans by September 15, following the BI Connector's end of life and the earlier migrate-to-forward CLI command. Forward is where capability accumulates: DynamoDB connectivity, PREWHERE, lightweight deletes in beta, arm64-native local runs and a ClickHouse bump from 25.3 to 25.8.
Two things are happening in parallel, retiring the old platform on a published schedule while making the new one worth the move. Ingestion is the current focus and it is moving quickly, with v1 going from experimental in the CLI to the default for local files inside two weeks, and integer preservation and quarantine persistence fixed around it. The updated agent skills mentioned alongside the CLI work suggest the tooling is being shaped for agents as well as people.
September 15 is the next fixed milestone, and paid tiers are the obvious follow-on though these entries stop short of committing to a date for them. Expect v1 ingestion to keep widening from local files into the remaining paths now that it is the default for one of them.
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 NetObserv or Tinybird.
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
Cortex is betting on Parquet block storage and graduating years of experimental features.
Storm 3.0 finishes removing the Clojure it was built in, and moves to a Java 21 baseline.
Five release candidates in two years, none of them stable, and none since October 2025.
A monitoring project whose public release feed skips the release that mattered.
Axiom is rebuilding observability so an AI agent, not a human, can be the first user.
See all NetObserv alternatives → · See all Tinybird alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tinybird is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Tinybird is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 NetObserv alternatives in Analytics are ranked by recent ship velocity. Browse the "NetObserv alternatives" section above for the current picks, or visit /alternatives/netobserv for the full list with editorial commentary on each.
Top Tinybird alternatives in Analytics are ranked by recent ship velocity. Browse the "Tinybird alternatives" section above for the current picks, or visit /alternatives/tinybird for the full list with editorial commentary on each.