npm ci works. it just doesn't scale well.

Every run reinstalls from scratch. That adds up fast.

same packages, same wait

Your lockfile hasn't changed. But your CI still downloads and installs everything from scratch on every push.

the registry is a live dependency

Every live npm ci is a pull from a public registry. Rate limits on recurring runs can silently break your build.

CI minutes add up

Teams running dozens of parallel builds burn hours waiting for dependency that are identical across runs.

built for teams that ship fast

One API call replaces your dependency install step on repeat builds.

Skip the reinstall

When your lockfile hasn't changed, a cache hit returns a pre-built archive. No reinstall, no registry round-trips.

Start free, scale when you need

The free plan covers small projects and evaluation. Upgrade to Solo or Team when your first-run build volume grows.

Pull from npm less. Stay safer.

Cache hits skip the registry entirely. Your pipeline extracts a known archive instead,shrinking the window where a compromised package could reach your build at install time.

Hit rate visibility

Track cache hits, first-run builds, and API activity from the dashboard to tune your pipeline setup.

One API call to integrate

Send manifests from your CI runner, download and extract the archive. Works with any CI system.

x64 and arm64

Native support for both architectures across Node.js Docker images. The cache key includes architecture and image digest.

how it works

Drop it into any CI workflow in under an hour.

1

Create your account

Sign up and generate an access token from the dashboard.

2

Send your manifests

Send your package.json, lockfile, Node version, and architecture.

3

We resolve the cache

Get your existing archive on a cache hit. On a first-time build we run npm ci.

4

Extract and continue

Download a tar, extract it, and run the rest of your pipeline as normal.

Full walkthrough

cache hit vs. first-run build

Both paths start the same. We determine if there is a cached build.

01 CI sends manifests + metadata

02 We determine if there is a cached build

cache check

Cache hit — repeat build

03 Existing archive found

04 CI downloads and extracts archive

First-run build — cache miss

03 No archive found → we run npm ci

04 Result archived

05 CI downloads and extracts archive

First-run builds count against your plan limits. Repeat builds are always free.

npm ci, but cached.

npm ci works. it just doesn't scale well.

built for teams that ship fast

how it works

cache hit vs. first-run build

Your next build should be faster.