authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Apideck and Infisical — release velocity, themes, recent moves, and the top alternatives to consider.
A unified-API vendor growing by connector count, with accounting as the clear priority.
Apideck's feed is a connector catalogue: every entry announces one new integration and enumerates exactly which unified resources it supports and how completely. The last two months are dominated by Accounting — SnelStart, Twinfield, Restaurant365, Sage Intacct REST — with Issue Tracking (Freshservice, two GitHub Enterprise variants, Jira via API token) and HRIS (Hailey HR, HiBob) filling in behind.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Infisical ships near-daily across four surfaces — secrets management, PKI and certificate manager, PAM, and KMS. This release adds folder-level RBAC, so permissions can be scoped inside a project rather than only at project and environment level, and gives approvals and change requests their own webhook events. PKI keeps widening: a GCP Certificate Manager sync, Windows and Linux pre-fetch commands for PKI syncs, and certificate renewals exposed so agents can follow them. Project retention limits and Kubernetes managed-identity auth templates round it out, alongside a long run of v3 UI migration work.
Apideck's feed is a connector catalogue: every entry announces one new integration and enumerates exactly which unified resources it supports and how completely. The last two months are dominated by Accounting — SnelStart, Twinfield, Restaurant365, Sage Intacct REST — with Issue Tracking (Freshservice, two GitHub Enterprise variants, Jira via API token) and HRIS (Hailey HR, HiBob) filling in behind.
Two patterns are worth noting beyond the count. Coverage is documented honestly rather than uniformly — Twinfield's notes admit that line descriptions are not preserved and that only unpaid invoices list — which suggests Apideck is selling against the fiction that a unified API erases provider differences. Separately, connectors are arriving in more shapes: alongside fully mapped ones sit auth-only connectors that authenticate through Vault and then hand the raw provider API to the Proxy, and alternative auth variants of providers already covered.
Expect Accounting to keep leading the release count, and more providers to arrive first as auth-only or beta connectors before their unified resource mappings are filled in.
Infisical ships near-daily across four surfaces — secrets management, PKI and certificate manager, PAM, and KMS. This release adds folder-level RBAC, so permissions can be scoped inside a project rather than only at project and environment level, and gives approvals and change requests their own webhook events. PKI keeps widening: a GCP Certificate Manager sync, Windows and Linux pre-fetch commands for PKI syncs, and certificate renewals exposed so agents can follow them. Project retention limits and Kubernetes managed-identity auth templates round it out, alongside a long run of v3 UI migration work.
Two threads run underneath the release stream. Consolidation continues — dynamic secrets moved onto a shared provider registry this release, the same pattern that let native integrations enter deprecation in v0.162.22. The second is authorization getting finer rather than broader: folder RBAC, certificate private-key reads scoped to the certificate subject, LDAP bind passwords no longer returned on GET, and approval checks that respect validation rules. The product is being made safe to hand to more people inside one organisation, not just to more organisations.
Approval and change-request webhooks are the eventing half of a workflow whose UI shell just moved to v3, so external approval routing — the events feeding a reviewer outside Infisical — is the natural next step. The changelog is a PR list and states no plan.
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 Apideck or Infisical.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Alert rate limits stop being per-source and start being per-tenant, by query.
The essay series keeps running ahead of the products it describes.
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
The 3.x line finally ships function: authenticated secret writes and render patches.
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all Apideck 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 6.3 vs 5.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 6.3 vs 5.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 Apideck alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apideck alternatives" section above for the current picks, or visit /alternatives/apideck 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.