Docs›Production deployment

Deployment decisions

Choose among Deno Deploy, containers, and general cloud platforms by runtime boundary

View Markdown Upstream source

Choose the runtime model first

Goal	Consider first	Verify
Git-driven multi-region (US/EU) runtime and managed data	Deno Deploy	current regions, quotas, build and runtime APIs
System packages, Kubernetes, portable image	Docker	image variant, signals, filesystem user, health checks
Existing VM or PaaS	native Deno or container	installed version, persistent volumes, network policy
Single-file CLI	`deno compile`	target architecture, dynamic assets, permissions, native code

Platform-independent contract

Document at least:

entry point and start command;
bind address and PORT behavior;
required Deno permissions;
environment variable names, with no secrets in images or logs;
/health or an equivalent platform signal;
SIGTERM, timeout, retry, and idempotency boundaries;
lockfile, Deno version, and rollback artifact.

Continue with Deno Deploy, Data and cron, Classic migration, Docker, or the production baseline.