GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
A side-by-side editorial comparison of Infisical and Incus — release velocity, themes, recent moves, and the top alternatives to consider.
Infisical's secrets manager is growing a privileged-access platform around it.
Infisical ships a tagged release every two to four days, and the last ten are dominated by three build-outs: privileged access management, PKI and certificate syncing, and automated credential rotation. PAM has moved past scaffolding — connection testing, SSH session logging, CA certificate handling, and account fields auto-filled from a pasted connection string all landed inside three weeks. The core secrets store is stable enough that most of the churn now sits in the access layer wrapped around it.
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.
Infisical ships a tagged release every two to four days, and the last ten are dominated by three build-outs: privileged access management, PKI and certificate syncing, and automated credential rotation. PAM has moved past scaffolding — connection testing, SSH session logging, CA certificate handling, and account fields auto-filled from a pasted connection string all landed inside three weeks. The core secrets store is stable enough that most of the churn now sits in the access layer wrapped around it.
The releases point at a consolidation play: one control plane for secrets, machine identities, certificates, and privileged sessions, rather than a secrets store that hands off the rest to other tools. The agent-proxy and proxied-service work — Google Workspace templates, last-used timestamps, a dynamic-secret registry folded into the proxy allow-list — suggests brokered access is becoming a primary path rather than an add-on. Rotation is spreading backend by backend, with Azure app connections, LDAP, and Datadog API keys added across consecutive releases.
Expect rotation and PAM to keep expanding one connector at a time, with more app-connection rotation backends and more PKI sync destinations. A stable PAM release out of the current iteration is the likely next milestone.
7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.
The rhythm is a monthly feature release running alongside a long-term branch, and the recent work leans toward reach rather than new primitives: clients built natively for Windows and macOS, translations updated in nearly every release, feature gating so the same daemon behaves correctly across host configurations. Stateful migration getting migration-compatible CPU flags is the most operationally significant item, since it is what makes live migration work across non-identical hosts.
The cadence in this window is a feature release roughly every four to six weeks with LTS patches interleaved, so a 7.4 is the expected next step. The entries give no indication of a headline feature queued for it.
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 Incus.
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Firecracker's microVMs can now grow and shrink devices while running.
See all Infisical alternatives → · See all Incus alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Infisical and Incus are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 and Incus are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Incus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Incus alternatives" section above for the current picks, or visit /alternatives/incus for the full list with editorial commentary on each.