Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Certbot vs WorkOS
A side-by-side editorial comparison of Certbot and WorkOS — release velocity, themes, recent moves, and the top alternatives to consider.
Certbot vs WorkOS: at a glance
| Feature | Certbot | WorkOS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 8.8 |
| Sparks · 30d | 0 | 2 |
| Top themes | tls, certificates, acme, api-refactor | identity, authentication, ai-agents, scim |
| Last editorial update | 9d ago | 15h ago |
| Website | Visit → | — |
What is Certbot?
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
Certbot is on a roughly monthly minor cadence and the defining change in this window is IP address certificate support. 5.3.0 added the --ip-address flag for the standalone and manual plugins and began renaming the API's domain concept to identifier; 5.4.0 extended IP issuance to the webroot plugin. The other visible work is structural: the nginx and apache plugin code moved into the certbot package as extras, the pyOpenSSL dependency is being unwound through a series of deprecations, and certbot.ocsp is scheduled for removal from the public API.
What is WorkOS?
WorkOS is building identity for agents while quietly fixing the sign-up funnel.
WorkOS ships several small entries a week, and August splits cleanly in two. One half is authentication housekeeping for human users: an Android SDK, deliverability checks that reject undeliverable addresses at sign-up, invitation acceptance counting as email verification, and a reversible SCIM proxy for migrating directory connections without downtime. The other half is agent infrastructure — Agent Registration via the auth.md protocol, and the Pipes Token Proxy that calls third-party APIs on a user's behalf without the application ever touching their token.
Certbot vs WorkOS: editorial side-by-side
Certbot
2.5INFRA · APIS
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
◆ Current state
Certbot is on a roughly monthly minor cadence and the defining change in this window is IP address certificate support. 5.3.0 added the --ip-address flag for the standalone and manual plugins and began renaming the API's domain concept to identifier; 5.4.0 extended IP issuance to the webroot plugin. The other visible work is structural: the nginx and apache plugin code moved into the certbot package as extras, the pyOpenSSL dependency is being unwound through a series of deprecations, and certbot.ocsp is scheduled for removal from the public API.
◆ Where it's heading
The identifier rename is the tell — Certbot's data model assumed a certificate subject was a domain name, and IP address issuance forced that assumption out of the type system. Expect that refactor to continue reaching further into the plugin API, since get_chall_pref has already changed signature. In parallel the project is shedding dependencies and consolidating packaging: plugins as extras rather than separate distributions, pyOpenSSL functions deprecated batch by batch, and Docker images tracking new Python versions promptly. The releases have become small and predictable, with most content in the Changed and Fixed sections rather than Added.
◆ Prediction
Expect IP address support to reach the remaining plugins, following standalone and manual then webroot, and expect the pyOpenSSL removal to land as a major version once the deprecation cycle completes. Given 5.5.0 already deprecated certbot.ocsp for removal in the next major, that release is the one to watch for breaking changes.
WorkOS
8.8INFRA · APIS
WorkOS is building identity for agents while quietly fixing the sign-up funnel.
◆ Current state
WorkOS ships several small entries a week, and August splits cleanly in two. One half is authentication housekeeping for human users: an Android SDK, deliverability checks that reject undeliverable addresses at sign-up, invitation acceptance counting as email verification, and a reversible SCIM proxy for migrating directory connections without downtime. The other half is agent infrastructure — Agent Registration via the auth.md protocol, and the Pipes Token Proxy that calls third-party APIs on a user's behalf without the application ever touching their token.
◆ Where it's heading
The agent work is the strategic line. Registration gives an agent an identity of its own instead of a borrowed human session; the token proxy means an application acting for a user never holds the credential. Together they describe a stack where an agent can be authorized, audited and revoked as a first-class principal. The human-auth releases are conversion and migration work — the deliverability check and SCIM Bridge both remove reasons a customer stalls — which is what a developer-infrastructure company does while its next category is still forming.
◆ Prediction
Registration and the token proxy leave scoping and revocation as the visible gaps, so expect per-agent permissions or consent surfaces next. Whether auth.md gains adoption beyond WorkOS is not something these entries can answer.
Alternatives to Certbot and WorkOS
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 Certbot or WorkOS.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all Certbot alternatives → · See all WorkOS alternatives →
Recent activity from Certbot and WorkOS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoWorkOSAndroid SDK
- 2d agoWorkOSHigher quality sign-ups with email deliverability checks
- 5d agoWorkOSMigrate SCIM Connections with SCIM Bridge
- 6d agoWorkOSAccepted invitations count as email verification
- 13d agoWorkOSPipes Token Proxy ⚡
- 15d agoWorkOSAgent Registration ⚡
- 28d agoCertbot5.7.0 fixes nginx parsing of comments inside multi-line directives
- 3mo agoCertbot5.6.0 bumps dependency floors and rebases Docker on Python 3.14
- 4mo agoCertbot5.5.0 folds the nginx and apache plugins into certbot extras
- 5mo agoCertbot5.4.0 extends IP address issuance to the webroot plugin
- 6mo agoCertbot5.3.1 rebuilds snaps with updated dependencies
- 6mo agoCertbotCertbot adds IP address certificates and an identifier-based API ⚡
Frequently asked questions
What is the difference between Certbot and WorkOS?
They serve adjacent needs but don't currently overlap on shipped themes. WorkOS is currently shipping more aggressively (velocity 8.8 vs 2.5), with 2 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 Certbot better than WorkOS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. WorkOS is currently shipping more aggressively (velocity 8.8 vs 2.5), with 2 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 Certbot?
Top Certbot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Certbot alternatives" section above for the current picks, or visit /alternatives/certbot for the full list with editorial commentary on each.
What are the best alternatives to WorkOS?
Top WorkOS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "WorkOS alternatives" section above for the current picks, or visit /alternatives/workos for the full list with editorial commentary on each.