Deno Deploy Config Builder

Deno Deploy is a globally distributed serverless platform by the Deno company, running JavaScript and TypeScript at the edge using Deno's secure V8-based runtime. Unlike Node.js hosting, Deno Deploy has no build step — you point it at a TypeScript entry file and it deploys within seconds. It supports Deno KV (built-in key-value store), WebSockets, Deno.cron() for scheduled tasks, and static file serving. The free tier includes 100K requests/day and 1GB bandwidth.

Deno uses an explicit permission system — code cannot access the network, filesystem, or environment variables without flags. For Deno Deploy, most permissions are granted automatically. For local dev, use flags: --allow-net (network), --allow-read (file reads), --allow-write (file writes), --allow-env (environment variables), --allow-run (subprocesses). Use --allow-all for development convenience, but restrict permissions in production scripts. Deno Deploy itself grants permissions based on the APIs your code calls.

Deno KV is a built-in key-value database in Deno, backed by FoundationDB on Deno Deploy. Access it with: const kv = await Deno.openKv(). Operations include kv.get(key), kv.set(key, value), kv.delete(key), kv.list({prefix}), and atomic transactions. On Deno Deploy, data is globally replicated. Locally, it uses SQLite. Key paths are arrays: kv.set(['users', userId], userData). It supports strong consistency and ACID transactions via kv.atomic().

An import map lets you alias module specifiers: { "imports": { "hono": "https://deno.land/x/hono@v4/mod.ts" } }. With an import map, your code uses import { Hono } from 'hono' instead of the full URL. This centralizes version management and makes imports cleaner. In deno.json, set importMap: './import_map.json'. For JSR packages (the new Deno registry), use jsr: specifiers: import { Hono } from 'jsr:@hono/hono'. Import maps are the recommended approach over inline URL imports.

Deno.cron() is a native scheduled task API in Deno Deploy. Usage: Deno.cron('task-name', '0 * * * *', async () => { ... }). The name must be unique within a deployment. The schedule uses standard cron syntax. On Deno Deploy, crons run in a dedicated isolate on the schedule — no separate worker or queue needed. Locally, Deno.cron() requires the --unstable-cron flag and runs immediately for testing. Cron tasks have a 5-minute execution limit on Deno Deploy.