Deno Deploy

deno.com · 5 records in Compute, Egress and tunnels, Storage · JSON

Records 5

caveatDeno Deploy (Compute)
Computefree tieridentity emailno cardlimit retention-clampedevidence documentedstale on 2026-12-05
caveatDeno Sandbox
Computefree tieridentity email?card?limit request-rateevidence documentedstale on 2026-12-05
fails: egressDeno Deploy (Egress and tunnels)
Egress and tunnelsfree tieridentity emailno cardlimit volume-quotaevidence documentedstale on 2026-11-23
fails: quotaDeno Deploy (managed Deno KV)
Storagefree tieridentity email?card?evidence reportedstale on 2026-11-05
fails: quotadeno deploy deployment assets (static file store)
Storageidentity email?card?evidence reportedstale on 2026-11-05

Deno Deploy (Compute)

Compute

deno.com/deploy/pricingCloud VMcompute/deno-deployJSON compare report an error

Free allowance: Free at USD 0: 1 million requests a month, 20 GiB of egress, 10 hours of active CPU, 150 GiB-hours of memory time, 10 apps, 10 GiB of revision storage and 1 GiB of KV.
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: emailno card, no phone
Binding limit: retention-clampedidle apps shut down after about 20 to 30 seconds
Evidence: documented12 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05

Free tier	Free at USD 0: 1 million requests a month, 20 GiB of egress, 10 hours of active CPU, 150 GiB-hours of memory time, 10 apps, 10 GiB of revision storage and 1 GiB of KV. unit mixed; metered on request-count
Price	none stated
Limits	retention-clamped (binding) idle apps shut down after about 20 to 30 seconds source volume-quota 10 hours of active CPU and 150 GiB-hours of memory a month source request-rate 1 million requests a month source 10 hours of active CPU a month is the wall: an always-resident process cannot exist because idle apps are shut down after 20 to 30 seconds, so the 10 hr is spent by request handling and cron-triggered work, not by uptime.
Binding	retention-clamped the 20 to 30 second idle shutdown means there is no resident process to bill, so the CPU grant is spent by requests rather than by uptime.
Identity	email a Deno Deploy account; no card on the Free plan
Egress	20 GiB a month included on Free, a monthly limit; inbound request data does not count; the Free column lists no overage price (the paid Pro and Builder columns list '(then $0.20/GiB)') free allowance: 20 GiB
Per-object cap	a 768 MB default memory allocation per app; 10 apps
Retention	revision storage is 10 GiB with automatic removal of older revisions per the retention setting
Interface	cli The deno deploy command-line interface (a subcommand of the deno CLI) for creating and deploying apps, and the console.deno.com web dashboard
Tooling	the deno CLI, subcommand deno deploy (create, deploy and manage apps)
Composes with	A perpetual 1M-request front that can hold secrets, run cron and talk to an IPv6-only VPS behind it; it is the IPv4 face for a Hax box, and it costs nothing at that request rate.
Reliability	a cold start follows every idle period; CPU is not consumed while the app waits on I/O, so the meter is friendlier than the wall clock suggests
Notes	The 150 GiB-hours matches.
Evidence note	documented the Free plan table and the idle-shutdown sentence were read on the pricing page
Parsed numbers	price USD 0 10 hours a day / month price USD 0 / month has-free-tier 1 volume-quota 10 hours

Evidence 12

