authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Redocly and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Resend ships an API endpoint most days, and has just added the checkbox enterprises ask for
Resend is an email API for developers, releasing nearly every day in short, single-purpose notes. The current run is almost entirely API surface: email metrics, shareable email links, duplicating an automation, renaming an API key without regenerating it. Distribution work runs alongside — an MCP server, a CLI, plugins for Cursor and n8n — so that everything reachable by API is also reachable from whatever tool a developer is already in. Single Sign-On is the first entry in a while aimed at a buyer rather than a builder.
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.
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.
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.
Resend is an email API for developers, releasing nearly every day in short, single-purpose notes. The current run is almost entirely API surface: email metrics, shareable email links, duplicating an automation, renaming an API key without regenerating it. Distribution work runs alongside — an MCP server, a CLI, plugins for Cursor and n8n — so that everything reachable by API is also reachable from whatever tool a developer is already in. Single Sign-On is the first entry in a while aimed at a buyer rather than a builder.
Two strands. The API is being filled in methodically: anything the dashboard can do is becoming an endpoint, which is what makes the CLI, MCP server and editor plugins cheap to build on top. And the product is starting to grow the account-level features an organisation buys rather than a developer adopts — SSO now, after pay-as-you-go pricing and suppression visibility earlier in the year. The two strands are the same motion at different altitudes: bottom-up adoption, then the controls that let it survive procurement.
SSO rarely arrives alone; expect SCIM provisioning, role definitions and audit logging to follow, since the API-key and permissions surface is already there to build them on.
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 Redocly or Resend.
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.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Redocly alternatives → · See all Resend alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Infra & APIs. Resend 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. Resend 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 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.
Top Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.