Supabase Edge Functions
A serverless function runtime provided by Supabase, built on Deno and deployed at edge nodes worldwide. It resides in the same project as the Postgres database, can access the database directly, and follows RLS policies, making it suitable for low-latency webhook processing scenarios.
Timeline (last 90 days)
The team's entire system has no dedicated server; everything runs on serverless functions.
The Quiet Hours Valet Command Center team's frontend is deployed on Vercel, its backend uses Supabase Edge Functions to host 8 automation workflows, and its voice layer connects to VAPI through an Asterisk PBX to complete orchestration.
Edge Functions have no persistent process for deduplication, so the processing logic for each event must carry its own idempotency key, typically implemented as a unique constraint in Postgres.
The team put the routing logic at the Edge Function layer: based on the caller number or webhook metadata, it decides which Agent's processing flow an event is dispatched to.
Supabase Edge Functions is a Deno-based edge runtime suitable for low-latency, short-lived tasks such as webhooks, and it connects directly with Supabase's Postgres and authentication system.
The voice command center system is built and deployed using Supabase Edge Functions, the VAPI voice API, and Vercel.
Supabase Edge Functions is a Deno-based serverless function runtime deployed on global edge nodes, and it belongs to the same project as Supabase's Postgres, Auth, and Storage.
For larger scales beyond 8 concurrent agents (such as dozens or hundreds), whether Postgres row locks and Edge Functions concurrency limits will become bottlenecks is not given data in the original text and is an unknown that needs to be considered when evaluating.
Supabase Edge Functions have execution duration and concurrency limits, and when logic is too heavy it pushes the pressure onto the database connection pool.
All Facts (10)
Edge Functions在CDN边缘节点上运行，冷启动时间通常在5ms以内，典型实现包括Cloudflare Workers、Vercel Edge Functions和Supabase Edge Functions
80%UnverifiedThe team put the routing logic at the Edge Function layer: based on the caller number or webhook metadata, it decides which Agent's processing flow an event is dispatched to.
50%UnverifiedThe Quiet Hours Valet Command Center team's frontend is deployed on Vercel, its backend uses Supabase Edge Functions to host 8 automation workflows, and its voice layer connects to VAPI through an Asterisk PBX to complete orchestration.
50%UnverifiedThe team's entire system has no dedicated server; everything runs on serverless functions.
50%UnverifiedEdge Functions have no persistent process for deduplication, so the processing logic for each event must carry its own idempotency key, typically implemented as a unique constraint in Postgres.
50%UnverifiedSupabase Edge Functions is a Deno-based edge runtime suitable for low-latency, short-lived tasks such as webhooks, and it connects directly with Supabase's Postgres and authentication system.
50%UnverifiedThe voice command center system is built and deployed using Supabase Edge Functions, the VAPI voice API, and Vercel.
50%UnverifiedSupabase Edge Functions is a Deno-based serverless function runtime deployed on global edge nodes, and it belongs to the same project as Supabase's Postgres, Auth, and Storage.
50%UnverifiedSupabase Edge Functions have execution duration and concurrency limits, and when logic is too heavy it pushes the pressure onto the database connection pool.
50%UnverifiedFor larger scales beyond 8 concurrent agents (such as dozens or hundreds), whether Postgres row locks and Edge Functions concurrency limits will become bottlenecks is not given data in the original text and is an unknown that needs to be considered when evaluating.
50%