Latticev2.0 / 01 — 09
Launch · November 2027

Builds that remember

Lattice 2.0 caches every step of every build across your whole team, so nothing compiles twice.
Release2.0.0
Runs onAny CI, any laptop
LanguagesTS, Go, Rust, Python
LicenseApache 2.0
Latticev2.0 / 02 — 09
The problem
Your CI rebuilds the same 94% of the repo on every single push.
Median across 310 monorepos that ran Lattice 1.x, Q3 2027
Lattice / faster on a 2,400-package monorepov2.0 / 03 — 09
Cold builds
11×
faster on a 2,400-package monorepo
The first build on a new branch pulls from the team cache instead of starting from scratch.
Lattice benchmark suite, 16-core runners
Latticev2.0 / 04 — 09
Two commands
Drop it into the CI you already have
No new runners, no config rewrite. Lattice wraps the build you run today.
build step
# install once
$ npm i -g @lattice/cli
 
# wrap your build
$ lattice run "pnpm build" --remote team
 
hashing 2,418 tasks
cache 2,301 hits · 117 misses
built 117 tasks in 41.8 s
 
✓ done in 52.3 s (was 9 min 34 s)
Latticev2.0 / 05 — 09
How it works
Every task is an address
01Hashinputs, env and toolchain
02Look uplocal, then the team cache
03Fetch or buildonly what changed runs
04Shareresults signed and uploaded
Same inputs, same address: a result built once anywhere is reused everywhere.
Latticev2.0 / 06 — 09
What's new in 2.0
Faster, and smaller
Cache hit rate96.2%up from 81% in 1.x
Lookup4 ms p50regional edge cache
Storage−63%chunked, deduplicated
Remote execBetafan out to 512 workers
Self-hostOne binaryS3, GCS or disk
Latticev2.0 / 07 — 09
Lattice Cloud
One cache, every office
Replicated to six regions. A build in Berlin warms the cache for the morning in Austin.
Latticev2.0 / 08 — 09
“Our main branch used to take nine minutes to go green. It takes fifty seconds now, and the bill went down.”
Priya RamanPlatform lead, Northwind Labs
Latticev2.0 / 09 — 09
Available today
Stop building twice
lattice.example/2npm i -g @lattice/cli
FreeUp to 5 seats
Team$12 / seat
Docslattice.example/docs
Talk to ushi@lattice.example