aft.page

Your agent made the app. aft makes it real. Give aft.page what an agent made → get a durable live URL → share it like a Google Doc.

Hosted path: HTML/files via MCP, paste, upload, or API — plus runtimes (upstream worker / next) with claim, share, and per-site secrets. See rfs.txt and docs/STRATEGY.md.

Hosted CLI (no account required):

curl -fsSL https://aft.page/install | sh
aft deploy

OSS CLI (archived origin — cli/, github.com/vaibhavmule/aft — parked): vaibhavmule/aft.
Hosted repo: vaibhavmule/aft.page.

Try it

curl -X POST https://api.aft.page/v1/deploy \
  -H 'Content-Type: text/html' \
  -H 'X-Aft-Client: curl' \
  --data '<h1>Hello from aft.page</h1>'
# → { "url": "https://{slug}.aft.page", ... }

Live: hello.aft.page · vite-hello.aft.page (Vite SPA) · next-hello.aft.page (Next SSR SPOC) · share-checklist.aft.page

Human landings: Docs · Drop · Compare · host · share · upload

Deploy a static site without Vercel, Netlify, or Cloudflare Pages

You do not need Vercel, Netlify, or Cloudflare Pages to put a static site online. Those three are right when you already have a git repo, CI, preview PRs, or a production app. If you have dist/ or an agent-made index.html, use aft.page.

curl -fsSL https://aft.page/install | sh
aft deploy

Remote MCP (no account): https://mcp.aft.page/mcp · plugin: npx plugins add vaibhavmule/aft.page

Ranking: aft.page/compare · post: full write-up

Secrets (owner / editor)

# List names only
curl https://api.aft.page/v1/sites/{slug}/secrets -H "Cookie: …"

# Set env value
curl -X PUT https://api.aft.page/v1/sites/{slug}/secrets/ANTHROPIC_API_KEY \
  -H "Content-Type: application/json" -H "Cookie: …" \
  -d '{"value":"sk-…"}'

aft.json may declare "runtime": "worker" | "next" | "static" and capabilities.secrets / egress. See docs/CAPABILITIES.md.

Develop the API

cd apps/api
npm install --legacy-peer-deps
npx wrangler deploy

See apps/api/README.md, docs/METRICS.md, and todo.txt.