Deno Deploy
Deno Land Inc. · ⚡ Serverless / FaaS
Deno Deploy is a serverless platform for JavaScript, TypeScript and WebAssembly apps with a free plan, Deno KV, GitHub deploys and edge caching.
Free-tier constraints
- Offer type
- Perpetual
- When idle
- Stays active
- Credit card
- Required
- Commercial use
- Allowed
- At the limit
- Service suspends
- Data expiry
- Not published
Free-tier compatibility
- ✓Static hosting
- ✓Serverless
- —Long-running processes
- —Docker
- ✓WebSockets
- ✓Cron
- —Background workers
- ✓Persistent disk
- ✓Custom domains
Overview
Deno Deploy is the managed serverless platform from the Deno team. It is designed for JavaScript, TypeScript and WebAssembly applications that benefit from a Deno-native runtime, GitHub deployments, built-in observability and edge caching. For Fresh and Hono projects, it is often the most direct production target.
The current free plan is usage-based rather than a single tiny VM. It includes monthly requests, egress bandwidth, CPU time, memory time, active apps, custom domains and KV storage. That makes it attractive for prototypes, personal apps and low-traffic production services, but you still need to watch quotas because free organizations can be paused when they exceed limits.
The main caveat is platform transition. Deno Deploy Classic and the newer Deno Deploy are not identical, and the docs note a Classic shutdown date. New projects should start from the current console and documentation instead of relying on old Deploy Classic guides.
Sources and verification
Checked 2026-08-18Pros
- ✓First-party Deno runtime with TypeScript support and Node/npm compatibility
- ✓Free plan includes requests, bandwidth, CPU time, memory time, apps and KV storage
- ✓GitHub and CLI deployment paths
- ✓Works especially well with Fresh, Hono and other edge-friendly JavaScript apps
Cons
- ✕Free organizations can hit monthly usage pauses when limits are exceeded
- ✕Full free-plan usage may require credit-card verification
- ✕New Deno Deploy differs from Deploy Classic, which has its own migration path
Best for
- →Deno, Fresh and Hono apps that should run close to users
- →TypeScript APIs and small full-stack apps with Deno KV
- →Teams that want a Deno-native serverless platform instead of a Node server
Getting started
- 1 Create a Deno Deploy organization in the console
- 2 Connect a GitHub repository or deploy from the CLI
- 3 Configure build, install and runtime settings in the dashboard or deno.json
- 4 Add environment variables, KV or custom domains as needed
- 5 Watch requests, CPU time, memory time and bandwidth usage in the console
Features
- ✓JavaScript, TypeScript and WebAssembly runtime
- ✓GitHub and CLI deployments
- ✓Deno KV storage
- ✓Web Cache API and HTTP edge cache
- ✓Logs, analytics and OpenTelemetry-friendly runtime
Frameworks
Languages
FAQ
The official pricing page lists 1M requests per month, 20 GB egress, 15 CPU hours, 350 GB-h memory time, 20 active apps, 50 custom domains and 1 GiB each of volume and KV storage.
No. It is Deno-native, but Deno's current platform also supports Node and npm-compatible JavaScript frameworks such as Hono, Fresh, Astro, SvelteKit and Express-style apps.
Review the current Deno Deploy docs because Deploy Classic has a separate runtime model and is scheduled to shut down on July 20, 2026.
Deploy these projects to Deno Deploy
Open-source projects and templates that run on Deno Deploy's free tier.