Solidus Auth

Solidus Auth vs WorkOS

WorkOS turns enterprise SSO into a $125/month line item per customer connection; Solidus's DID-based credential carries the same federation handshake at protocol cost — but WorkOS ships this today, self-serve, and Solidus's version is tested code behind an admin gate.

Solidus is a public testnet: no mainnet, no token, no external audit, and no paying customer. Every claim below is checkable; none of them are a substitute for the certifications an incumbent already holds.

What WorkOS does better

Where Solidus is different

Side by side

Solidus compared with WorkOS. Rows marked as won by WorkOS are noted in the final column.
FeatureSolidusWorkOS
What it actually isTestnet-anchored OID4VP verifier + Solid-OIDC/DPoP provider"Enterprise readiness in a box" — SSO + SAML + SCIM + Directory + Audit Logs as composable services
SSO / SAML connection pricing$0/connection — the credential carries its own handshake$125/connection/month (volume tiers to $65)
Free tierTestnetAuthKit free to 1M MAUWorkOS wins
Audit LogsNot offered$125/mo + $99/mo per 1M eventsWorkOS wins
SSO / SAML / SCIM / directory syncNone shipped as a self-serve productShipped, mature, self-serveWorkOS wins
Where the user directory livesWith the user — a W3C VC they holdIn your WorkOS-connected IdP + WorkOS's directory sync layer
ArchitectureOpen protocol — did:solidus, W3C-registeredCentralized, proprietary SaaS
Self-serve signup for the differentiating featurePlain OIDC: yes. Credential verifier: admin-gated, no self-serve signupYes, fully self-serveWorkOS wins

Check it yourself

curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 | jq '{state,merged,merged_at}' → merged 2026-07-04 — the DID method behind the $0/connection claim, registered and checkable in under a minute.

Compare the receipts, not the pitch.