SLmetrics
A young ML metrics package rewrote its own backend twice in six months chasing speed.
Comparison · Infra & APIs
dockViewR vs WorkOS
A side-by-side editorial comparison of dockViewR and WorkOS — release velocity, themes, recent moves, and the top alternatives to consider.
dockViewR vs WorkOS: at a glance
| Feature | dockViewR | WorkOS |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 8.8 |
| Sparks · 30d | 0 | 3 |
| Top themes | shiny, htmlwidgets, ui-layout, javascript-bindings | identity, agent-auth, scim, developer-tools |
| Last editorial update | 1h ago | 21h ago |
| Website | Visit → | — |
What is dockViewR?
Draggable dock panels for Shiny, learning that layout state belongs on the client
dockViewR wraps the dockview JavaScript library so Shiny apps can offer draggable, splittable, tabbed panel layouts — the IDE arrangement, driven from R. Three releases since May 2025 have taken it from a working widget to one with a proper server-side control surface: panels can be added, removed, selected and moved from the server, and the dock exposes a reactive proxy.
What is WorkOS?
WorkOS is building the identity layer for agents while quietly making it easy to switch to it.
WorkOS sells enterprise-readiness infrastructure — SSO, SCIM directory sync, and AuthKit — to application developers. The recent work runs on two tracks. One is a fast-moving agent stack: agent identities registering through an open protocol, a proxy that calls third-party APIs so applications never hold user tokens, and Atlas, an AI coworker that is an end-user product rather than a developer primitive. The other is adoption and developer experience, including a local API for CI/CD testing and a reversible SCIM migration bridge.
dockViewR vs WorkOS: editorial side-by-side
dockViewR
0.0INFRA · APIS
Draggable dock panels for Shiny, learning that layout state belongs on the client
◆ Current state
dockViewR wraps the dockview JavaScript library so Shiny apps can offer draggable, splittable, tabbed panel layouts — the IDE arrangement, driven from R. Three releases since May 2025 have taken it from a working widget to one with a proper server-side control surface: panels can be added, removed, selected and moved from the server, and the dock exposes a reactive proxy.
◆ Where it's heading
The design has been converging on the standard htmlwidgets pattern, and 0.3.0 is where it commits. Earlier releases routed panel-id checks through Shiny inputs, which meant the state was stale until the next reactive flush and forced awkward workarounds when manipulating the dock inside observeEvent(). Moving those checks to the browser and adding dock_view_proxy() drops that class of bug entirely, at the cost of a breaking API change and a dev-mode option for surfacing the warnings.
◆ Prediction
Having taken one breaking change to reach the proxy idiom, the natural follow-on is filling out the proxy surface so every panel operation is reachable through it.
WorkOS
8.8INFRA · APIS
WorkOS is building the identity layer for agents while quietly making it easy to switch to it.
◆ Current state
WorkOS sells enterprise-readiness infrastructure — SSO, SCIM directory sync, and AuthKit — to application developers. The recent work runs on two tracks. One is a fast-moving agent stack: agent identities registering through an open protocol, a proxy that calls third-party APIs so applications never hold user tokens, and Atlas, an AI coworker that is an end-user product rather than a developer primitive. The other is adoption and developer experience, including a local API for CI/CD testing and a reversible SCIM migration bridge.
◆ Where it's heading
The agent releases fit together as one bet: if agents are going to act on users' accounts, someone has to issue their identities and hold their credentials, and WorkOS is positioning to be that party in both cases. What is notable is the pairing with go-to-market plumbing. A reversible SCIM proxy with zero downtime and safe rollbacks is not a capability story, it is a switching-cost story, and shipping it alongside the agent work suggests confidence that the platform is worth migrating onto.
◆ Prediction
Expect the agent identity and token custody pieces to converge into a single documented stack, since Pipes and Agent Registration currently solve adjacent halves of the same problem. Atlas remains the thinnest-described release and the least clear in intent.
Alternatives to dockViewR 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 dockViewR or WorkOS.
traits.build
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
rwasm
The toolchain that gets R packages into the browser is optimising for payload size, not features.
Fail2Ban
Fail2Ban finally ships 1.1.1 after 14 months in beta, with a botched deb package on the way out the door
plogr
A logging header for Rcpp packages that sat untouched for nine years, then changed how it switches on
RNifti
The C++ layer under R's neuroimaging stack, closing the gaps where images stopped acting like arrays
See all dockViewR alternatives → · See all WorkOS alternatives →
Recent activity from dockViewR and WorkOS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoWorkOSMigrate SCIM Connections with SCIM Bridge
- 3d agoWorkOSAccepted invitations count as email verification
- 10d agoWorkOSPipes Token Proxy ⚡
- 12d agoWorkOSAtlas: Your AI Coworker ⚡
- 12d agoWorkOSAgent Registration ⚡
- 17d agoWorkOSTesting WorkOS in CI/CD
- 8mo agodockViewRReactive proxy replaces stale input-based panel checks
- 1y agodockViewRServer-side panel control and add/remove tracking
- 1y agodockViewRFirst CRAN release of the dockview panel widget
Frequently asked questions
What is the difference between dockViewR 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 3 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 dockViewR 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 3 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 dockViewR?
Top dockViewR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dockViewR alternatives" section above for the current picks, or visit /alternatives/dockviewr 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.