date	source	what it proved
2026-10-22	deno.com/deploy/pricing	free plan row gives 1M requests, 20 GiB egress, 10 hr active CPU, 150 GiB-hr memory, 10 apps, 5 custom domains, quoted
2026-10-22	docs.deno.com/deploy/pricing_and_limits/	applications have a maximum memory allocation of 512 MB and no upload request limit within the provider
2026-10-22	docs.deno.com/deploy/classic/	Deploy Classic shut down on 20 July 2026 and no new users were onboarded to it, quoted
2026-10-24	deno.com/deploy/pricing	quoted: 'Idle apps automatically shut down after ~20-30 seconds, so you're not billed for memory while scaled to zero.'
2026-10-24	deno.com/deploy/pricing	quoted: 'Requests/month: 1M', 'Egress Bandwidth: 20GiB', 'Active CPU: 10 hr', 'Memory time: 150 GiB-hr', 'Apps: 10', 'KV storage: 1 GiB'
2026-10-24	deno.com/deploy/pricing	quoted: '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.'
2026-11-03	deno.com/deploy/pricing	egress is a monthly limit, 20GiB in the Free column, inbound request data not counted
2026-11-03	deno.com/deploy/pricing	the paid column prices egress beyond its allowance at $0.20/GiB; the Free column has no such line
2026-11-03	docs.deno.com/deploy/	Deno Deploy can be deployed from a CLI, besides the web dashboard
2026-11-04	docs.deno.com/runtime/reference/cli/deploy/	the CLI reference documents the deno deploy command
2026-11-04	docs.deno.com/runtime/reference/cli/deploy/	the reference names deno deploy create
2026-11-04	deno.com/deploy/pricing	the Pro column (200GiB) and the Builder column (2,000GiB) each list egress beyond the allowance at $0.20/GiB; the Free column (20GiB) lists none

More fields 10

facets	`{"class": "perpetual-allowance","free_tier_kind": "perpetual-allowance","shape": {"vcpu": null,"ram_gib": 0.75,"gpu_class": null,"gpu_count": null}}`
shape	`{"vcpu": null,"ram_gib": 0.75,"disk_gib": null,"gpu_class": null,"gpu_count": null}`
billing model	free
term	none
m10h usd	0.0
m24h usd	0.0
price arithmetic	no charge inside the free allowances
free tier kind	free-allowance
network out	`{"allow_outbound": true,"allow_inbound_listen": false,"ports": "HTTP through the platform edge; no listening TCP socket","static_ip": false,"ipv6": false,"per_session_bytes": null}`
session cap	`{"wall_clock_min": null,"idle_reap_s": 30,"restart_required": false,"note": "idle apps shut down after about 20-30 seconds"}`

Deno Sandbox

Compute

deno.com/deploy/pricingContainer and VM sandboxcompute/deno-sandboxJSON compare report an error

Free allowance: A free plan with a monthly request allowance, an egress allowance and a per-plan sandbox concurrency; sandbox compute bills through the same CPU, memory and egress meters as deployments
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: email?placeholder, not evidence; card unknown, phone unknown
Binding limit: request-rateinbound HTTP requests a month on the free plan; the page lists the row but the extracted text does not carry its number
Evidence: documented4 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05

Free tier	a free plan with a monthly request allowance, an egress allowance and a per-plan sandbox concurrency; sandbox compute bills through the same CPU, memory and egress meters as deployments unit requests; metered on request-count
Price	none stated
Limits	request-rate (binding) inbound HTTP requests a month on the free plan; the page lists the row but the extracted text does not carry its number source per-ip-shaping egress is metered monthly across all deployments; inbound request data does not count against it source per-object-cap volume storage is per plan and is the only sandbox resource that differs by plan source not stated
Identity	email (placeholder) not published
Egress	Free plan: 20GiB a month of egress across all deployments; inbound request data does not count; sandbox compute bills through the same egress meter free allowance: 20GiB a month on the Free plan
Per-object cap	not stated
Retention	not stated
Interface	unknown
Reliability	no reliability event recorded
Evidence note	documented the Deploy pricing page was read on 2026-10-22 and defines the meters: active CPU only, memory time, egress and volume storage, with sandbox compute on the same meters. It states the plan structure without naming the free plan's numbers in the extracted text, so the unit is recorded and no figure is invented
Parsed numbers	has-free-tier 1

Evidence 4

date	source	what it proved
2026-10-02	deno.com/deploy/pricing	not published
2026-10-22	deno.com/deploy/pricing	'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.' and 'Run untrusted or generated code in isolated microVMs. Sandbox compute bills through the same CPU, memory, and egress meters at your plan's rates; only availability, concurrency, and volume storage differ per plan.' quoted
2026-11-03	deno.com/deploy/pricing	the Free plan has a 20GiB monthly egress limit
2026-11-03	deno.com/deploy/pricing	sandbox compute uses the same egress meter

