Increase the CPU time on Edge Functions, even billing it

Summary The current 2-second CPU time limit for Supabase Edge Functions is quite restrictive for many real-world use cases. While the ultra-low latency is great for short tasks, sometimes we need more like AWS Lambda that gives 15 minutes freely Processing larger payloads Calling external APIs that take longer to respond Generating dynamic content Coordinating actions across multiple services (e.g. 3rd-party APIs) I would personally be willing to pay for increased limits, even if that meant being billed similarly to AWS Lambda (based on duration). Why is this important? Supabase is an amazing platform for quickly building apps. It combines database, auth, storage, and serverless functions — all in one place — making it incredibly convenient and organized. However, when a use case outgrows the CPU limits of Edge Functions, we’re forced to move away from Supabase into AWS or another platform, just for that one part. This breaks the cohesion of the stack. Even w…