incident.io
Nexus does the diagnosis; the rest is on-call plumbing
Comparison · Infra & APIs
Depot vs Split.io
A side-by-side editorial comparison of Depot and Split.io — release velocity, themes, recent moves, and the top alternatives to consider.
Depot vs Split.io: at a glance
| Feature | Depot | Split.io |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 0.6 |
| Sparks · 30d | 1 | 0 |
| Top themes | ci-cd, build-acceleration, test-analytics, source-control | feature-flags, harness-integration, policy-as-code, pipelines |
| Last editorial update | 1d ago | 3mo ago |
| Website | — | Visit → |
What is Depot?
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.
What is Split.io?
Split FME's March releases pull feature flags fully into the Harness DevOps platform.
Split.io now ships under the Harness Feature Management & Experimentation (FME) brand, and the substantive activity is captured in the rolled-up release-notes page rather than per-release entries. The March 2026 wave landed three real ships: Policy As Code (OPA) for FME Feature Flags, Feature Flag Archiving with RBAC and pre-archive checks, and the GA of FME steps in Harness pipelines covering full flag lifecycle management. The rest of the recent feed is scraper artifacts — page chrome captured as titles.
Depot vs Split.io: editorial side-by-side
Depot
6.3INFRA · APIS
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Split.io
0.6INFRA · APIS
Split FME's March releases pull feature flags fully into the Harness DevOps platform.
◆ Current state
Split.io now ships under the Harness Feature Management & Experimentation (FME) brand, and the substantive activity is captured in the rolled-up release-notes page rather than per-release entries. The March 2026 wave landed three real ships: Policy As Code (OPA) for FME Feature Flags, Feature Flag Archiving with RBAC and pre-archive checks, and the GA of FME steps in Harness pipelines covering full flag lifecycle management. The rest of the recent feed is scraper artifacts — page chrome captured as titles.
◆ Where it's heading
FME is becoming a first-class part of the Harness DevOps surface rather than a standalone feature-flag tool. Pipeline-native flag operations, policy-as-code governance, and archiving as a managed lifecycle state all reflect a single direction: feature flags as a governed, audited, and pipeline-integrated component of the deployment system. The standalone Split UX is fading into Harness conventions.
◆ Prediction
Expect more Harness-platform conventions to land on FME — RBAC unification, environments and pipelines parity, OPA policy templates shipped out of the box, and observability tying flag changes back into deploy-failure/MTTR dashboards. Standalone-Split UX surfaces will likely be retired further.
Alternatives to Depot and Split.io
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 Split.io.
werf
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
ZoneMinder
1.38.4 is a security release in all but name, closing ACL gaps across the API.
Infisical
PAM and PKI now take up most of the lines in Infisical's release notes.
Biome
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
See all Depot alternatives → · See all Split.io alternatives →
Recent activity from Depot and Split.io
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoDepotmacOS 26 is now the default macOS version for GitHub Actions runners
- 9d agoDepotDepot CI now supports native GitHub stacked pull requests
- 14d agoDepotTest results are now generally available ⚡
- 22d agoDepotAI analysis available for all Depot CI workflows and jobs
- 28d agoDepotSplit CI test suites with historical timing data (beta)
- 1mo agoDepotDepot CI now supports Tailscale
- 4mo agoSplit.ioScrape artifact: docs nav element
- 4mo agoSplit.ioMarch 2026 FME release roll-up ⚡
- 4mo agoSplit.ioScrape artifact: page anchor element
- 5mo agoSplit.ioScrape artifact: tag list
- 5mo agoSplit.ioScrape artifact: edit-page footer link
- 5mo agoSplit.ioScrape artifact: copyright footer
Frequently asked questions
What is the difference between Depot and Split.io?
They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 6.3 vs 0.6), 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 Split.io?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 6.3 vs 0.6), 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 Split.io?
Top Split.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Split.io alternatives" section above for the current picks, or visit /alternatives/split for the full list with editorial commentary on each.