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_SECRETas a project environment variable in Deno Deploy, for an app that signs cookies.- Read other values with
wisp::env("KEY");std::env::varsees nothing and there is no.env. WISP_STORE=deno-kvand the rest: Environment variables.
Limits
- Deno Deploy has no sockets, so it always serves with
Deno.serve. (Locallydeno run -A main.tsreads raw sockets, andWISP_NODE_HTTP=1selectsDeno.serve.) - WebSockets work through
Deno.upgradeWebSocket; a message past the limit closes with 4009, as Deno'sclosetakes no 1009.Response::streamandResponse::eventsare live. - No threads or files: use
wisp::spawnandwisp::sleep. See What works on the edge. wisp::everyis not in the edge build.RateLimitcounts in the memory of each isolate, so each isolate has its own count.wisp::channel: when the app calls Wisp'schannel,main.tsrelays each send to the other isolates and regions through aBroadcastChannelnamedwisp. Deploy has it;deno runneeds--unstable-broadcast-channel(deno run -A --unstable-broadcast-channel main.ts), and without it the channels reach this isolate only (main.tssays so once).- Cron: each
wisp::cronschedule (and one each minute forwisp::work's queues) is aDeno.cronat the top level ofmain.ts, which asks the app for/_wisp/cron/<schedule>withCRON_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-5becomes2,3,4,5,6);*and*/nname the same days either way.L,Wand#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. LocallyDeno.cronneeds--unstable-cron; without it the app says the jobs do not run and serves on. Queued jobs needWISP_STORE=deno-kv.
Files and Data
dist/denohas no separate static folder: the app answers forstatic/itself.Table::savedandRestare per-instance memory unlessWISP_STORE=deno-kv(ordeno-kv:<path>for a file or URL) is set. See Saved tables.wisp::kvandwisp::blobsdefault 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?