Docs / Claim & share

Claim & share

Keep an anonymous deploy forever, change its URL, make it private, invite people, roll back, or destroy — same *.aft.page slug.

Why claim

Anonymous deploy is live immediately. Unclaimed sites stay up but are permanently deleted after 30 days without a visit or update. Claim to keep the URL forever and unlock the project dashboard: private access, invites, secrets, domains, rollback, destroy.

How to claim

  1. After deploy, open the claimUrl printed by the CLI / MCP / Drop result (https://aft.page/claim?slug=…&token=…), or use Claim on the live preview bar when you have the edit token.
  2. Sign in with Google or a magic link.
  3. The site appears under Projects. Same https://{slug}.aft.page URL.

The edit token is sensitive — treat it like a password until you claim. After claim, ownership is your account; edit token alone cannot manage the site.

Change URL

Random or long-title slugs happen. You can rename:

  • Before claim: Preview → Change URL (needs deploy ?token=).
  • After claim: Project → Overview / Danger → Change URL, or aft login && aft rename new-slug.

The old *.aft.page hostname stops working immediately. Custom domains stay attached to the site. API: POST /v1/sites/{slug}/rename with { "slug": "new-name" }.

Private & invites

Owner: project Access (or preview Access) → Public / Private. Private sites require invite-by-email (view or edit). Edit can redeploy / rollback; view can open the live site only.

aft visibility private
aft visibility public

Redeploy & rollback

Redeploy in place keeps the same slug. History is on the project Deploys tab. CLI (after login):

aft rollback              # list
aft rollback dep_…       # restore prior deploy

Agents can use MCP aft_deploys / aft_rollback with the edit token before claim — mcp.md.