No account to start

Turn your agent-built app into a shareable URL in seconds.

Drop your files or deploy from your agent. No repository, cloud setup, or account required.

Your URL stays the same when you update—and you can roll back or remove it anytime.

% # Add to your agent
% https://mcp.aft.page/mcp

deploy({
  html: "<!DOCTYPE html><title>Hello</title><h1>Live from MCP</h1>",
  preferred_slug: "hello"
})
# → hello.aft.page

What you can ship

Agent output becomes a live app you can open, share, and keep — without a cloud account.

  1. Deploy

    ships today

    Drop a folder or let your agent call MCP. Live *.aft.page URL in seconds. No account.

  2. Share

    after claim

    Public when you want. Private when it’s internal. Invite by email; revoke without redeploying.

  3. Keep

    same URL

    Same URL when you update. Roll back or remove anytime. Claim to own it.

Static HTML, CSS, and JS today. 200 files · 10 MB each · 50 MB total. Claim to keep ownership.

Four ways in.

Same live URL whether an agent or a human ships it.

  1. 001

    MCP

    Point your agent at mcp.aft.page.

  2. 002

    Drop

    Folder or zip in the browser. No account to start.

  3. 003

    cURL

    POST HTML to the deploy API. Get a URL back.

  4. 004

    Claim

    Own the slug. Update, invite, or take it private.

Share like a Doc

Invite by email. Revoke when done.

Public when you want. Private when it’s internal. Add a teammate by email; remove access without redeploying. Company SSO is on the roadmap.

View a live example

Same URL while it matters

Update, roll back, or stop.

Your URL stays the same when you update the app—and you can roll back or remove it anytime. No permanent infrastructure work for software that might only matter for a week.

Deploy an app

Why agent users pick aft

A URL and a share — without the rest of the ceremony.

Traditional cloud
aft
Time to URL
Repo · build · account · wait
Seconds from agent output
Sharing
Public site or DIY auth
Invite by email · revoke anytime
Ownership
Scattered across tools
Claim · update · same URL
Custom domain
Platform DNS ceremony
Request access · CNAME to cname.aft.page
Lifecycle
Always-on by default
Ship · use · stop when done
Built for
Big Software teams
Small software · agent users

Longer write-ups: typical app host · file drop · static hosting

Free to make it live.

Pay when you keep more apps running, need private sharing, or connect live internal data. Nothing is billed during beta.

Free

Now

Ship a public URL. No account required.

$0 during
beta
Deploy an app

Free includes

  • Public *.aft.page URL
  • MCP, Drop, and API deploy
  • Claim + basic share
  • 200 files · 10 MB each · 50 MB total

Team

After beta

Private apps and a durable project. Same features work today after you claim.

$99 per
month
Join waitlist

Everything in Free, plus

  • Private apps + invite by email
  • Owner, versions, rollback
  • Stateful runtime as it ships
  • Founder email support

Enterprise

Company SSO and bring-your-own cloud when Team is not enough.

Custom
Contact

Everything in Team, plus

  • Company SSO
  • BYOC when you need it
  • Custom limits
  • Design-partner path for live data

Questions, answered

What aft.page is, who it's for, and how it works — in plain language.

What is aft.page?

aft.page turns software your AI agent builds into a live, shareable HTTPS URL in seconds — no repository, cloud account, or build setup. Deploy by dropping files, pasting HTML, or letting your agent call the MCP.

Do I need an account to deploy?

No. Anonymous deploy gives you a live *.aft.page URL immediately. You only sign in when you want to claim a page, update it, make it private, or invite people.

Is aft.page free?

Yes — free during beta, including private invite after you claim. Team is $99/month when billing starts. Waitlist members hear before anything is charged.

How is aft.page different from a typical cloud host?

Those are built for Big Software: repositories, builds, and cloud accounts. aft is the publishing and permission layer for small software that one person or a small team uses — an instant URL, invite-by-email sharing, clear ownership, and secrets, without the ceremony.

How do AI agents deploy to aft.page?

Any agent that speaks MCP can use the remote server at https://mcp.aft.page/mcp with the deploy, aft_deploys, aft_rollback, and aft_health tools, or call the API directly.

Can I make a page private or invite people?

Yes. Claim a deploy, then keep it public, make it private, or invite specific people by email — and revoke access anytime.

Can I use my own domain?

Yes after you claim. Project → Domains, request access, then CNAME to cname.aft.page. HTTPS issues from there. The *.aft.page URL stays.

What can I deploy, and what are the limits?

Single HTML documents or multi-file static sites and SPAs (include index.html). Limits: 200 files, 10 MB per file, and 50 MB total.

Ready to ship a live URL?

Drop files or deploy from your agent. No repository, cloud setup, or account required.

BETA · FREE FOR NOW

Free during beta.

Paid plans will be announced before billing begins. Join the waitlist for pricing and product updates—including company SSO.

Pricing & product updates only. No spam. Unsubscribe anytime. Privacy details.