testthat
testthat now ships a reporter built for the coding agent running the tests.
A side-by-side editorial comparison of Depot and nfs-ganesha — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Depot | nfs-ganesha |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | ci-cd, build-acceleration, test-analytics, source-control | nfs, storage, grpc, rdma |
| Last editorial update | 1d ago | 3h ago |
| Website | — | Visit → |
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
Depot has spent the last month building outward from build acceleration. Test results went generally available with JUnit ingest, org-wide flaky and slow test analytics, and timing-based shard balancing. Underneath that, Depot Metal moved CI and Sandboxes onto bare-metal microVMs the company controls end to end, and Depot Code entered private beta as a diskless git server backed by blob storage. The smaller releases fill in the surrounding surface: Tailscale access to private networks, GitLab OIDC, Datadog CI Visibility, stacked pull requests, and macOS 26 runners on M4.
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.
Depot has spent the last month building outward from build acceleration. Test results went generally available with JUnit ingest, org-wide flaky and slow test analytics, and timing-based shard balancing. Underneath that, Depot Metal moved CI and Sandboxes onto bare-metal microVMs the company controls end to end, and Depot Code entered private beta as a diskless git server backed by blob storage. The smaller releases fill in the surrounding surface: Tailscale access to private networks, GitLab OIDC, Datadog CI Visibility, stacked pull requests, and macOS 26 runners on M4.
Each layer Depot adds is one it previously rented — compute from cloud runners, source hosting from GitHub, test insight from nothing at all. Owning the storage and hypervisor tiers is what makes the performance claims possible, and owning test data is what turns a build accelerator into something that reports on the pipeline rather than just running it faster. The pattern suggests Depot is positioning as the full CI platform, with speed as the entry point rather than the product.
Depot Code should move from private to open beta with tighter Depot CI integration, since a git server the company controls is what makes source-aware caching and test selection possible. Expect the test analytics to grow toward selecting which tests to run, not only how to split them.
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.
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.
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.
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 Depot or nfs-ganesha.
testthat now ships a reporter built for the coding agent running the tests.
EasyBuild opened itself to third-party plugins and went all-in on AMD GPUs
Casdoor ships a version per commit, and this week's commits are org-boundary checks
NetBox spent 4.6's patch cycle paying down GraphQL query cost, release after release
Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
See all Depot 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. Depot 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. Depot 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 Depot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Depot alternatives" section above for the current picks, or visit /alternatives/depot 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.