evaluate
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
Comparison · Infra & APIs
Depot vs watcher
A side-by-side editorial comparison of Depot and watcher — release velocity, themes, recent moves, and the top alternatives to consider.
Depot vs watcher: at a glance
| Feature | Depot | watcher |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | ci-cd, build-acceleration, test-intelligence, git-hosting | filesystem-events, r6, build-portability, c-bindings |
| Last editorial update | 13h ago | 1h ago |
| Website | — | Visit → |
What is Depot?
Depot keeps absorbing the CI stack — tests, networking, runners, now its own git host.
Depot has moved well past build caching. Test results reached general availability in July with org-wide flaky, slow, and recurring failure analytics plus timing-based shard splitting; Sherlock's AI analysis became available on any run rather than only failed ones; and CI jobs can join a Tailscale tailnet to reach private services. The runner fleet now defaults to macOS 26 on M4 hardware, Depot CI understands GitHub stacked pull requests, and Depot Code — a diskless git server backed by blob storage — entered private beta.
What is watcher?
watcher is a thin filesystem-events binding whose releases are mostly build work.
The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.
Depot vs watcher: editorial side-by-side
Depot
6.3INFRA · APIS
Depot keeps absorbing the CI stack — tests, networking, runners, now its own git host.
◆ Current state
Depot has moved well past build caching. Test results reached general availability in July with org-wide flaky, slow, and recurring failure analytics plus timing-based shard splitting; Sherlock's AI analysis became available on any run rather than only failed ones; and CI jobs can join a Tailscale tailnet to reach private services. The runner fleet now defaults to macOS 26 on M4 hardware, Depot CI understands GitHub stacked pull requests, and Depot Code — a diskless git server backed by blob storage — entered private beta.
◆ Where it's heading
The pattern is absorbing each adjacent piece of the pipeline that Depot's position already gives it data about. It runs the builds, so it owns test timing, so it can balance shards; it runs the jobs, so it can diagnose them; it hosts the runners, so it can wire private networking into them. Depot Code extends the same logic upstream to source hosting, which would close the loop between repository and runner. A quieter parallel thread keeps moving SDK- and dashboard-only settings into the CLI, stated explicitly as making projects configurable by agents and scripts.
◆ Prediction
Depot Code widening past private beta and binding more tightly to CI is the move the rest of the window sets up. The test work is also positioned to go from reporting to selection — skipping tests a change cannot affect — since Depot now holds the timing and failure history that would require, though the entries stop short of saying so.
watcher
0.0INFRA · APIS
watcher is a thin filesystem-events binding whose releases are mostly build work.
◆ Current state
The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.
◆ Where it's heading
The API is deliberately small and appears finished; the work that remains is making the C dependency install cleanly everywhere. Dropping cmake follows the same move nanonext made, which is not a coincidence — both come from the same author and both are aiming at environments where installing a build system is not an option.
◆ Prediction
With cmake gone and the bundled library current, further releases are most likely to track libfswatch upstream rather than extend the R interface.
Alternatives to Depot and watcher
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 watcher.
carrier
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
gh
gh spent its last two releases making failures and interruptions recoverable.
checkhelper
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
dockerfiler
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
crane
Crane is turning into the table-and-plot layer for Roche's clinical output stack.
See all Depot alternatives → · See all watcher alternatives →
Recent activity from Depot and watcher
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoDepotmacOS 26 is now the default macOS version for GitHub Actions runners
- 11d agoDepotDepot CI now supports native GitHub stacked pull requests
- 14d agoDepotSet cache retention when creating a project with --cache-policy-keep-days
- 15d agoDepotView and edit project details from the Depot CLI
- 16d agoDepotTest results are now generally available ⚡
- 24d agoDepotAI analysis available for all Depot CI workflows and jobs
- 1mo agowatchercmake dropped from the bundled library build
- 3mo agowatcherBundled libfswatch updated to 1.20.1
- 8mo agowatcherWindows CPU usage fix for sub-second latency
- 1y agowatcherSystem libfswatch found in non-standard locations
- 1y agowatcherMultiple paths per watcher, and older Windows builds fixed
- 1y agowatcherAccessor methods replace public Watcher fields
Frequently asked questions
What is the difference between Depot and watcher?
They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Depot better than watcher?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Depot?
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.
What are the best alternatives to watcher?
Top watcher alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "watcher alternatives" section above for the current picks, or visit /alternatives/watcher for the full list with editorial commentary on each.