Deno Deploy Pricing

Pricing shown covers Deno Deploy and Deno Subhosting usage.
Allowed inbound HTTP requests to your deployments per month
Monthly limit on data egress across all your deployments. Inbound request data does not count against this number.
Total number of domains that can be assigned to active deployments
Assign all requests to subdomains to a particular deployment
You're only billed for CPU while your app is actively running code. CPU isn't consumed while your app is waiting for incoming requests or blocked on network I/O.
You're billed for 768 MB of memory for each second your app is loaded in memory - the default allocation. Pro and Builder can configure a higher app/build memory limit, billed at that higher amount. Idle apps automatically shut down after ~20-30 seconds, so you're not billed for memory while scaled to zero.
Storage used by your app's deployment revisions - each revision's built image and its assets. Older revisions are automatically removed according to your retention settings.
Total number of deployments that can be active at any given time in your organization
Number of builds that can run at the same time within your organization
A "read unit" is an invocation of a Deno KV command which fetches data, like "get"
A "write unit" is an invocation of a Deno KV command which updates data, like "set"
Get real-time logs from your deployments
How far back you can query your apps' runtime logs and traces.
Requests, CPU, memory, network and KV usage per app, with this much history in the dashboard and the API.
Number of authenticated Deno Deploy users who can manage resources within an organization
Get support from the Deno community via Discord
Receive hands-on expert guidance from our engineers as you onboard to Deno Deploy
Allowed inbound HTTP requests to your deployments per month
Monthly limit on data egress across all your deployments. Inbound request data does not count against this number.
Total number of domains that can be assigned to active deployments
Assign all requests to subdomains to a particular deployment
You're only billed for CPU while your app is actively running code. CPU isn't consumed while your app is waiting for incoming requests or blocked on network I/O.
You're billed for 768 MB of memory for each second your app is loaded in memory - the default allocation. Pro and Builder can configure a higher app/build memory limit, billed at that higher amount. Idle apps automatically shut down after ~20-30 seconds, so you're not billed for memory while scaled to zero.
Storage used by your app's deployment revisions - each revision's built image and its assets. Older revisions are automatically removed according to your retention settings.
Total number of deployments that can be active at any given time in your organization
Number of builds that can run at the same time within your organization
A "read unit" is an invocation of a Deno KV command which fetches data, like "get"
A "write unit" is an invocation of a Deno KV command which updates data, like "set"
Get real-time logs from your deployments
How far back you can query your apps' runtime logs and traces.
Requests, CPU, memory, network and KV usage per app, with this much history in the dashboard and the API.
Number of authenticated Deno Deploy users who can manage resources within an organization
Get support from the Deno community via Discord
Receive hands-on expert guidance from our engineers as you onboard to Deno Deploy
Allowed inbound HTTP requests to your deployments per month
Monthly limit on data egress across all your deployments. Inbound request data does not count against this number.
Total number of domains that can be assigned to active deployments
Assign all requests to subdomains to a particular deployment
You're only billed for CPU while your app is actively running code. CPU isn't consumed while your app is waiting for incoming requests or blocked on network I/O.