authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Infisical vs Redocly
A side-by-side editorial comparison of Infisical and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
Infisical vs Redocly: at a glance
What is Infisical?
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.
What is Redocly?
Redocly opens its docs MCP endpoint to anonymous readers
Redocly publishes a per-package changelog across a wide surface — Realm, Reef, Revel, Reunite, Redoc, the theme and config packages — so a single upstream fix appears as six or seven near-identical entries on the same timestamp. The newest substantive item is a single config feature: mcp.docs.publicEndpoint, which exposes a documentation MCP endpoint to anonymous users. Around it sit Reunite app changes for organization invites and project card badges, and a batch of packages all republished for one missing dependency export.
Infisical vs Redocly: editorial side-by-side
Infisical
6.3INFRA · APIS
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Redocly
5.0INFRA · APIS
Redocly opens its docs MCP endpoint to anonymous readers
◆ Current state
Redocly publishes a per-package changelog across a wide surface — Realm, Reef, Revel, Reunite, Redoc, the theme and config packages — so a single upstream fix appears as six or seven near-identical entries on the same timestamp. The newest substantive item is a single config feature: mcp.docs.publicEndpoint, which exposes a documentation MCP endpoint to anonymous users. Around it sit Reunite app changes for organization invites and project card badges, and a batch of packages all republished for one missing dependency export.
◆ Where it's heading
Two things are visible in this feed. The first is the packaging: because every package cuts its own version for a shared fix, the changelog overstates activity and buries the one release that carries a feature. The second is where the features land — documentation as something machines consume, with the MCP endpoint now reachable without a login. The config package is where that gets switched on, which is a reasonable signal that the capability is being pushed toward self-serve adoption rather than kept behind account setup.
◆ Prediction
Expect the MCP surface to accumulate configuration rather than announcements — scoping, rate limiting, or which docs the endpoint exposes — since that is the shape every feature on this feed arrives in.
Alternatives to Infisical and Redocly
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 Redocly.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Retool
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all Infisical alternatives → · See all Redocly alternatives →
Recent activity from Infisical and Redocly
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoInfisicalFolder-level RBAC lands; PKI syncs to GCP Certificate Manager
- 2d agoRedoclyPublic MCP docs endpoint for anonymous users
- 5d agoRedoclyVisibility badges on project cards
- 5d agoRedoclyPending organization invites surfaced inside the app
- 6d agoInfisicalPAM discovers Postgres accounts; gateway pools get load balancing
- 7d agoInfisicalRoot encryption key rotation lands; cert profiles move into applications
- 7d agoInfisicalPAM gains IAM auth for Postgres; KMS keys get delete protection
- 8d agoRedoclyReef: missing @xyflow/system exports fixed
- 8d agoRedocly@redocly/graphql-docs: missing @xyflow/system exports fixed
- 8d agoRedocly@redocly/asyncapi-docs: missing @xyflow/system exports fixed
- 12d agoInfisicalTwo fixes: identity TLS cert constraints and rotation inputs
- 12d agoInfisicalCertificate manager adds PKCS#12 keystore import
Frequently asked questions
What is the difference between Infisical and Redocly?
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.
Is Infisical better than Redocly?
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.
What are the best alternatives to Infisical?
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.
What are the best alternatives to Redocly?
Top Redocly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Redocly alternatives" section above for the current picks, or visit /alternatives/redocly for the full list with editorial commentary on each.