Deno · Rate Limits

Deno Rate Limits

Deno Deploy enforces per-isolate resource constraints (memory, deployment size) plus monthly quotas (requests, bandwidth, CPU time, memory time, KV reads/writes/storage) per organization rather than fixed per-second request rates. Free hits hard caps; Pro and Builder bill overage at published per-unit rates; Enterprise quotas are negotiated.

Deno Rate Limits is the machine-readable rate-limit profile for Deno on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 8 rate-limit definitions, across the free, pro, builder, all, and enterprise tiers, measuring requests_per_month, gb_per_month, hours_per_month, memory_mb, and bytes.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Edge Compute, Serverless, JavaScript, Runtime, and Rate Limiting.

8 Limits Throttle: 429 Quota: 429
Edge ComputeServerlessJavaScriptRuntimeRate LimitingQuotasThrottling

Limits

Free Tier Monthly Request Quota organization
requests_per_month · month
1000000
Free Tier Egress Bandwidth Quota organization
gb_per_month · month
20
Free Tier CPU Time Quota organization
hours_per_month · month
15
Pro Tier Monthly Request Quota organization
requests_per_month · month
5000000
Builder Tier Monthly Request Quota organization
requests_per_month · month
20000000
Per-Isolate Memory Cap deployment
memory_mb
512
Deployment Bundle Size deployment
bytes
1073741824
Enterprise Negotiated Quota contract
varies
-1

Policies

Quota-Based Throttling
Throttling is enforced via monthly organization-scoped quotas (requests, bandwidth, CPU time, memory time, KV operations and storage), not fixed per-second RPS. Free is hard-capped; Pro and Builder bill overage at published rates.
Spending Limits
Organizations can configure alert thresholds and hard spending limits in the Deno Deploy dashboard to bound overage charges from traffic spikes.
TLS Egress Restriction
Direct Deno.connect to port 443 is prohibited; deployments must use Deno.connectTls or fetch to make outbound TLS calls.
Acceptable Use
Deployments are bound by Deno's acceptable use policy; sustained abuse of shared infrastructure may be throttled or suspended.
Beta SLA
Public-beta features carry no uptime guarantees. Enterprise plans get a 99.95% SLA.