mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 01:45:10 +03:00
Pro plan increased from 500 to 1000 functions per project, Team from 1000 to 2000. ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? docs update for function limits ## What is the current behavior? The function limits for Pro and Team plans are 500 and 1000 respectively in the docs. ## What is the new behavior? The function limits are updated to 1000 and 2000 for Pro and Team plans in the docs to match the updated limits in the backend. ## Additional context <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated platform limits for Pro plans to support up to 1,000 functions per project. * Updated platform limits for Team plans to support up to 2,000 functions per project. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
44 lines
2.1 KiB
Plaintext
44 lines
2.1 KiB
Plaintext
---
|
||
id: 'functions-limits'
|
||
title: 'Limits'
|
||
description: "Limits applied Edge Functions in Supabase's hosted platform."
|
||
subtitle: "Limits applied Edge Functions in Supabase's hosted platform."
|
||
---
|
||
|
||
## Runtime limits
|
||
|
||
- Maximum Memory: 256MB
|
||
- Maximum Duration (Wall clock limit):
|
||
This is the duration an Edge Function worker will stay active. During this period, a worker can serve multiple requests or process background tasks.
|
||
- Free plan: 150s
|
||
- Paid plans: 400s
|
||
- Maximum CPU Time: 2s (Amount of actual time spent on the CPU per request - does not include async I/O.)
|
||
- Request idle timeout: 150s (If an Edge Function doesn't send a response before the timeout, 504 Gateway Timeout will be returned)
|
||
|
||
## Platform limits
|
||
|
||
- Maximum Function Size: 20MB (bundled locally via the CLI) or 5MB (bundled server-side, e.g. via the Management API or Dashboard)
|
||
- Maximum no. of Functions per project:
|
||
- Free: 100
|
||
- Pro: 1000
|
||
- Team: 2000
|
||
- Enterprise: Unlimited
|
||
- Maximum log message length: 10,000 characters
|
||
- Log event threshold: 100 events per 10 seconds
|
||
- Recursive/Nested Function Calling: ~5000 requests per minute [more details](/docs/guides/functions/recursive-functions)
|
||
|
||
### Secrets
|
||
|
||
- Maximum number of secrets per project: **100**
|
||
- Secret name length: up to **256** characters
|
||
- Maximum secret size: **48 KiB** (**24,576** characters)
|
||
- Names must NOT start with the prefix `SUPABASE_` (this prefix is reserved).
|
||
|
||
## Other limits & restrictions
|
||
|
||
- Outgoing connections to ports `25` and `587` are not allowed.
|
||
- Serving of HTML content is only supported with [custom domains](/docs/reference/cli/supabase-domains) (Otherwise `GET` requests that return `text/html` will be rewritten to `text/plain`).
|
||
- Web Worker API (or Node `vm` API) are not available.
|
||
- Static files cannot be deployed using the API flag. You need to build them with [Docker on the CLI](/docs/guides/functions/quickstart#step-6-deploy-to-production).
|
||
- Node Libraries that require multithreading are not supported. Examples: [`libvips`](https://github.com/libvips/libvips), [sharp](https://github.com/lovell/sharp).
|