Wisp.place Documentation
Decentralized static site hosting on the AT Protocol.
Wisp.place enables you to host static websites directly in your AT Protocol repository. Your Personal Data Server (PDS) holds the cryptographically signed manifest and files as the authoritative source of truth, while hosting services index and serve them with CDN-like performance.
Quick Start
Section titled “Quick Start”Using the Web Interface
Section titled “Using the Web Interface”Visit https://wisp.place and sign in with your AT Protocol account to deploy sites through the browser.
Using the CLI
Section titled “Using the CLI”# Download the CLI binary for your platformcurl -L https://sites.wisp.place/nekomimi.pet/wisp-cli-binaries/wisp-cli-x86_64-linux -o wisp-clichmod +x wisp-cli
# Deploy your site./wisp-cli your-handle.bsky.social --path ./my-site --site my-siteYour site will be available at:
https://sites.wisp.place/{your-handle}/{site-name}Or map it to your own domain with a DNS TXT record.
How it works
Section titled “How it works”- You upload static files (HTML, CSS, JS, images — anything a browser can serve)
- Files are compressed and stored as blobs in your AT Protocol repo as a
place.wisp.fsrecord - Hosting services watch the AT Protocol firehose and cache your site
- Visitors get your site served fast from cache, with automatic invalidation on updates
Your PDS is the source of truth. Hosting services are read-only caches — they can always reconstruct your site from your repo.
Next steps
Section titled “Next steps”- CLI reference — deploy, pull, and serve sites from the command line
- Architecture — how the firehose, hosting, and storage tiers fit together
- Self-hosting — run your own Wisp instance
- Redirects & rewrites — Netlify-style URL rules
- Lexicons — the AT Protocol record types that power it all