fshy / Compute / Egress and tunnels / Storage

Deno Deploy

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

Deno Deploy Computecaveatemailno cardDretention-clamped
Deno Sandbox Computecaveatemail?card?Drequest-rate
Deno Deploy Egress and tunnelsfails: egressemailno cardDvolume-quota
Deno Deploy (managed Deno KV) Storagefails: quotaemail?card?R
deno deploy deployment assets (static file store) Storagefails: quotaemail?card?R

Deno Deploy Compute

caveatemailno cardDretention-clamped

deno.com/deploy/pricing · cloud VM · compute/deno-deploy · JSON · compare

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
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
Egress	20 GiB a month included on Free; inbound request data does not count free_allowance: 20 GiB
Identity	email a Deno Deploy account; no card on the Free plan
Limits	retention-clamped 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.
Interface	unknown inferred from the tooling the provider documents; not probed
Tooling	not stated
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	Confirms the corpus row. One number moved: the default memory allocation is now 768 MB, where the corpus recorded a 512 MB per-app ceiling. The 150 GiB-hours matches.
Evidence rung	documented the Free plan table and the idle-shutdown sentence were read on the pricing page today
Checked	2026-10-25 (live); stale on 2026-11-24
Parsed numbers	`$.extras.m10h_usd` price USD0.0 / month `$.extras.m24h_usd` price USD0.0 / month `$.limits[1].value` limit:volume-quota 10.0 hours

Evidence (6)

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.'

More fields (10)

{
 "wave2": {
  "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"
 }
}

Unknown or withheld values (2)

$.interface interface-unknown
$.tooling not-stated

Deno Sandbox Compute

caveatemail?card?Drequest-rate

deno.com/deploy/pricing · container and VM sandbox · compute/deno-sandbox · JSON · compare

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
Per-object cap	not stated
Retention	not stated
Egress	not stated
Identity	email (placeholder) not published
Limits	request-rate 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
Binding	request-rate
Interface	unknown
Tooling	not stated
Composes with	not stated
Reliability	no reliability event recorded
Evidence rung	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
Checked	2026-10-23 (live); stale on 2026-11-22

Evidence (2)

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

More fields (15)

{
 "talaria_m10h_usd": 110.0,
 "talaria_m24h_usd": 236.0,
 "nemo_m10h_usd": 44.25,
 "keep_rate": 1.0,
 "keep_rate_basis": null,
 "billing_model": "unclassified",
 "shape": null,
 "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"
 },
 "persistent_storage": null,
 "network_out": null,
 "price_note": null,
 "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 or withheld values (17)

$.chaining not-stated
$.egress.metered egress-unknown
$.egress.terms not-stated
$.evidence[0].proved process
$.extras.keep_rate_basis process
$.extras.price_note process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note not-stated
$.per_object_cap.notes process
$.per_object_cap.stated not-stated
$.reliability_note none-observed
$.retention.notes not-extracted
$.retention.stated not-stated
$.tooling not-stated

Deno Deploy Egress and tunnels

fails: egressemailno cardDvolume-quota

deno.com/deploy/pricing · paas l4 port · egress/deno-deploy · JSON · compare

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
Per-object cap	not applicable
Retention	not applicable
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.
Identity	email Deno Deploy account; the free plan is $0/month with 10 apps.
Limits	volume-quota 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.
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 rung	documented The request meter is described as inbound HTTP; no page states a UDP or raw TCP listener, and none can be configured.
Checked	2026-10-23 (live); stale on 2026-11-22
Parsed numbers	`$.limits[0].value` limit:volume-quota 20.0 GiB `$.price_per_tb_month` price-per-tb USD0.0 TB / month

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 or withheld values (2)

$.per_object_cap.stated not-applicable
$.retention.stated not-applicable

Deno Deploy (managed Deno KV) Storage

fails: quotaemail?card?R

deno.com/deploy · paas · storage/deno-deploy · JSON · compare

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
Per-object cap	not stated
Retention	not stated
Egress	20 GiB/month on Free, metered: 'Egress Bandwidth: Monthly limit on data egress across all your deployments.' Also 1M requests/month. This is 25x short of even one day of the client's serving workload. free_allowance: 20 GiB per month
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
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.
Notes	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'.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (3)

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

More fields (1)

{
 "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 or withheld values (8)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

deno deploy deployment assets (static file store) Storage

fails: quotaemail?card?R

docs.deno.com/deploy/pricing_and_limits/ · rejected-provider · storage/deno-deploy-deployment-assets · JSON · compare

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 s unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	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 s
Notes	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 s
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (2)

date	source	what it proved
2026-10-21	docs.deno.com/deploy/pricing_and_limits/	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 s
2026-10-21	deno.com/deploy/pricing	cited as the basis of the rejection: 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 s

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "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 s",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (15)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded