Drop
Point flypod at a folder, a build output, or even a single file. No project setup, no account prompt.
$ npx flypod index.htmlZero auth. Agent-native. Live in seconds.
Your files,
live in seconds.
Run a command, drop a folder, or call from code. No config, no pipeline.
$ npx flypod ./dist HTML or Markdown · no account
How it works
Three steps, all visible in your terminal. No pipeline to configure. Just the path from a folder to a live URL.
Build and ship
flypod packs the directory, stores a version, and prepares the live preview.
-> Uploading 3.2 MB
-> Building
-> DeployingGet a URL
A live URL lands in stdout. Share it, test it, or hand it back to the agent loop.
Live URL: https://a3f1c2d4e5b60789.flypod.pageDeploys that can disappear without drama.
Temporary by default, yours when you want
Anonymous deploys are isolated and expire in 14 days. Perfect for previews, demos, and experiments. Run flypod login whenever you like and every site you deployed on that machine becomes permanently yours.
TTL: 14 days Versioned, one-command rollback
Every deploy is a version. flypod update ships a new one to the same site; flypod rollback brings the last one back. flypod remembers which site a folder maps to, so no flags needed.
flypod rollback Deploy receipt
Every deploy returns what flypod fixed for you and what it could not, each with a fix recipe. Your agent finds out the site is broken before your reviewer does.
"healed": ["spa-fallback"], "warnings": 0 Lives in your agents
One command writes an Agent Skill into .claude/skills and .agents/skills, so Claude Code, Codex, Cursor, Gemini CLI, and Copilot all just know flypod.
flypod install skill Script it. Shell it.
Use the CLI for one-shot deploys, or call the library when your agent already has the files in memory.
CLI
$ npx flypod ./dist
✓ Live https://a3f1c2d4e5b60789.flypod.page
$ flypod update # ship a change → new version
✓ version a1b2c3 is now live
$ flypod rollback # undo it
✓ rolled back to 9f8e7dLibrary
import { deploySite, collectDist } from "flypod";
const files = await collectDist("./dist");
const result = await deploySite({ files });
console.log(result.url);Questions, answered
The eight things people ask before they run the command. Same answers a search or answer engine gets.
What is flypod?
flypod is a zero-auth deploy primitive. You drop a folder of files, or run npx flypod ./dist, and get a live URL back. It also renders markdown into a docs site. No account, no config, no build pipeline.
Do I need an account to deploy with flypod?
No. Deploys are anonymous and require no account or login. Run npx flypod ./dist, or drop a folder on flypod.dev, and you get a live URL instantly. A site deployed this way is temporary and expires in 14 days; run flypod login later and it becomes permanently yours.
What does a flypod URL look like?
https://<site-id>.flypod.page, where the site id is 16 hex characters that flypod picks. There are no custom domains and no chosen names. Every site is served there, claimed or anonymous: claiming a site clears its 14-day expiry, it does not change the address. flypod.dev is this site, the docs, the API and your account pages, and never serves uploaded content — since deploying takes no account, keeping uploads on a separate domain confines reputation damage from a bad upload to a domain the rest of flypod does not depend on.
How much does flypod cost?
flypod is free. Anonymous deploys cost nothing: no account, no card.
How long do flypod deploys last?
Anonymous deploys are temporary: they expire 14 days after they are created, which is ideal for previews, demos, and agent workflows. Deploys made while signed in never expire.
How do I keep a flypod deploy from expiring?
Run flypod login. There are only two states a site can be in, temporary or yours, and flypod login is the one command between them. It claims every anonymous site that machine has deployed, not just the most recent one, so you can deploy first and sign in whenever you decide the site is worth keeping. Sites you own have no expiry and are listed by flypod list. You never have to save or handle a token yourself.
Can I use flypod with my AI coding agent?
Yes. Run npx flypod install skill and flypod writes an Agent Skill into your repo: .claude/skills/flypod for Claude Code, and .agents/skills/flypod for Codex, Cursor, Gemini CLI, and GitHub Copilot. It is a short SKILL.md plus reference docs the agent opens when it needs them. After that your agent knows how to deploy with flypod on its own, with no manual configuration. If you manage skills with the skills CLI instead, npx skills add flypod-dev/flypod-skill installs the same thing.
What kind of sites can flypod deploy?
Static sites. HTML, CSS, JavaScript that runs in the browser, and markdown (which flypod renders into a docs site). flypod does not run server-side code: there are no functions, no databases, no backend. If your site is a folder of files that a browser can render, flypod can deploy it.
How do I publish a new version or roll back with flypod?
Run flypod update to ship changes to the same site as a new version. Plain flypod always creates a brand-new site instead. flypod versions lists every version and flypod rollback makes the previous one live again (or pass a version id). flypod remembers which site a folder maps to, so these need no flags; pass --site <id> to target a site from anywhere.
Your build has somewhere to go now.
No account. No config. Just the deploy loop, moving.
Comments your reviewers can leave inline.
Toggle on per site. Visitors get a pseudonym, highlight any passage on the page, and leave a comment anchored to that exact text. Owners read the thread in context or through the companion JSON feed.
Read the comments docs →