← Back to home
Comparison · Infra & APIs

nfs-ganesha vs WorkOS

A side-by-side editorial comparison of nfs-ganesha and WorkOS — release velocity, themes, recent moves, and the top alternatives to consider.

nfs-ganesha vs WorkOS: at a glance

Featurenfs-ganeshaWorkOS
SectorInfra & APIsInfra & APIs
Velocity score6.38.8
Sparks · 30d12
Top themesnfs, storage, grpc, control-planeidentity, authentication, ai-agents, scim
Last editorial update1d ago14h ago
WebsiteVisit →

What is nfs-ganesha?

NFS-Ganesha is porting its management plane from DBUS to gRPC, four major versions in a month.

NFS-Ganesha is a user-space NFS server with pluggable FSAL backends for CEPH, GPFS and others. It is releasing major versions at an unusual rate — 12.0 through 15.1 since mid-July — and the connecting thread across all of them is gRPC: infrastructure first, then stats collection ported from DBUS, then more commands, then CacheMgr APIs and export management. Version 15.0 adds memory statistics and accounting alongside those APIs.

Read the full nfs-ganesha trajectory →

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.

Read the full WorkOS trajectory →

nfs-ganesha vs WorkOS: editorial side-by-side

N
nfs-ganesha
INFRA · APIS
6.3

NFS-Ganesha is porting its management plane from DBUS to gRPC, four major versions in a month.

◆ Current state

NFS-Ganesha is a user-space NFS server with pluggable FSAL backends for CEPH, GPFS and others. It is releasing major versions at an unusual rate — 12.0 through 15.1 since mid-July — and the connecting thread across all of them is gRPC: infrastructure first, then stats collection ported from DBUS, then more commands, then CacheMgr APIs and export management. Version 15.0 adds memory statistics and accounting alongside those APIs.

◆ Where it's heading

This is a control-plane migration carried out release by release in the open. Each version moves another slice of management surface onto gRPC — stats, exports, cache manager, a fake recall API for testing — while the data path work continues separately with XCOPY and clustered quality of service at 14.0. The 15.1 release extends ShowExports with a protocol summary and adds a gRPC FakeRecall API, which reads as filling in coverage rather than opening new ground. Note 15.0 and 15.1 are stamped seventy-nine seconds apart, so they were cut together rather than released as separate events.

◆ Prediction

Expect the remaining DBUS-era management commands to keep landing as gRPC APIs at this cadence. The open question these entries do not answer is whether DBUS is eventually removed or kept indefinitely alongside.

W
WorkOS
INFRA · APIS
8.8

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 nfs-ganesha 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 nfs-ganesha or WorkOS.

See all nfs-ganesha alternatives → · See all WorkOS alternatives →

Recent activity from nfs-ganesha and WorkOS

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agonfs-ganeshaShowExports gains a protocol summary; gRPC FakeRecall API added
  2. 1d agonfs-ganeshaMemory accounting and CacheMgr gRPC APIs
  3. 2d agoWorkOSAndroid SDK
  4. 2d agoWorkOSHigher quality sign-ups with email deliverability checks
  5. 5d agoWorkOSMigrate SCIM Connections with SCIM Bridge
  6. 6d agoWorkOSAccepted invitations count as email verification
  7. 13d agoWorkOSPipes Token Proxy
  8. 13d agonfs-ganeshaMore gRPC commands and RDMA rpcbind registration
  9. 15d agoWorkOSAgent Registration
  10. 15d agonfs-ganeshaXCOPY server-side copy and clustered quality of service
  11. 25d agonfs-ganeshagRPC expands with more stats collection
  12. 1mo agonfs-ganeshagRPC stats collection ported over from DBUS

Frequently asked questions

What is the difference between nfs-ganesha and WorkOS?

They serve adjacent needs but don't currently overlap on shipped themes. WorkOS is currently shipping more aggressively (velocity 8.8 vs 6.3), with 2 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is nfs-ganesha 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 6.3), with 2 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to nfs-ganesha?

Top nfs-ganesha alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nfs-ganesha alternatives" section above for the current picks, or visit /alternatives/nfs-ganesha 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.