CRUMB a card from devarno-cloud

Not a Build Orchestrator, Not a Cache

nestr beginner 3 min read

What this means for you

Two wrong frames, both retired. Nestr is not a build orchestrator: those schedule tasks and cache build outputs. And nestr is not a dependency cache either: the 2026-05 version of this card said “Nestr caches the dependency tree itself”, which is the “pellets-as-compression” drift the north star warns against. Nestr is a package distribution layer focused on supply-chain security. Sources: landing src/lib/constants.ts:247-249 @cb59f69; nestr-tools docs/north-star/intent.md:28,45-49 @b8f0585.

The pitch

The FAQ answer, verbatim: “Nx and Turborepo are build orchestrators: they schedule tasks and cache build outputs. Nestr is not a build orchestrator. It is a package distribution layer focused on supply-chain security: content-addressed packages, designed to be signed and transparency-logged, that never run code while installing.” Speed is a side effect of content addressing and zstd, not the point (intent.md:28).

Who it’s for

The evaluator who hears “we already have a build cache” and needs the one-sentence reason nestr is a different layer, without overclaiming features that are not yet available.

Proof points

  • Different question answered: “can a compromised maintainer run code on our machines?”, not “can we skip work?”.
  • Drift watch 1 (intent.md:45-49): optimising ratio or cache hits while signature, sandbox and log work sits unenforced is named as a failure mode, so cache framing is off-message.
  • The old “Perch is a monitoring stack orchestrators don’t ship” differentiator is dropped: Perch is pre-production.
  • The FAQ names the two tools only to define the category boundary; it makes no claim that nestr replaces or beats them.
quadrantChart
title Where nestr sits
x-axis "Skips work" --> "Proves what is installed"
y-axis "Build layer" --> "Package distribution layer"
quadrant-1 "Nestr's lane"
quadrant-2 "Package caches"
quadrant-3 "Build orchestrators"
quadrant-4 "Supply-chain scanners"
"Build orchestrators": [0.2, 0.2]
"Dependency caches": [0.25, 0.75]
"Nestr": [0.85, 0.85]

neighbors on the map