Prowler
Prowler's assistant stopped explaining findings and started deciding what to do with them.
Comparison · Infra & APIs
Knock vs nfs-ganesha
A side-by-side editorial comparison of Knock and nfs-ganesha — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs nfs-ganesha: at a glance
| Feature | Knock | nfs-ganesha |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | notification infrastructure, data sources, agent interface, workflow primitives | nfs, storage, grpc, rdma |
| Last editorial update | 4h ago | 23h ago |
| Website | — | Visit → |
What is Knock?
Knock is pulling every customer-data source into notifications, then putting an agent on top.
Knock is a notification infrastructure layer, and the last two months have gone into two things: widening what can trigger a workflow, and making the resulting data legible. Amplitude and Clay both landed as first-class data sources, so product events, cohort changes and enriched CRM rows now drive messaging directly rather than through customer-written glue. The workflow engine gained a wait-for-event primitive, and the template editor was rebuilt around block editing.
What is nfs-ganesha?
NFS-Ganesha is burning through major versions to migrate management onto gRPC
Four major versions shipped in roughly six weeks. The common thread across 12.0, 13.0 and 14.0 is gRPC: management and statistics functionality is being ported off DBUS onto a gRPC interface, expanding each release. Version 14.0 also landed XCOPY server-side copy and clustered quality of service, and RDMA support gained rpcbind registration. Version 11.0 folded rpc.statd into the server itself.
Knock vs nfs-ganesha: editorial side-by-side
Knock
6.3INFRA · APIS
Knock is pulling every customer-data source into notifications, then putting an agent on top.
◆ Current state
Knock is a notification infrastructure layer, and the last two months have gone into two things: widening what can trigger a workflow, and making the resulting data legible. Amplitude and Clay both landed as first-class data sources, so product events, cohort changes and enriched CRM rows now drive messaging directly rather than through customer-written glue. The workflow engine gained a wait-for-event primitive, and the template editor was rebuilt around block editing.
◆ Where it's heading
The shape is a product moving up from delivery mechanics toward the surrounding workflow. Sources reduce the integration code a customer writes before Knock is useful; the agent layer reduces the reporting work after. Category and tag management being pulled into dedicated dashboard pages is the housekeeping that follows: the primitives got numerous enough to need their own administration surface.
◆ Prediction
Expect the data-source list to keep growing along the same lines — warehouse and product-analytics tools that already hold the user state Knock needs — and for the agent to be given more of the dashboard's read surface.
nfs-ganesha
6.3INFRA · APIS
NFS-Ganesha is burning through major versions to migrate management onto gRPC
◆ Current state
Four major versions shipped in roughly six weeks. The common thread across 12.0, 13.0 and 14.0 is gRPC: management and statistics functionality is being ported off DBUS onto a gRPC interface, expanding each release. Version 14.0 also landed XCOPY server-side copy and clustered quality of service, and RDMA support gained rpcbind registration. Version 11.0 folded rpc.statd into the server itself.
◆ Where it's heading
Two migrations are running in parallel - management moving from DBUS to gRPC, and external daemons like rpc.statd being absorbed into the server - both of which reduce the number of moving parts an operator has to deploy alongside Ganesha. The unusually fast major-version cadence suggests version numbers are tracking integration milestones rather than compatibility promises.
◆ Prediction
Expect the remaining DBUS-based management surface to finish its move to gRPC, and clustered quality of service to gain the configuration and monitoring surface the other subsystems already have. RDMA looks like the next area due for attention given the recent rpcbind work.
Alternatives to Knock and nfs-ganesha
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.
ESPHome
ESPHome's August beta opens while the July line keeps absorbing hardware fixes.
Cronicle
Cronicle has spent 2026 hardening the paths that let a scheduler run arbitrary commands
Merge
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
Jackett
Jackett ships daily, and every release is trackers chasing sites that moved.
k0s
k0s keeps four Kubernetes branches patched in lockstep, one backport at a time.
See all Knock alternatives → · See all nfs-ganesha alternatives →
Recent activity from Knock and nfs-ganesha
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoKnockCategory + tag management
- 7d agoKnockAmplitude data source
- 8d agonfs-ganeshaMore gRPC commands and RDMA rpcbind registration
- 10d agonfs-ganeshaNFS-Ganesha 14.0 adds XCOPY and clustered quality of service ⚡
- 14d agoKnockAnalytics in the Knock agent ⚡
- 15d agoKnockWait for event function
- 16d agoKnockClay data source
- 19d agonfs-ganeshagRPC statistics collection expands
- 21d agoKnockRedesigned template editor
- 25d agonfs-ganeshaMore DBUS statistics ported to gRPC
- 1mo agonfs-ganeshaLock split cuts PUTFH/OPEN contention; configurable fd limit
- 1mo agonfs-ganesharpc.statd integrated into the server
Frequently asked questions
What is the difference between Knock and nfs-ganesha?
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.
Is Knock better than nfs-ganesha?
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.
What are the best alternatives to Knock?
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.
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.