Make the Computation VanishMake theComputationVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanishVanish
Skip to demoInstall Vanish
`curl -fsSL https://vanishcompute.com/install.sh | bash`
The first run in a repository uploads and hashes your tree, so on a large one it takes a while — about a minute and a half on a 27 GB tree. After that Vanish adds roughly a second to a command in a normal repository.
V / COMPUTE● DEMO CONSOLE
AWithout Vanish
$ npm test
✔ local command completes
✔ worker command completes first
✔ battery drains during execution
✔ replay restores initial state
✔ headline vanishes and returns
ℹ pass 5 ℹ fail 0
Your Laptop CPU
historycomputing
cpu0
cpu1
cpu2
cpu3
processnoderunning
Batteryillustrative
BWith Vanish
$ vanish npm test
✔ local command completes
✔ worker command completes first
✔ battery drains during execution
✔ replay restores initial state
✔ headline vanishes and returns
ℹ pass 5 ℹ fail 0
Your Laptop CPU
historylight activity
cpu0
cpu1
cpu2
cpu3
processvanishready
Batteryillustrative
Vanish Worker CPU
historycomputing
cpu0
cpu1
cpu2
cpu3
processnoderunning
Output captured from this demo’s five Node tests; durations omitted. Animation is illustrative, not a Vanish benchmark.
01 / SEND
Start where you are.
Run from your repository, including uncommitted source files.
02 / RUN
Give the work room.
Managed Linux compute runs the command. Output streams to your terminal.
03 / REVIEW
Bring back what matters.
Inspect the output files locally, then choose which changes to apply.