From origin to edge.
One fast path for public npm packages and immutable first-party releases—resolved at the source, routed through Cloudflare, and delivered with integrity intact.
❯npm install zod --registry=https://npm.lemonize.cyou
resolvezod@latest from npmjs.org
routetarball through npm.lemonize.cyou
edgecache-ready · integrity preserved
✓added 1 package in 642ms
UPSTREAM
npmjs.org
GATEWAY
Cloudflare
ARCHIVE
none
ORIGIN
registry.npmjs.org
EDGE GATEWAY
npm.lemonize.cyou
UPSTREAM ARCHIVE
None — cache only
The delivery path
A shorter route to the package.
Lemonize is a pull-through gateway. The first request still reaches npm; cacheable responses then become available from Cloudflare's network for subsequent requests.
- 01 / 03
Request
Point npm at the Lemonize gateway. Package names, versions, and lockfiles keep working as expected.
- 02 / 03
Resolve
A cache miss is resolved from the public npm registry and tarball URLs are routed back through Lemonize.
- 03 / 03
Deliver
Eligible metadata and tarballs are cached by Cloudflare and served from the edge on later requests.
npm / pull-through CDN
Use npm. Change one URL.
npm install zod --registry=https://npm.lemonize.cyouPackage metadata is requested from npm, rewritten so tarballs return through the same hostname, and streamed to the client without an upstream R2 mirror.
Cache misses depend on npm's response time. Edge hits avoid that origin round trip; no claim of a fixed millisecond latency is made.
Pull-through, not a mirror
New packages are fetched on demand. Lemonize does not keep an R2 archive of upstream npm tarballs.
Integrity stays intact
Upstream package metadata and integrity fields are preserved while download URLs are safely rewritten.
A native registry too
Install immutable first-party packages today. Namespace-scoped publishing remains gated until the production write cutover.