Hosting
Wisp builds one binary for a server, an image for a container host, plain files for a static host, or WebAssembly for an edge or serverless host. Pick your host below for the build command, the deploy steps, its environment and its limits. The general rules are in Deploying and Edge and serverless targets.
| Host | Build command | Runtime |
|---|---|---|
| VPS | wisp build | native binary |
| Docker | wisp build --docker | container |
| Fly.io | wisp deploy init fly | container |
| Render | wisp deploy init render | container |
| Railway | wisp deploy init railway | container |
| Cloudflare | wisp build --target cloudflare or pages | WebAssembly on Workers or Pages |
| Deno Deploy | wisp build --target deno | WebAssembly on Deno |
| Vercel | wisp build --target vercel | WebAssembly, Node function or Edge |
| Netlify | wisp build --target netlify | WebAssembly, function or edge function |
| AWS Lambda | wisp build --target lambda | static Linux binary |
| Bun | wisp build --target bun | WebAssembly on Bun |
| Node | wisp build --target node | WebAssembly on Node 20+ |
| GitHub Pages | wisp build --static | static files |
| Cloud Run | wisp build --docker | container |
| Azure | wisp build --docker or --target node | container or WebAssembly on Node |
An app that signs cookies needs WISP_SECRET (32 or more random characters) on every host: Environment variables.
Is This Page Useful?