Bring your own key.
The translation engine is yours — your contract, your key, your choice. The rest is ours. Here's exactly where the line is.
The engines you can bring
Three today, for voice. You hold the contract and load the key. Taiwa uses it for your calls and nobody else's.
DeepL
DeepL Voice. 37 languages and 9 regional variants. It is the one engine of the three where your own glossary changes the translation today. A German company, and translation is the thing they do.
OpenAI
OpenAI's realtime translation model. OpenAI says it hears more than 70 languages and speaks 13.
Google Gemini
Gemini Live Translate. Google lists more than 70 languages. It is a preview model, which means Google offers no service level on it yet.
You can hold more than one key. Set a default engine, then send a particular language to a particular engine — Japanese to one, everything else to another.
More engines are built and in test. One is listed here only after a real call has run on it, which is the same rule we hold the platforms to. Not every engine runs on every platform yet, so we check your combination during onboarding.
Language counts for OpenAI and Gemini are each supplier's own published figures, October 2026.
What the engine does
All of the translation. Every word your customer says and every word your agent says is recognised, translated and spoken back by the engine you chose.
We didn't build a translation engine, and we aren't going to. Building one is the work of a handful of organisations on earth. Making one usable at 3pm on a Tuesday, inside the call your agent is already taking, is the work we did.
What we do
Everything around it.
Taiwa reads the audio out of a live call in a console that was never built to let anyone do that. It handles the accounts, the language settings and the sign-in. It keeps the customer's original voice playing under the translation so you don't lose what translation can't carry. And it puts all of that inside a call your agents are already taking, without changing your platform.
The engine translates. Taiwa is the part that makes it usable at 3pm on a Tuesday by an agent who didn't ask for a new tool.
Why your key and not ours
Because a reseller sits between you and the terms you're actually agreeing to. With your own key you get the supplier's price, the supplier's data terms and the supplier's invoice, and nothing of ours is hidden inside them.
It also means you aren't tied to one engine. They overtake each other, and none of them is equally good at every language. When another engine becomes the better choice for your calls, you change the key, not the product.
We're not going to reproduce any supplier's accuracy figures here. If you want to know how good the translation is, the honest answer is: try it on your calls, in your languages, with your customers.
Request early access →What this means for your data
Your customers' audio goes to the supplier you chose, under your contract with them. That's not a footnote, it's the architecture, and it's the thing your security reviewer will ask about first.
We've written our half out in full rather than leaving you to infer it. For their half, read theirs — we're not going to paraphrase a supplier's security posture and have you rely on our summary of it.
Where the audio goes →Our other commercial relationships
Kanso names every commercial relationship it has, and Taiwa is one of them — Kanso builds this product and takes the revenue from it. If a Kanso consultant recommends Taiwa to you, that's a recommendation with a stake in it, and Kanso's rule is to say so in writing and name a competing option alongside it.
That rule applies to Taiwa exactly as it applies to everything else.
Kanso's principles →