Pricing
flypod is free
Last updated: 2026-09-13
Deploying costs nothing. An account costs nothing. There is no card to enter, no trial to start, and no paid tier behind any of it. This page exists because "free" is the kind of claim that deserves the details underneath it.
The whole price list
- Deploy without an account — free. The URL is live in seconds and lasts 14 days.
- Sign in — free. Your deploys stop expiring. That is the entire difference.
- Versions, rollback, Markdown rendering, comments, the API — free. Nothing is held back behind a tier.
There is nothing to enter a card into
flypod never asks for a payment method. Not at signup, not at a usage threshold, not when a site gets traffic. There is no billing page, because there is no billing.
Signing in exists for exactly one reason — to make a site permanent and to list the sites you own. It is not a plan, and nothing else on flypod is gated behind it.
What the catch actually is
The catch is the limits, and they are published. flypod is cheap to run because it does almost nothing: it stores files and serves them. It does not run your code, hold your data, or build your project, so there is no per-user compute to meter.
The two limits that matter most before you start:
- Deploys made without an account expire after 14 days. The files and the site record are deleted; the URL stops working. Sign in, or claim the site, and the expiry is cleared.
- Static files only. No server code, no database, no build step, no custom domains, and every deployed site is public.
The full list, with the reasoning behind each one, is on what flypod can't do. Read that before you read this page again.
No quotas, no seats, no metering
There is no per-account quota. The limits that apply are the same for
everyone, signed in or not: 50 MB per zipped deploy, 100 MB unpacked, 5,000 files per deploy,
10 MB for a deploy made in the browser, and 10 deploys per minute per IP. Over a size limit
the API answers 413; over the rate limit it answers 429.
There are no seats to buy, because there is no team object to put them in. A site belongs to the account that owns it, and a URL is shareable with anyone.
How this is paid for
flypod is a free hobby project run by an individual, as stated in the terms. It is funded out of pocket, and the limits above are sized to keep it that way. The 14-day expiry on anonymous deploys is the single largest reason the bill stays small: storage that cleans itself up does not compound.
That also sets an honest expectation about the service level. There is no uptime guarantee and no support contract. If the thing you are deploying has to stay up, treat flypod as the place you show it, not the place it lives.
Start without deciding anything
Point it at a folder. You can decide whether the site is worth keeping after you have seen the URL.
npx flypod ./dist
To let a coding agent do it on its own, run npx flypod install skill once in the
repo. Full documentation is at docs.flypod.dev.
Related: what flypod can't do, how abuse is handled and reported, terms of service, and privacy.