Supabase Edge Functions pricing
Supabase · Edge FaaS (per invocation, Deno) · snapshot captured June 2026
Supabase Edge Functions is priced as edge faas (per invocation, deno). 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). It scales to zero, so you pay nothing while idle. Egress: Egress counts against the project's overall bandwidth allowance.
Source: Supabase pricing. Data as of June 2026.
Supabase Edge Functions pricing at a glance
| Cost factor | Supabase Edge Functions |
|---|---|
| Pricing model | Edge FaaS (per invocation, Deno) |
| Per 1M requests | $2.00 / 1M |
| Per GB-second | n/a |
| Free tier | 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 (no charge when idle) |
| Egress | Egress counts against the project's overall bandwidth allowance. |
| Regions | Global edge (Deno-based) across Supabase regions. |
Source: Supabase pricing page. Data as of June 2026.
Source: Supabase pricing. Snapshot June 2026 — verify on the vendor's pricing page. Serverless pricing changes frequently.
Worked example
A small API doing 1,000,000 requests/month, each running ~200 ms at 256 MB of memory (≈50,000 GB-seconds/month):
Supabase Edge Functions is not billed per request — it uses edge faas (per invocation, deno), so a per-request figure is not comparable. 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). Use the platform's own model for this workload.
Computed from the committed June 2026 snapshot rates. See the calculator to change the assumptions, and methodology for the formula.
Cost pros & cons
Where Supabase Edge Functions saves money
- Simple per-invocation pricing (no GB-second math)
- Tight integration with Supabase Postgres/Auth/Storage
- Deno runtime with global edge execution
Watch-outs
- Higher per-million-invocation rate ($2) than Lambda/Cloudflare
- Best value only if you already use Supabase
- Less control over compute/memory tuning
Supabase Edge Functions vs similar platforms
How Supabase Edge Functions compares with related serverless platforms on the headline rates:
| Platform | Model | Per 1M req | Per GB-s | Egress |
|---|---|---|---|---|
| Supabase Edge Functions (this platform) | Edge FaaS (per invocation, Deno) | $2.00 / 1M | n/a | varies |
| AWS Lambda | FaaS (request + GB-second) | $0.20 / 1M | $0.0000167 / GB-s | $0.09/GB |
| Cloudflare Workers | Edge FaaS (request + CPU-ms) | $0.30 / 1M | n/a | Free |
| Google Cloud Run | Serverless containers (vCPU-s + GiB-s + request) | $0.40 / 1M | $0.0000025 / GB-s | varies |
| Google Cloud Functions | FaaS (now on Cloud Run model) | $0.40 / 1M | $0.0000025 / GB-s | varies |
| Azure Functions | FaaS (Consumption / Flex Consumption) | $0.20 / 1M | $0.000016 / GB-s | varies |
Frequently asked questions
How much does Supabase Edge Functions cost?
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.
Does Supabase Edge Functions have a free tier?
Yes — and it renews every month, not just for the first year. 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).
Does Supabase Edge Functions scale to zero?
Yes — Supabase Edge Functions scales to zero, so you pay nothing while it is idle (you are billed only for actual usage). Free plan: 500,000 Edge Function invocations/month.
What does Supabase Edge Functions charge for egress?
Egress counts against the project's overall bandwidth allowance. Egress is one of the most overlooked serverless costs, so model your outbound data when comparing platforms.
Keep exploring
Source & accuracy
Figures are a dated snapshot from Supabase's pricing page (snapshot captured June 2026). The worked example is a transparent calculation over those inputs (see methodology). Serverless pricing is volatile and varies by region, memory tier and discounts — verify current prices on the vendor's page before relying on them. This is an informational comparison, not a quote.
Last updated: 2026-06-21