More fields 7

keep rate	1.0
billing model	unclassified
session cap	`{"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "CPU bills only while code runs, so a sandbox waiting on I/O costs nothing; the page states no wall clock"}`
free tier kind	allowance
burst x	1.0
ps	`{"gib": null,"price": "volume storage is priced per plan; it is the one sandbox resource plans differ on","durability": "persistent block-storage volume","on_stop": true,"on_destroy": false,"retention": "until deleted"}`
net	`{"out": true,"in": true,"ports": "HTTP","static_ip": false,"ipv6": null,"allowance": "monthly egress allowance; inbound does not count"}`

Unknown values 8

chaining: a source was read and is silent on this field
interface: the access interface was not established
limits note: a source was read and is silent on this field
per object cap stated: a source was read and is silent on this field
reliability note: nothing of this kind was observed
retention notes: the field may be stated in a source that was not read
retention stated: a source was read and is silent on this field
tooling: a source was read and is silent on this field

Deno Deploy (Egress and tunnels)

Egress and tunnels

deno.com/deploy/pricingPaaS L4 portegress/deno-deployJSON compare report an error

Free allowance: Free $0/month ... Requests/month: Allowed inbound HTTP requests to your deployments per month: 1M ...
Verdict: fails: egressdata cannot be read back out at a usable rate or price
Cost: free tier
Identity: emailno card, no phone
Binding limit: volume-quota20 GiB egress per month
Evidence: documented2 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23

Free tier	Free $0/month ... Requests/month: Allowed inbound HTTP requests to your deployments per month: 1M ... Egress Bandwidth: 20GiB. unit GiB; metered on downloaded-bytes
Price	USD 0
Limits	volume-quota (binding) 20 GiB egress per month source request-rate 1M inbound HTTP requests per month source
Binding	volume-quota 20 GiB is 0.020 TiB, and the 1M requests/month cap would bind even earlier for small datagrams. No non-HTTP transport exists.
Identity	email Deno Deploy account; the free plan is $0/month with 10 apps.
Egress	Egress Bandwidth 20GiB per month; inbound request data does not count against it.; ingress: http-only free allowance: Egress Bandwidth 20GiB per month; inbound request data does not count against it.
Interface	cli, rest deployctl, console, and GitHub Actions integration.
Tooling	deployctl, the console, and GitHub integration.
Composes with	Good for an HTTP API or webhook receiver; no endpoint.
Reliability	Idle apps shut down after about 20-30 seconds and scale to zero.
Notes	Deploy Classic was shut down on 2026-07-20, before this read; the current Deno Deploy is the record. Outbound sockets existed for clients, never an inbound port.
Evidence note	documented The request meter is described as inbound HTTP; no page states a UDP or raw TCP listener, and none can be configured.
Parsed numbers	has-free-tier 1 volume-quota 20 GiB price USD 0

Evidence 2

date	source	what it proved
2026-10-23	deno.com/deploy/pricing	Free: 1M inbound HTTP requests/month, 20GiB egress, 10 apps, 10 hr active CPU
2026-10-23	docs.deno.com/deploy/classic/api/runtime-sockets/	Deploy Classic supported outbound TCP sockets and is "Sunsetting on July 20, 2026"

More fields 7

wg path	none
wg detail	Inbound is HTTP requests only: the free tier meters "Allowed inbound HTTP requests to your deployments". There is no port to bind.
ingress	http-only
volume tib month	0.0195
volume stated	Egress Bandwidth 20GiB per month; inbound request data does not count against it.
bytes transit	no
transit note	Deno's edge terminates HTTPS.

Unknown values 2

per object cap stated: the field does not apply to this kind of offer
retention stated: the field does not apply to this kind of offer

