Deno Deploy vs Supabase Edge Functions: pricing
Deno Deploy and Supabase Edge Functions both bill by resource-time rather than per request. Deno Deploy is edge faas (requests + cpu-time) ($2.00 / 1M) and Supabase Edge Functions is edge faas (per invocation, deno) ($2.00 / 1M). Snapshot June 2026 — verify on the vendor's pricing page.
Data as of June 2026.
Deno Deploy vs Supabase Edge Functions side by side
| Cost factor | Deno Deploy | Supabase Edge Functions |
|---|---|---|
| Vendor | Deno | Supabase |
| Pricing model | Edge FaaS (requests + CPU-time) | Edge FaaS (per invocation, Deno) |
| Per 1M requests | $2.00 / 1M | $2.00 / 1M |
| Per GB-second | n/a | n/a |
| Free tier | Free: 1,000,000 requests/month + 20 GB egress + 15 CPU-hours. Pro is $20/mo with 5M requests + 200 GB egress + 40 CPU-hours; overage $2 per 1M requests + $0.50/GB + $0.05/CPU-hour. | Free plan: 500,000 invocations/month. Pro/Team: 2,000,000 invocations included, then $2 per additional 1M invocations. Billed per invocation only (compute folded in). |
| Scale to zero | Yes | Yes |
| Egress | $0.50/GB | varies |
| Regions | Global edge network (V8 isolates). | Global edge (Deno-based) across Supabase regions. |
Sources: Deno pricing · Supabase pricing.
Sample monthly cost
A rough monthly total for a sample workload: 5,000,000 requests/month, each ~150 ms at 256 MB of memory, plus 25 GB of egress. Computed after each platform's free tier; excludes platform minimums and regional variation, so treat it as a starting point:
| Component | Deno Deploy | Supabase Edge Functions |
|---|---|---|
| Compute (after free tier) | Usage-based | Usage-based |
| Egress (25 GB) | $13 | varies |
| Estimated total / month | Usage-based | Usage-based |
Verdict
On cost for this sample workload, Deno Deploy and Supabase Edge Functions both bill by resource-time rather than per request. But price is not the only factor: Deno Deploy (native typescript/javascript edge runtime, fast cold starts) versus Supabase Edge Functions (simple per-invocation pricing (no gb-second math)). Read each platform's full breakdown — Deno Deploy and Supabase Edge Functions — and model your own workload in the calculator.
Frequently asked questions
Is Deno Deploy or Supabase Edge Functions cheaper?
For a sample workload of 5M requests/month at 256 MB, 150 ms each plus 25 GB egress, Deno Deploy and Supabase Edge Functions both bill by resource-time rather than per request. This is illustrative and after each platform's free tier; your real cost depends on memory, duration, egress and region. snapshot captured June 2026.
How do Deno Deploy and Supabase Edge Functions price requests?
Deno Deploy: Free: 1M requests + 20 GB egress + 15 CPU-hours/month. Pro ($20/mo): 5M requests + 200 GB egress + 40 CPU-hours, then $2 per additional 1M requests, $0.50/GB egress, $0.05/CPU-hour. Supabase Edge Functions: Per-invocation billing: 500k/month free, 2M included on Pro/Team, then $2 per additional 1M invocations. Built on the Deno runtime. Compute time is folded into the per-invocation price (no separate GB-second meter). Snapshot June 2026 — verify on the vendor's pricing page.
Do Deno Deploy and Supabase Edge Functions scale to zero?
Deno Deploy: yes, no charge when idle. Supabase Edge Functions: yes, no charge when idle. Scale-to-zero saves money for spiky traffic but adds cold-start latency on the first request.
Which has the better free tier, Deno Deploy or Supabase Edge Functions?
Deno Deploy: Free: 1,000,000 requests/month + 20 GB egress + 15 CPU-hours. Pro is $20/mo with 5M requests + 200 GB egress + 40 CPU-hours; overage $2 per 1M requests + $0.50/GB + $0.05/CPU-hour. Supabase Edge Functions: Free plan: 500,000 invocations/month. Pro/Team: 2,000,000 invocations included, then $2 per additional 1M invocations. Billed per invocation only (compute folded in).
More comparisons
Last updated: 2026-06-21