Wisp.place is a decentralized static site hosting platform built on the AT Protocol, designed to empower users to host websites directly within their own personal data repositories. By leveraging the cryptographic integrity of the AT Protocol, Wisp.place ensures that a user's Personal Data Server (PDS) acts as the authoritative source of truth for their site's content. Hosting services observe the AT Protocol firehose to cache and serve these sites, providing CDN-like performance while maintaining decentralized control. The platform was created by @nekomimi.pet.

Functionality centers on transforming a folder of static files into a live, accessible website. Users can deploy content through a web-based dashboard or a dedicated command-line interface. The process involves compressing files, storing them as blobs within an AT Protocol repository, and notifying hosting services to cache the update, allowing visitors to access the site with high speed and automatic invalidation upon changes.

Some of the key features are:

• Decentralized Storage: Files are stored directly in your AT Protocol repository, ensuring you retain full ownership and control.
• Command Line Control: The wispctl CLI provides full deployment, management, and local testing capabilities for advanced users.
• Incremental Updates: Uses content-addressed CIDs to track changes and only upload modified files, enabling rapid deployment cycles.
• Custom Domains: Support for mapping custom domains or subdomains to hosted sites via DNS TXT records.
• Local Preview: Ability to serve site files locally with real-time updates monitored via the AT Protocol firehose.
• Self-Hosting Options: Users have the flexibility to run their own infrastructure to monitor the firehose and host sites independently.
• Zero-Configuration: Designed to work with sensible defaults, eliminating the need for complex YAML or JSON configuration files.
• Security and Performance: Automatic file compression and metadata management ensure efficient delivery while bypassing common content sniffing restrictions.

Users operate the platform primarily through the wispctl CLI or web dashboard. The CLI handles the authentication, file filtering (via .wispignore), compression, and upload processes. Once deployed, the site becomes accessible via a global URL provided by the service, or through custom domain configuration. The architecture ensures that even if a specific hosting provider goes offline, the site data remains safely stored in the user's PDS, allowing for recovery or migration to other providers.

Some common use cases include:

• Personal Portfolios: Hosting personal landing pages or creative portfolios with full control over the underlying data.
• Documentation Sites: Deploying static documentation generated by tools like static site generators directly to a decentralized environment.
• Blog Hosting: Publishing static blogs or text-based sites that benefit from the speed of CDN-like caching and the immutability of the AT Protocol.
• CI/CD Pipelines: Integrating automated site deployments into existing development workflows using tools like Tangled Spindle or other CI/CD environments.