Comparison

aft.page vs Cloudflare Drop

Cloudflare Drop is a fast, throwaway static share. aft.page is the publishing and permission layer for small software you actually keep — a durable URL you own, share privately, and update in place.

Cloudflare Drop
aft.page
Best for
Quick static upload → temporary URL
Small software you keep, share & update
Persistence
Temporary by default
Durable URL you claim and keep
Sharing
Public link
Invite by email · private · revoke
Updates
Re-upload as a new drop
Redeploy in place — same URL
Dynamic / secrets
Static files only
Secrets vault + worker / next upstream
Agents
Manual upload
Native MCP: deploy
Custom domain
Not the product
Request access · CNAME to cname.aft.page
Identity
None
Accounts · roles · audit history

When Cloudflare Drop is the right call

  • A one-off static file or folder you just need a link for
  • A throwaway preview you don't plan to keep
  • No need for identity, private sharing, or updates in place

When aft.page is the right call

  • You want the URL to persist and be owned, not expire
  • Share privately with specific people and revoke later
  • Update the page in place at the same URL
  • Hold secrets or add dynamic /api/* endpoints
  • Let your AI agent deploy directly over MCP
  • Attach your own domain after claim

aft.page is built on Cloudflare — it doesn't rebuild those primitives. It adds the small-software lifecycle raw static hosting leaves to you: ownership, private sharing, redeploy, and secrets.

Common questions

How is aft.page different from Cloudflare Drop?

Cloudflare Drop is great for a fast, throwaway static upload to a temporary URL. aft.page adds the lifecycle and permission layer on top: a durable URL you can claim and keep, private sharing by invite, redeploy in place at the same URL, secrets, custom domains, and native agent deploys over MCP.

Does aft.page run on Cloudflare?

Yes. aft.page is built on Cloudflare. It does not replace Cloudflare's primitives — it adds the small-software lifecycle (ownership, sharing, secrets, redeploy) that raw static hosting leaves to you.

Can I keep and update a page instead of it expiring?

Yes. Claim a deploy to keep the URL, then redeploy in place to update it without changing the link, and make it private or invite people when you need to.

Deploy an app Wire up your agent