JavaScript package registries
for teams that move fast

npm-compatible package delivery on infrastructure purpose-built for JavaScript. Faster installs, smaller payloads, and safer defaults, without changing the tools your team already uses.

A better registry

JavaScript packages are not idempotent artifacts; they form enormous, dynamic dependency graphs that affect every install, build, and deployment. Most registries are glorified S3 buckets designed to store files statically - not leveraging any understanding of dependent relationships or linking critical associative metadata.

Move fast
without changing your tools

vlt serves npm-compatible packages through infrastructure purpose-built for JavaScript package distribution. Fine-tuned caching, smaller payloads, and faster CI—all while remaining fully compatible with the tools your team already uses.

Installing registry packages

70% faster installing packages compared to traditional tools from the npm registry

Executing scripts

Run your package scripts with vlr, targeting a single project or an entire workspace

Cataloging dependencies

Organize your dependencies, and catalog them to keep your codebase simple

npm registry

$npminstallnext

⠋ resolving dependencies…

added 42 packages in 3.1s

vlt registry

$vltinstallnext

resolving dependencies ✓ >extracting files ✓

23 cache hits

75 requests

Done in 1.1s

$

How much could you save?

Estimate your monthly CI savings. Adjust your install volume to see how vlt compares to npm on GitHub Actions 4-core runners.

Installs / mo
100K
25k100k1.0M10M100M

How does vlt compare?

vltLowest~$1.6K
npm~$5.8K

Savings breakdown

ItemQuantityCost
CI compute saved~368 hrs / mo$353 /mo
Annualized× 12 mo$4.2K
Estimated savings / yrBased on npm-vs-vlt install times on GitHub Actions 4-core runner pricing.
~$4.2K

Ready to build
something extraordinary?