Wisp is in pre-release, self-hosted since GitHub suspended us. Install it, or see the changelog.

Wisp

Host on Deno Deploy

Deno Deploy runs the app as WebAssembly on Deno's edge.

Two shutdowns: Deno Deploy Classic (dash.deno.com, the platform deployctl deploys to) shut down on 20 July 2026 (Deno Deploy Classic). The new Deno Deploy (console.deno.com, deno deploy) is closing too: Deno's announcement of 9 October 2026 says it "will continue operating for six months before shutting down", with no exact date, and migration help to Cloudflare Workers for paying customers. A new app is better on Cloudflare; the deno target still runs anywhere Deno does (deno run -A main.ts).

Build

rustup target add wasm32-unknown-unknown     # once
wisp build --target deno                     # dist/deno (--out <folder>)

In Deno Deploy's CI a plain wisp build picks the target from DENO_DEPLOYMENT_ID.

Deploy

From dist/deno:

deno deploy create --app my-app --source local --runtime-mode dynamic --entrypoint main.ts   # once
deno deploy --app my-app --prod
deno run -A main.ts          # try it locally (add --unstable-broadcast-channel for wisp::channel)

deployctl is for Deploy Classic only; the new Deno Deploy takes deno deploy. wisp deploy init deno writes a GitHub Actions workflow that builds and runs deno deploy --prod from dist/deno on push to main. It reads the secret DENO_DEPLOY_TOKEN (an organization token) and the variable DENO_DEPLOY_ORG. The command sets --app to the package name of your app.

Environment

  • WISP_SECRET as a project environment variable in Deno Deploy, for an app that signs cookies.
  • Read other values with wisp::env("KEY"); std::env::var sees nothing and there is no .env.
  • WISP_STORE=deno-kv and the rest: Environment variables.

Limits

  • Deno Deploy has no sockets, so it always serves with Deno.serve. (Locally deno run -A main.ts reads raw sockets, and WISP_NODE_HTTP=1 selects Deno.serve.)
  • WebSockets work through Deno.upgradeWebSocket; a message past the limit closes with 4009, as Deno's close takes no 1009. Response::stream and Response::events are live.
  • No threads or files: use wisp::spawn and wisp::sleep. See What works on the edge.
  • wisp::every is not in the edge build. RateLimit counts in the memory of each isolate, so each isolate has its own count.
  • wisp::channel: when the app calls Wisp's channel, main.ts relays each send to the other isolates and regions through a BroadcastChannel named wisp. Deploy has it; deno run needs --unstable-broadcast-channel (deno run -A --unstable-broadcast-channel main.ts), and without it the channels reach this isolate only (main.ts says so once).
  • Cron: each wisp::cron schedule (and one each minute for wisp::work's queues) is a Deno.cron at the top level of main.ts, which asks the app for /_wisp/cron/<schedule> with CRON_SECRET: set it as a project variable. Deno counts the weekday 1 to 7 from Sunday, where cron counts 0 to 6, so the build writes a weekday field that names days as Deno's list (1-5 becomes 2,3,4,5,6); * and */n name the same days either way. L, W and # stop the build: Deno has none. Deno runs crons in production deploys only, in UTC, up to a minute late, and skips a run while the last is still going. Locally Deno.cron needs --unstable-cron; without it the app says the jobs do not run and serves on. Queued jobs need WISP_STORE=deno-kv.

Files and Data

  • dist/deno has no separate static folder: the app answers for static/ itself.
  • Table::saved and Rest are per-instance memory unless WISP_STORE=deno-kv (or deno-kv:<path> for a file or URL) is set. See Saved tables.
  • wisp::kv and wisp::blobs default to Deno KV (WISP_KV_<NAME>=deno-kv); a blob is at most 64 KiB there. See Storage.

More

Edge and serverless targets, Deploying.

Is This Page Useful?

View This Page's Source

Type to search every docs page and heading.