Deploy a static site to IPFS — without touching a CLI

To deploy a static site to IPFS in one step, drag your build folder onto Stasho’s drop zone: your files are hashed into a CID, pinned on Aleph Cloud’s storage network, and served at a live HTTPS URL in under a minute — typically about 10 seconds — no Kubo install, no CAR files, no pinning-service account, no signup. The drop is claimable for 4 hours; claiming is free and keeps the site up.

How it works

Build your site (npm run build, hugo, astro build — anything that outputs a folder of static files).
Drag the output folder onto the drop zone above. The files are hashed into a content identifier (CID) and pinned; you get a live gateway URL.
Claim it (free) to keep it. Claiming turns the drop into a project: custom domains, redeploys, and GitHub-connected deploys on every push.

What the CID gets you

Your deploy isn’t a row in a host’s database — it’s a fingerprint of the files themselves. The same folder always produces the same CID, and any IPFS-compatible host can serve it. That means the deploy is portable by construction: if you ever want to leave, copy the CID and pin the identical site anywhere else (ipfs pin add <cid> on your own node, or any pinning service). No export step, no migration.

The manual way, for comparison

The conventional route to IPFS deployment: install and initialize Kubo, run a local daemon, ipfs add -r ./dist, keep your machine online or open a pinning-service account, wire a CI action for redeploys, and configure DNSLink records for a domain. It works, and it’s the right path if you want to run your own node. If you just want the site up, that entire list is what the drop zone replaces. (Several widely-linked tutorials for the manual route also predate current tooling — check dates before following one.)

Limits, stated plainly

Anonymous drops are claimable for 4 hours and capped per IP (10 per hour, 20 per day; IPv6 counts per /64 prefix, so one network shares the allowance). Claiming is free and removes the window.
Static output only — no server-side rendering at request time.
Framework build steps run for signed-in projects; anonymous drops publish the folder as-is (build locally first).

FAQ

Who pins my site? While your project is active, we pin it on Aleph Cloud’s storage network. The pin is verifiable — the CID either resolves or it doesn’t; there’s no trust-us layer. And because pinning is commodity infrastructure, our pin is replaceable by any other pin of the same CID.

What happens if I stop paying? Your site doesn’t silently vanish. Claimed projects that lapse eventually stop being pinned by us — but the CID stays valid, and anyone (including you) can re-pin the exact same site anywhere else.

Do custom domains work? Add your domain and we give you a short list of DNS records to create. Once they’re in place, your domain serves the site over HTTPS, and every redeploy follows the domain automatically.