Increase the CPU time on Edge Functions, even billing it

[JVini0166]

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 with AWS' broad service ecosystem, I would prefer to pay Supabase to keep everything in one place. It’s more manageable, especially for solo devs and small teams. I know others in the community feel the same.

Thanks for building such a powerful and dev-friendly platform!

I would give you guys all my money that I pay for AWS if you guys had more CPU time hahah

[toy-crane]

I totally agree his opinion.
It is too short to use AI functionalities.

Currently, I am considering migrating the API due to frequent CPU timeouts
Please make sure to support this feature so it stays on Supabase

[tracklazy]

FUCK 2 DAYS NO ONE ANSWER ???? Subject: URGENT: My Project Is Blocked After Clicking Backup #37085

SUPABASE EMAIL : garifiltet@gmail.com

Dear Supabase Support Team,

I am reaching out urgently regarding a serious issue with my project.

After I clicked the “Backup” button in the dashboard, my entire Supabase project became blocked and is now completely inaccessible. This unexpected downtime has severely impacted my work.

I am currently on a Pro plan, and I expect reliable service and responsive support. I’ve already submitted a support request, but I have not received any resolution or update.

Please investigate and restore access to my project immediately. If additional action is needed on my side, kindly provide clear instructions.

This issue is extremely urgent.

Thank you for your prompt support.

Best regards,
Hamza

[cprcrack]

I agree, 2 seconds of CPU time is too little. I'm also willing to pay more if needed, but having to switch to another provider because my server functions are CPU intensive (at least 4 seconds in my case) is a pain in the ass.

[sourman]

My current work around is to run a bunch of EDGE funcitons that respawn themselves when they are about to die or have pgmx to keep track of who died and pick up the work. It is really nasty stuff. I mostly need this for cron jobs that run a day. Would be amazing if Supabase introduced Supabase EDGE Heavy with relaxed latency guarantees than EDGE but large CPU compute allowance

[JulienLecoq]

News? It's been years that it is a problem...