From folder to HTTPS in one command.

A Small Deployment Plane for Static Sites

Yeeet takes an already-built file or folder and publishes it as an atomic HTTPS release. It combines direct-to-bucket uploads, immutable versions, a movable live alias, SPA refresh support, private review links, custom domains, and edge-aware caching behind one browser workflow and one CLI.

It is intentionally focused: Yeeet serves static output and never executes an untrusted build. Run your framework's build locally or in CI, then hand Yeeet the resulting dist, build, out, or public directory.

Deploy Your First Site

Bring Node.js 20.19+ or 22.12+, a Yeeet account, and a folder containing static files. The CLI handles the manifest, parallel uploads, atomic activation, and URL.

1. Install the CLI

   Install the public package once so yeeet is available from any project.

   npm install --global @yeeet.dev/cli

   Copy

2. Log In from Your Terminal

   A one-time device flow opens in your browser. Your terminal never asks for or stores your password.

   yeeet login

   Copy

3. Point at the Output Folder

   Yeeet creates a readable random subdomain when you do not specify a name.

   yeeet deploy ./dist

   Copy

Random When Quick. Named When Stable.

Skip a name for an instant throwaway URL, or choose a name when the URL should remain stable across releases. Either way, the upload becomes visible only after every file is ready.

Save Project Defaults

Run yeeet init comet to create .yeeet.json. From then on, the project name and routing mode travel with the project.

yeeet init comet
yeeet deploy ./dist

Every Launch Is Recoverable

A named site is a movable pointer to an immutable release. List history, preview any version, or atomically make an older version live again.

yeeet versions comet
yeeet rollback comet 52eabb5f

# Or roll back to the previous ready release
yeeet rollback comet

Version commands accept a full deployment ID or an unambiguous prefix of at least 8 characters. Live aliases revalidate at the edge in about 10 seconds; immutable preview URLs never change.

Remove What You No Longer Need

yeeet version remove comet 52eabb5f --yes
yeeet remove comet --yes

Protect It. Share It in One Click.

Password protect a launch, then send a signed share URL. Reviewers need no Yeeet account and do not have to type the password.

export YEEET_DEPLOY_PASSWORD="a long private password"
yeeet deploy ./dist --name review
yeeet share review

Change access without re-uploading files. Rotating the link revokes both the previous URL and existing viewer cookies.

yeeet access protect review <version> --password "a new password"
yeeet access rotate-link review <version>
yeeet access public review <version>

Bring a Custom Hostname

Attach a hostname from the CLI. Yeeet returns the routing and ownership-verification records; Railway provisions and renews TLS once DNS verifies.

yeeet domain add comet www.example.com --json

# After adding every returned DNS record
yeeet domain refresh comet www.example.com --json
yeeet domain list comet --json

Add every returned DNS record exactly as shown. Propagation time depends on your DNS provider. Use domain list to inspect routing, verification, and certificate status.

Predictable for Agents & CI

Create an API key in the dashboard, provide it through the environment, and request JSON. The same CLI works interactively, in CI, or as an agent tool.

export YEEET_TOKEN="yeeet_…"
yeeet whoami --json
yeeet deploy ./dist --json

curl -fsSL https://docs.yeeet.dev/llms.txt

• Exit 0: deployment succeeded and stdout contains the final JSON object.
• Exit 2: authentication is required; provide YEEET_TOKEN.
• Exit 1: validation, upload, or network failure; stderr explains the next action.

Command Map

Use yeeet --help or yeeet <command> --help for every option.

Quick Fixes