announcementWhat vx is, and what it refuses to be
What vx is, and what it refuses to be
vx runs and caches your task graph, correctly, and nothing else. How a run works, and what will never be inside.
Hello, vx
vx runs your monorepo's tasks and caches them, on Bun, with nothing behind a paid cloud. Here it is in one picture and one run.
announcementvx runs your monorepo’s tasks and caches the results. It is built on Bun, and nothing sits behind a paid cloud.
flowchart LR D[find projects] --> G[one task graph] G --> K[a key per task] K --> R[run here] K --> X[or restore from the cache] style K stroke:#c6f84e,stroke-width:2px
Run it twice
Section titled “Run it twice”Four packages, each with a build (bun build) and a test
(bun test). Eight tasks:
$ vx run build test --all --force tasks 8 success · 8 total cache local 8↑ time 134ms
$ vx run build test --all cache local 8✓ time 21msThe second run finds every result in the cache, so nothing runs. Timed from outside, start-up included:
The table
| Run | Command | Fastest |
|---|---|---|
| cold | vx run build test --all --force |
158.1 ms |
| warm | vx run build test --all |
115.0 ms |
Min of 20 runs (median 170.9 ms cold, 138.8 ms warm) · Linux x64, 4 cores, Bun 1.4.4 · vx 0be0367 · 2026-10-23
Most of the warm 115 ms is Bun loading vx. The run itself reports 21 ms.
What you get, what you don’t
Section titled “What you get, what you don’t”| Where | What |
|---|---|
| Core | graph, keys, scheduler, local cache, running on this machine |
| Plugins | remote caches, remote execution, telemetry, CI summaries, lockfile keys |
| Never | a hosted dashboard, a daemon, a cloud you must buy into |
With no plugins, vx still runs and caches. You add a plugin by naming
it in .vx/workspace.ts.
- Quickstart: your first cached task, in a repo you already have.
- What vx is, and what it refuses to be.
- Benchmarks: vx, Turborepo, Nx and Vite Task on one graph, each in its own native config.
More at vznjs.github.io/vx.
Keep reading
announcementcorrectnessTurborepo, Nx and Vite Task undo your commit on a cache hit
Turborepo, Nx and Vite Task undo your commit on a cache hit
Commit a file that sits in a task’s output folder. On the next cache hit, Turborepo, Nx and Vite Task write the old copy back over it, and the run reports success.
sandboxA sandboxed task reads what it depends on, and nothing beside it
A sandboxed task reads what it depends on, and nothing beside it
A sandboxed task can read the outputs of the tasks it depends on, in any project, and never their sources. With hermetic: true it reads nothing of the machine you did not name.