Free tier	1 GiB of KV storage on Free. Pricing page, KV section: 'KV storage: 1 GiB'; 'KV read units/mo (4KiB): 1,000,000'; 'KV write units/mo (1KiB): 500,000'. Pro raises KV to 5 GiB. Deployment assets are separately capped: 'the total size of all files within the deployment (source files and static files) should not exceed 1 gigabyte' and Free includes 'Revision storage: 10 GiB'. unit GiB; metered on stored-bytes
Price	none stated
Identity	email (placeholder) not published
Egress	20 GiB/month on Free, metered: 'Egress Bandwidth: Monthly limit on data egress across all your deployments.' Also 1M requests/month. free allowance: 20 GiB per month
Per-object cap	not stated
Retention	not stated
Interface	rest rest
Tooling	`Deno.Kv` API in-runtime; `@deno/kv` client; remote access via the URL connector (`https://api.deno.com/v2/databases/<id>/connect`). No HTTP object endpoint — every read must go through your own code.
Composes with	10 apps per organization on Free, but KV storage is 1 GiB per organization, not per app, so extra apps buy nothing. 1 GiB x N organizations requires N billing identities for 20 TiB — 20,000 accounts. Dead.
Reliability	Durable once written, but 'Deleting a Deno KV database instance ... deletes all existing Deno KV databases and their data' — a single DELETE wipes every KV database in the org, which is a sharp edge. Free-plan service is in public beta with no uptime guarantee.
Parsed numbers	has-free-tier 1

date	source	what it proved
2026-10-21	deno.com/deploy/pricing	Free column: 'KV storage: 1 GiB'; 'KV read units/mo (4KiB): 1,000,000'; 'KV write units/mo (1KiB): 500,000'; 'Egress Bandwidth: 20GiB'; 'Revision storage: 10 GiB'; 'Apps: 10'
2026-10-21	docs.deno.com/deploy/pricing_and_limits/	'should not exceed 1 gigabyte' deployment bundle; 'No uptime guarantees are provided during the initial public beta'
2026-10-21	docs.deno.com/deploy/reference/deno_kv/	'this action deletes all existing Deno KV databases and their data'; last updated June 5, 2026

dead end {"failure_class": "quota","why": "1 GiB of KV storage on Free. Pricing page, KV section: 'KV storage: 1 GiB'; 'KV read units/mo (4KiB): 1,000,000'; 'KV write units/mo (1KiB): 500,000'. Pro raises KV to 5 GiB. Deployment assets are separately capped: 'the total size of all files within the deployment (source files and static files) should not exceed 1 gigabyte' and Free includes 'Revision storage: 10 GiB'.","retry_when": null,"first_recorded": "2026-10-21"}

dead end	`{"failure_class": "quota","why": "1 GiB of KV storage on Free. Pricing page, KV section: 'KV storage: 1 GiB'; 'KV read units/mo (4KiB): 1,000,000'; 'KV write units/mo (1KiB): 500,000'. Pro raises KV to 5 GiB. Deployment assets are separately capped: 'the total size of all files within the deployment (source files and static files) should not exceed 1 gigabyte' and Free includes 'Revision storage: 10 GiB'.","retry_when": null,"first_recorded": "2026-10-21"}`

Unknown values 4

per object cap notes: the field may be stated in a source that was not read
per object cap stated: the field may be stated in a source that was not read
retention notes: the field may be stated in a source that was not read
retention stated: the field may be stated in a source that was not read

deno deploy deployment assets (static file store)

Storage

docs.deno.com/deploy/pricing_and_limits/storage/deno-deploy-deployment-assetsJSON compare report an error

Free allowance: The deployment bundle cap is 1 GB for ALL files in a deployment: 'the total size of all files within the deployment (source files and static files) should not exceed 1 gigabyte.' 'Revision…
Verdict: fails: quotathe free allowance is too small to matter
Cost: not stated
Identity: email?placeholder, not evidence; card unknown, phone unknown
Binding limit: noneno named constraint binds
Evidence: reported2 sources; a third party said so
Freshness: stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05

Free tier	The deployment bundle cap is 1 GB for ALL files in a deployment: 'the total size of all files within the deployment (source files and static files) should not exceed 1 gigabyte.' 'Revision… unit none; metered on none
Price	none stated
Identity	email (placeholder) not published
Egress	not recorded
Interface	unknown
Tooling	not recorded