For developers and coding agents with static output already on disk.

Turn a build folder into latest and pinned URLs.

WGW Deploy is a CLI path for previews, repros, docs, dashboards, and agent output. Default deploys go from./dist to a publicwgw.lol URL. Every deploy also gives you an immutable pinned revision.

Read CLI docs Scan commands

local build outputlatest + pinned

$ npm run build
created dist/

$ npx wgw-deploy
prepare ./dist
upload changed files
latest https://careful-fall-mqstr7zz.wgw.lol/
pinned https://careful-fall-mqstr7zz--26704cb219eb67f3.wgw.lol/

Ship the artifact you already built.

Build static output

Use whatever already produces files: Vite dist, Astro dist, exported Next.js, docs, reports, dashboards, or one HTML file.

Deploy from the folder

Run the default command for dist, or pass --dir and --cwd when the output lives somewhere else.

Return both links

Send the latest URL for live review and the pinned URL when the exact files need to stay reachable.

Name it if it graduates

Assign a WGW subdomain or external custom hostname when a preview turns into something people should remember.

Clean it up

List local projects when you need state, then delete throwaway projects instead of leaving old URLs around.

The CLI surface is small enough to remember.

Use the default command when the artifact isdist. Add flags only when the folder, domain, output format, or lifecycle needs more precision.

Default deploy

npx wgw-deploy

Uses the dist folder in the current working directory and returns a latest URL plus a pinned revision URL.

Pick the output folder

npx wgw-deploy --dir ./public

Use this when the build output is not dist, or when the artifact is a folder of docs, reports, or static files.

Target another app

npx wgw-deploy --cwd /path/to/app --dir build

Projects are tied to cwd and deploy directory, so this keeps repeated deploys attached to the same tracked project.

Assign a domain

npx wgw-deploy --domain preview.example.com

Maps the current project to a WGW subdomain or external hostname. External domains point a CNAME at cname.wgw.lol.

Remove the domain

npx wgw-deploy --delete-domain

Returns the project to its generated wgw.lol domain and starts a fresh generated-project expiration window.

List local projects

npx wgw-deploy --list --json

Reads locally tracked projects, URLs, hashes, directories, and expiration state from the CLI project store.

Print the agent skill

npx wgw-deploy --skill

Gives coding agents the operating instructions for when to deploy, which URL to return, and what not to upload.

Delete the project

npx wgw-deploy --delete

Removes the locally tracked project and the remote project when a temporary preview has done its job.

One deploy leaves two links behind.

The latest URL is the moving pointer. The pinned URL is the fixed record. Use the one that matches the job instead of arguing about which file a reviewer saw.

Latest project URL

https://careful-fall-mqstr7zz.wgw.lol/

Use it for demos, review threads, docs, dashboards, and previews that should move forward with the next deploy.

Pinned revision URL

https://careful-fall-mqstr7zz--26704cb219eb67f3.wgw.lol/

Use it for bug reports, audits, evals, and handoffs where later deploys must not change the evidence.

A preview can get a real name when it stops being disposable.

Assign a WGW subdomain with a bare name, or assign an external hostname and point DNS at the CNAME target the CLI returns.

$ npx wgw-deploy --domain launch-preview
url https://launch-preview.wgw.lol/
pinned https://launch-preview--26704cb219eb67f3.wgw.lol/

$ npx wgw-deploy --domain docs.example.com --json
dns CNAME docs.example.com -> cname.wgw.lol

$ npx wgw-deploy --delete-domain

Agents need instructions they can execute.

WGW Deploy ships an agent skill so a coding agent can publish generated pages, repros, docs, dashboards, or reports without learning a hosting dashboard.

npx wgw-deploy --skill

Agent skill

npx wgw-deploy --skill

Markdown guide

https://deploy.wgw.lol/SKILL.md

LLM index

https://deploy.wgw.lol/llms.txt

Machine output

npx wgw-deploy --json

Prefer the CLI from the local machine that built the artifact.

Return both latest and pinned URLs when the CLI prints both.

Use the pinned URL for exact repros, audits, evals, and bug reports.

Use the latest URL for demos and review links that should update.

Do not upload secrets, tokens, authorization headers, or private config.

Run --list when project state, hashes, URLs, or expiration dates matter.

Use the CLI when the artifact already exists.

No account flow. No project setup page. No localhost tunnel. Build the static output, deploy it, send the URL that matches the review.

Open docs Read skill