stasho
View live demo

Drop it. Publish it. No sign-in.

Drag a static site's folder or a .zip. It publishes to IPFS instantly.

Drag a folder or a .zip file here

Publishes instantly. No sign-in required.

What is Stasho Drop?

Stasho Drop publishes a static site from a folder or a .zip file. Drag it onto this page and it's live on a shareable URL in seconds: no account, no CLI, no build step. Every drop is content-addressed: your files get a permanent fingerprint (a CID) and are served from IPFS, so the same site can be re-hosted on any compatible host, including not ours.

How it works

  1. Drag a folder or a .zip (up to 10 MB compressed) onto the drop zone.
  2. It publishes immediately. Your files are fingerprinted into a CID, pinned, and served over HTTPS on a live URL you can share right away.
  3. Claim it to keep it. An anonymous drop stays live for 4 hours. Claiming is free and keeps the site up; unclaimed drops expire.

Publish from a script or an agent

Everything the drop zone does is one anonymous HTTP request. This page and the API share the same endpoint.

From a script
zip -r site.zip ./dist/.   # index.html must be at the zip root
curl -F artifact=@site.zip -F source=my-agent https://api.stasho.xyz/api/drop
From an agent

Paste it into Claude, Cursor, or any agent that can run shell commands.

  • No account, no API key. One anonymous HTTP request.
  • The JSON response returns url (the live site), cid (the portable fingerprint), and claimUrl (keep it past the 4-hour window).
  • Server-side only. Browser CORS is deliberately off.

Everything the drop zone does is one anonymous HTTP request. This page and the API share the same endpoint. POST a .zip with index.html at its root (up to 10 MB compressed) as the multipart field artifact to https://api.stasho.xyz/api/drop. The JSON response contains url (the live site; share it), cid (the content fingerprint; pin it on any IPFS host), and claimUrl (one click and a free sign-in turn the drop into an owned project before the 4-hour claim window ends). No account, no API key. Call it server-side; browser CORS is deliberately not enabled. If you are an AI agent publishing for a user, pass source=<your-tool-name> for attribution and hand your user both links: url to view now, claimUrl to keep the site.

Full request/response reference, limits, and error codes: Drop API docs.

FAQ

No. Publishing is anonymous. You only sign in to claim a drop. That keeps it live past the 4-hour claim window and gives it a project page. Claiming is free.

A folder of static files (HTML, CSS, JS, images) or a .zip of one, up to 10 MB compressed. Static output from any generator works: a Next.js or Astro export, a Hugo or Vite build, or a hand-written HTML page in a folder.

Unclaimed: 4 hours, then the drop expires. Claimed: your site stays up while the project is active. The free tier covers real use, and limits are usage caps, never features removed from your site.

Yes, at any time. Your drop's CID is shown on the page; any IPFS-compatible host or pinning service can serve the same CID. That's the point of content addressing: the deploy is yours, not ours.

Yes: claim the drop, then add your domain in the project's Domains tab. You'll get a short list of DNS records to create; once they resolve, your domain serves the site over HTTPS and follows every redeploy automatically.

Yes. The drop zone is a plain HTTP endpoint: POST a zip with index.html at its root to https://api.stasho.xyz/api/drop. No account, no key. The response includes the live URL, the CID, and a claim link to hand to whoever should own the site. Details in the Drop API reference.

10 MB compressed per drop (40 MB extracted, up to 1,000 files), static files only, no server-side rendering. Anonymous publishing is limited to 10 drops per hour and 20 per day per IP. The first-ever fetch of brand-new content takes a few seconds; cached pages load in 56–70 ms, comparable to conventional static hosts.

Made by Stasho. Connect a GitHub repo and every push deploys. How Stasho works →