incident.io
Nexus does the diagnosis; the rest is on-call plumbing
A side-by-side editorial comparison of Biome and Split.io — release velocity, themes, recent moves, and the top alternatives to consider.
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
Split FME's March releases pull feature flags fully into the Harness DevOps platform.
Split.io now ships under the Harness Feature Management & Experimentation (FME) brand, and the substantive activity is captured in the rolled-up release-notes page rather than per-release entries. The March 2026 wave landed three real ships: Policy As Code (OPA) for FME Feature Flags, Feature Flag Archiving with RBAC and pre-archive checks, and the GA of FME steps in Harness pipelines covering full flag lifecycle management. The rest of the recent feed is scraper artifacts — page chrome captured as titles.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
The rule set is widening along two axes at once: frameworks and file types. Framework rules are now specific enough to argue about Svelte runes rather than generic JavaScript, and CSS handling has pushed into HTML attributes and registered custom properties. The larger move sits in 2.5.8's PR list rather than its changelog — a markdown linter, a markdown rule generator, a markdownlint rule source, a two-phase markdown parser, and a first rule in useTopLevelHeading, none of it documented for users yet.
Markdown linting looks close enough to ready that it should appear in the changelog proper rather than the PR list, most likely as nursery rules in the next minor.
Split.io now ships under the Harness Feature Management & Experimentation (FME) brand, and the substantive activity is captured in the rolled-up release-notes page rather than per-release entries. The March 2026 wave landed three real ships: Policy As Code (OPA) for FME Feature Flags, Feature Flag Archiving with RBAC and pre-archive checks, and the GA of FME steps in Harness pipelines covering full flag lifecycle management. The rest of the recent feed is scraper artifacts — page chrome captured as titles.
FME is becoming a first-class part of the Harness DevOps surface rather than a standalone feature-flag tool. Pipeline-native flag operations, policy-as-code governance, and archiving as a managed lifecycle state all reflect a single direction: feature flags as a governed, audited, and pipeline-integrated component of the deployment system. The standalone Split UX is fading into Harness conventions.
Expect more Harness-platform conventions to land on FME — RBAC unification, environments and pipelines parity, OPA policy templates shipped out of the box, and observability tying flag changes back into deploy-failure/MTTR dashboards. Standalone-Split UX surfaces will likely be retired further.
Other Infra & APIs 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 Biome or Split.io.
Nexus does the diagnosis; the rest is on-call plumbing
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
1.38.4 is a security release in all but name, closing ACL gaps across the API.
PAM and PKI now take up most of the lines in Infisical's release notes.
DNSControl is rewriting its record internals in public, one release candidate at a time
Fission's release feed carries only RC tags, and none of them say what shipped
See all Biome alternatives → · See all Split.io alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Biome is currently shipping more aggressively (velocity 5.0 vs 0.6), 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. Biome is currently shipping more aggressively (velocity 5.0 vs 0.6), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Biome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Biome alternatives" section above for the current picks, or visit /alternatives/biome for the full list with editorial commentary on each.
Top Split.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Split.io alternatives" section above for the current picks, or visit /alternatives/split for the full list with editorial commentary on each.