Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
pkgdown vs WorkOS
A side-by-side editorial comparison of pkgdown and WorkOS — release velocity, themes, recent moves, and the top alternatives to consider.
pkgdown vs WorkOS: at a glance
| Feature | pkgdown | WorkOS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 8.8 |
| Sparks · 30d | 0 | 2 |
| Top themes | documentation, llm-readable, quarto, dark-mode | identity, authentication, ai-agents, scim |
| Last editorial update | 5d ago | 15h ago |
| Website | Visit → | — |
What is pkgdown?
pkgdown now generates llms.txt and a markdown copy of every documentation page
pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.
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.
pkgdown vs WorkOS: editorial side-by-side
pkgdown
0.0INFRA · APIS
pkgdown now generates llms.txt and a markdown copy of every documentation page
◆ Current state
pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.
◆ Where it's heading
Two audiences are now being served from one build. Human-facing work continues in small increments - dark-mode plot filtering, new translations, a local http server so search works in preview - while the new machine-facing output is opt-out rather than opt-in. The default matters more than the feature: thousands of package sites will start emitting llms.txt without their maintainers choosing to.
◆ Prediction
Expect the markdown output to gain the same configuration surface the HTML has, and the llms.txt contents to get more selective as maintainers discover what ends up in it; a way to exclude individual pages is the obvious next request.
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 pkgdown 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 pkgdown 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 pkgdown alternatives → · See all WorkOS alternatives →
Recent activity from pkgdown 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 ⚡
- 1mo agopkgdownLocal preview served over http so search works
- 9mo agopkgdownbuild_llm_docs() emits llms.txt and markdown for every page ⚡
- 1y agopkgdownMenu items accept class and id attributes
- 1y agopkgdownROR IDs, Codeberg support, bslib navbar variables
- 1y agopkgdownKeyboard shortcut for search; clean_cache() added
- 2y agopkgdownQuarto vignettes, light/dark switch, self-hosted assets
Frequently asked questions
What is the difference between pkgdown and WorkOS?
They serve adjacent needs but don't currently overlap on shipped themes. WorkOS is currently shipping more aggressively (velocity 8.8 vs 0.0), 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 pkgdown 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 0.0), 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 pkgdown?
Top pkgdown alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pkgdown alternatives" section above for the current picks, or visit /alternatives/pkgdown 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.