flypod [path]

The default command deploys a directory or single file. Logged in, the deploy is owned and permanent. Anonymous, it lives 14 days; running flypod login later automatically claims every anonymous site this CLI remembers, so you don't need to track tokens to make a deploy permanent.

Synopsis

flypod [path]

With no path, flypod auto-detects the first of these directories that contains an index.html:

dist/
build/
out/
.output/public
.vercel/output/static
public/
_site/

The URL prints to stdout. The banner and hints print to stderr. In a non-TTY context, animation is stripped automatically. On success, flypod saves a folder-to-site link so flypod update knows where to ship next.

Flags

Examples

Deploy the auto-detected build directory:

flypod

https://k3p9x2.flypod.dev

Deploy an explicit directory:

flypod ./dist

Machine-readable output:

flypod ./dist --json

{
  "ok": true,
  "url": "https://k3p9x2.flypod.dev",
  "site_id": "k3p9x2",
  "version_id": "v_8f1a",
  "expires_at": null,
  "manage_token": "mt_...",
  "claim_token": null,
  "owner_account_id": "acc_...",
  "source": "dist",
  "files": 12,
  "bytes": 48213,
  "elapsed_ms": 742
}

Notes

• Logged-in deploys have expires_at: null and an owner_account_id. Anonymous deploys carry an expires_at 14 days out and a claim_token.
• Use --quiet in scripts to capture the URL cleanly while keeping the manage_token out of stdout.
• To make an anonymous deploy permanent later, just run flypod login — it auto-claims every anonymous site this CLI remembers.
• See Tokens and ownership for how account sessions, manage_token, and claim_token differ.