We built a production voice command center handling 8 concurrent AI agents, 8 automation workflows, and real-time state management across 5 frontend interfaces—all on Supabase Edge Functions, VAPI's voice API, and Vercel deployments. This article breaks down the architecture: how we designed an 8-table Postgres schema to coordinate valet trash operations, real estate wholesaling, and credit repair workflows through a single webhook listener; how we structured VAPI agent callbacks to trigger state mutations without race conditions; and the specific infrastructure decisions that let us ship this from a self-hosted Asterisk PBX backbone. If you're running a service business (field ops, logistics, customer contact) and considering voice automation, this is the technical blueprint we used to move from proof-of-concept to production at Load Bearing Empire.
Backend
Building a Multi-Agent Voice Command Center: Load Bearing Empire's QHV Stack on Supabase, VAPI, and Vercel
dev.to DevOps0 views
Source：https://dev.to/domoniqueluchin/building-a-multi-agent-voice-command-center-load-bearing-empires-qhv-stack-on-supabase-vapi-and-1ie3
PreviousGo Profiling in Production: pprof, Flamegraphs and Memory LeaksNextA crontab entry for a second weekly film, and the UTC hour it hides
Related posts
FiveM Script Database Migrations: What to Check Before You Install
0dev.to
The insurance edge case that breaks event-driven policy pipelines
0dev.to
The fix for an empty state isn't filling it
0dev.to UX
Five Things That Make Dependabot Painful for Terraform
0dev.to GitHub
Tracking Roblox player counts: what the public data actually gives you
0dev.to Data
Telegram gold signals this week: results to Oct 30
0dev.to Data