Actually @zucchi0657 migrating your entire system only to hit concurrency limits is tough. Concurrency limits apply at the organization level, not per account. This is standard across most API platforms. The default varies by plan (typically 10-50 concurrent calls), but you can request increases from Vapi support. How big apps handle this: They get their limits increased (Vapi is flexible for legitimate use cases), implement call queuing, or use multiple organizations for different client segments if needed. Python/Node.js wouldn’t change this - the limit is on Vapi’s side regardless of how you make the API calls. Multi-tenancy in one org is actually the right approach. Check out Vapi’s limits documentation here: https://docs.vapi.ai/limits This is fixable. Happy to help you architect a solution around this if you need freelance support. You’re not stuck, just need the right limit configuration.