incident.io
Nexus does the diagnosis; the rest is on-call plumbing
A side-by-side editorial comparison of Biome and Depot — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Biome | Depot |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | lint-rules, markdown-support, framework-coverage, css-formatter | ci-cd, build-acceleration, test-analytics, source-control |
| Last editorial update | 2h ago | 1d ago |
| Website | Visit → | — |
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
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.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
The rule set is widening along two axes at once: frameworks and file types. Framework rules are now specific enough to argue about Svelte runes rather than generic JavaScript, and CSS handling has pushed into HTML attributes and registered custom properties. The larger move sits in 2.5.8's PR list rather than its changelog — a markdown linter, a markdown rule generator, a markdownlint rule source, a two-phase markdown parser, and a first rule in useTopLevelHeading, none of it documented for users yet.
Markdown linting looks close enough to ready that it should appear in the changelog proper rather than the PR list, most likely as nursery rules in the next minor.
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.
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 Biome or Depot.
Nexus does the diagnosis; the rest is on-call plumbing
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
1.38.4 is a security release in all but name, closing ACL gaps across the API.
PAM and PKI now take up most of the lines in Infisical's release notes.
DNSControl is rewriting its record internals in public, one release candidate at a time
Fission's release feed carries only RC tags, and none of them say what shipped
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 6.3 vs 5.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 6.3 vs 5.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.
Top Biome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Biome alternatives" section above for the current picks, or visit /alternatives/biome for the full list with editorial commentary on each.
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.