blazz.ing
Vol. 01 — the ephemeral issue anonymous static hosting
blazz.ing turns any folder of static files into a live site on its own private subdomain. No account, no config, no dashboard — and in 30 days it's gone. That's the feature.
ship something ↓no signup unguessable subdomains 6 MB max compressed static anything burns in 30 days
three ways, zero accounts
tar czf - -C ./dist . | curl -sS --data-binary @- \
-H 'Content-Type: application/gzip' https://blazz.ing/api/sitesUp to 6 MB compressed. The JSON response is your live site — and the only time you'll see its update token.
curl -fsSL https://blazz.ing/install | bash
blazz ./distOne script, then one word. Point it at any folder; junk like .git stays home.
FEED THE FIRE — drop a folder, get a URL
or click to chooseDrops here really publish — straight to a live URL on its own subdomain.
now live
your-site.blazz.ingburns — push again to reset the clock
This token is the only credential that can update or delete this site. It will never be shown again, and we can't recover it.
six facts, no fine print
No build queue, no cold start, no deploy spinner. The API response already contains your live URL — the site is serving before your command returns.
Every site lives on an unguessable subdomain. No index, no listing, no search. The only people who find it are the people you hand the link to.
Every site burns off 30 days after its last push. Push again and the clock resets. Nothing you forget about lingers on the internet forever.
No signup, no email, no API key. Publishing is anonymous; your update token is the only credential, and only you have it.
HTML, CSS, JS, images, fonts, WASM — if a browser can load it, we'll serve it. Up to 6 MB compressed per push.
A one-page API with JSON everywhere and an /llms.txt your coding agent already understands. Robots ship here without supervision.
days — then gone
Thirty days after its last push, a site self-destructs — files, subdomain, everything. Pushing an update resets the clock. Demos, prototypes, and handoffs get exactly the lifespan they deserve: long enough to matter, never long enough to haunt you.
for the robots
blazz.ing is small enough to fit in a context window. One page covers publish, update, delete, limits, and every response shape — point your coding agent at it and walk away.
curl -s https://blazz.ing/llms.txt