incident.io
Nexus does the diagnosis; the rest is on-call plumbing
A side-by-side editorial comparison of Fission and Infisical — 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.
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.
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.
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.
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 Infisical.
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
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
See all Fission alternatives → · See all Infisical 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.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. Infisical is currently shipping more aggressively (velocity 5.0 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 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.