incident.io
Nexus does the diagnosis; the rest is on-call plumbing
A side-by-side editorial comparison of Infisical and Split.io — release velocity, themes, recent moves, and the top alternatives to consider.
PAM and PKI now take up most of the lines in Infisical's release notes.
Six releases in two weeks, each a flat PR list with no narrative. The recurring feature work is privileged access management — Redis account types and web access, filling account fields from a pasted connection string, machine identity access — and PKI, which gained AWS Private CA as an issuing authority and SCEP enrollment for Microsoft Intune. Secret management itself mostly appears as rotation coverage for Cloudflare API tokens and R2 access keys.
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 releases in two weeks, each a flat PR list with no narrative. The recurring feature work is privileged access management — Redis account types and web access, filling account fields from a pasted connection string, machine identity access — and PKI, which gained AWS Private CA as an issuing authority and SCEP enrollment for Microsoft Intune. Secret management itself mostly appears as rotation coverage for Cloudflare API tokens and R2 access keys.
Infisical is assembling a credential platform rather than a secrets store, and it is doing so without a single headline release — each pillar arrives as two or three PRs per version. PKI is furthest along: issuing from an external AWS authority and enrolling devices through Intune puts it in territory previously held by dedicated certificate products. A third thread, the agent proxy, is accumulating the parts a product needs before launch — a Google Workspace service template, last-used timestamps, and adoption telemetry for proxied services.
The agent proxy is the thread most likely to get a real announcement; service templates and usage telemetry landing now are the groundwork a launch requires.
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 Infisical 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.
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
Fission's release feed carries only RC tags, and none of them say what shipped
See all Infisical 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. Infisical 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. Infisical 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 Infisical alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Infisical alternatives" section above for the current picks, or visit /alternatives/infisical 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.