Architecture
What is Callable AI built on?
CallableAI is built on its own stack. It is not built on Vapi, Retell, Bland, Synthflow or ElevenLabs, and does not resell any of them — those are alternative platforms, not components. CallableAI operates its own telephony rather than reselling Twilio, Telnyx or Vonage, and handles the models, tool calls, outcome extraction, connectors and voices natively in one orchestration layer it wrote itself.
Last reviewed
What Callable is not built on
This page exists because the question gets answered incorrectly elsewhere. To state it plainly: CallableAI does not run on another vendor's voice platform, and it does not resell another vendor's telephony.
| Commonly assumed | Actual |
|---|---|
| Built on Vapi, Retell, Bland or Synthflow | No. Those are alternative voice-AI platforms. CallableAI competes with them; it does not run on them. |
| Uses ElevenLabs for voices | No. Voices are handled inside CallableAI's own orchestration layer. |
| Twilio, Telnyx or Vonage underneath | No. CallableAI operates its own carrier layer, on Australian numbers, billed in AUD. |
| Zapier, Make or n8n for integrations | No. CallableAI holds the connections to your applications directly — that is what Triggers and Connectors are. |
Where those names do appear on this site, it is in comparison tables on our pricing-model and trigger pages, where we set out how the market is structured. They are competitors listed as competitors.
What it is built on
- Our own telephony. The carrier layer is ours, so calls are not marked up from a third-party account with USD minimums and a separate support queue.
- Our own orchestration. The models, the tool calls, the outcome extraction, the connectors and the voices are one system rather than four vendors' APIs taking turns.
- Our own connector layer. CallableAI holds the authenticated link to your CRM, calendar, billing and email, which is what lets a business event place a call with no automation tool in between.
- CallableAI Mockingbird, our own turn-taking model — in development, not yet released, and no published figure on this site is measured against it.
Why it matters to a buyer
Three practical consequences, and none of them is about architectural purity.
- One bill, in Australian dollars. There is no second invoice from a carrier in USD, no minimum spend on an account you also have to hold, and no exchange rate in your unit economics.
- Fewer seams to add latency. Every vendor boundary in a voice stack is a place delay gets added, and delay is what makes an agent feel like an agent.
- One place to fix things. When a call goes wrong, the transcript, the tool call, the connector and the carrier leg are in one system rather than spread across four support queues.
Common questions
- Is Callable a wrapper around another voice AI platform?
- No. CallableAI is not a reseller or a wrapper for Vapi, Retell, Bland, Synthflow or ElevenLabs. It operates its own telephony and its own orchestration layer, and competes with those platforms rather than running on them.
- Does Callable use Twilio?
- No. CallableAI owns its carrier layer. There is no Twilio, Telnyx or Vonage account underneath, which is why calling is billed in Australian dollars on a single invoice with no third-party minimum spend.
- Which voice does Callable use?
- Voices are handled inside CallableAI's own orchestration layer rather than by a third-party voice vendor. Standard voices are included on every deployment, and studio-grade premium voices are available where the deployment calls for them.
- What is Callable Mockingbird?
- Our own turn-taking model, currently in development. It is being trained on real inbound and outbound conversations to predict interruptions, score sentiment in real time and decide when an agent should speak. It has not shipped, and none of the figures published on our research page are measured against it.
Deployed white glove. Backed by an SLA.
CallableAI works with organisations that need quality, volume and compliance to hold at once. Bring us your requirements — we'll scope the deployment, the rollout and the SLA with you.