Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of Knock and nfs-ganesha — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Knock | nfs-ganesha |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | nfs, storage, grpc, control-plane |
| Last editorial update | 14h ago | 1d ago |
| Website | — | Visit → |
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
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.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
Two arcs run in parallel. The infrastructure lane is buying enterprise credibility — roles, passkeys, audit-grade permissions — the checklist items that decide procurement rather than daily use. The data lane keeps widening what can trigger a workflow: product analytics from Amplitude, enriched rows from Clay, internal Slack channels as a destination. Together they push Knock from a notification API toward the messaging control plane, with the agent as the layer that explains what the plane did.
Expect the roles work to continue into audit logs or scoped API keys, since granular permissions without an activity trail is an incomplete enterprise story. More data sources are likely on the same cadence, with the CRM and warehouse categories the obvious remaining gaps.
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.
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.
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.
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 Knock or nfs-ganesha.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all Knock alternatives → · See all nfs-ganesha alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Knock and nfs-ganesha are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock and nfs-ganesha are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.
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.