Always deployed.Released when you’re ready.

Keep your bundler. Add withZephyr().

Vite, Rsbuild, Rspack, webpack, Rollup, Parcel, Astro, Nuxt or TanStack Start: the plugin goes into the config you already have. Run your normal build and it deploys.

Only what changed goes up.

Every file is fingerprinted. Zephyr asks the edge what it already has and uploads the rest, so a one-line fix doesn’t re-send your whole app.

Tags follow builds. Environments wait for you.

Every build from every branch and every teammate (human or agentic) keeps a permanent URL to share and test. A tag like latest follows new builds on main by itself. production moves only when someone releases, and moving it back is a rollback.

Every attempt is a live preview.

Coding agents build and deploy like anyone else on the team. Each attempt gets its own URL, a tag like ai follows the newest one, and open previews reload themselves when it moves.

Nothing reaches users until someone releases it.

The team reviews what the agent tried and releases the one that works. When a release goes wrong, whoever spots it rolls back with the same move in reverse: no rebuild, no re-upload.

Give your agents the Zephyr playbook.

Zephyr Skills teach Claude Code, Cursor, Codex and OpenCode how versions, tags, environments and remotes work. The scaffolder returns a JSON receipt an agent can check instead of guessing.

$npx skills add https://github.com/ZephyrCloudIO/skillsCopy npx skills add https://github.com/ZephyrCloudIO/skills

Every team ships its own piece.

With Module Federation, checkout, catalog and search are separate apps with separate owners, people and agents alike. Each deploys on its own schedule, and the shell loads them together as one product.

Each environment loads its own versions.

Remotes resolve by environment, tag or semver range, like zephyr:checkout.shop.acme@staging. Staging runs the newest checkout while production stays on the last release, and releasing one remote doesn’t rebuild the shell or anything else.

Guardrails for many hands.

Protected environments only take builds from their members, so an agent’s build lands in staging until someone on the team releases it. Roles decide who can release, and every deploy and release is logged with who did it.

One build lands on every environment’s edge.

Each environment can run on Zephyr Cloud or on your own Cloudflare, AWS, Fastly or Akamai account. A build uploads to all of them at once, and each edge only receives the files it doesn’t already have.

Releasing is still a pointer move.

The build is already on every edge, so releasing it to production on AWS or production-eu on Akamai is the same move as before: no rebuild, no re-upload. Each environment releases on its own schedule.

Switching clouds is a setting.

Point an environment at a different provider and the next build deploys there. No new pipeline, no migration project. Kubernetes and custom edges are available on Enterprise.

The same one line, whatever you build with.

Bundler plugins for Vite, Rsbuild, Rspack, webpack, Rollup, Parcel and Rolldown (beta). Integrations for Astro, Nuxt, Modern.js, Rspress, TanStack Start and Vinext (beta). Starters for Angular, Svelte, Solid, Ember, Nx and Turborepo.

Server rendering at the edge.

TanStack Start, Nuxt, Vinext, Nitro, Hono and Elysia deploy their server code alongside the static files. It runs on Cloudflare, Zephyr Cloud included, with every version in its own isolate, so previews and rollbacks work for SSR too.

Mobile, without the app store wait.

React Native apps built with Re.Pack or Metro load their mini-apps from the edge. Release a new version and installed apps pick it up on their next update check.