carver
Get started
Static asset delivery

Cut your build down.
Ship only what changed.

Carver fingerprints, versions, and pushes your static assets to the edge on every deploy — with instant rollback if a release goes wrong.

$ carver push ./dist
→ fingerprinting 214 files
→ diff against last release: 12 changed
→ uploaded to edge (ams1, fra1, sjc1)
→ release v0.14.2 is live
$
zero-config CDN push content-hash versioning instant rollback framework agnostic
Why teams switch

Built for the last mile of a deploy

Most of what slows a release down happens after the build finishes. Carver handles that part so your pipeline doesn't have to.

01

Content-hash fingerprinting

Every asset is hashed on push, so browsers and CDNs cache aggressively without ever serving something stale.

02

Delta uploads

Only changed files leave your machine. A typical release moves a few megabytes, not the whole bundle.

03

One-command rollback

Every push is a named release. If something's wrong, point traffic at the last good one in under a second.

Get started

Three commands, first release

01

Install the CLI

npm install -g carver — or grab a static binary from the releases page.

02

Link a project

carver init writes a small config next to your build output directory.

03

Push a release

carver push ./dist fingerprints, diffs, and publishes — printing a shareable release URL.