incident.io
Nexus does the diagnosis; the rest is on-call plumbing
A side-by-side editorial comparison of Fission and Split.io — release velocity, themes, recent moves, and the top alternatives to consider.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
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.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
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 Fission 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.
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
DNSControl is rewriting its record internals in public, one release candidate at a time
See all Fission 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. Split.io is currently shipping more aggressively (velocity 0.6 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. Split.io is currently shipping more aggressively (velocity 0.6 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 Infra & APIs products to evaluate alongside.
Top Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission 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.