Loading…
Loading…
Google Vertex · LLM fallback + TTS for non-Latin scripts
When ai-gateway routes by preferredProviderForLocale (target language has non-Latin script + premium tier), requests go to Vertex gemini-2.5-pro. Vertex TTS handles all 56 locales including ones OpenAI TTS doesn't cover well (Arabic, Mandarin, Korean, Japanese).
Integration shape
ai-gateway routes premium-tier requests with target_language in non-Latin scripts to Vertex gemini-2.5-pro. Google response is translated back into OpenAI chat-completions shape so callers don't have to learn two formats. TTS via Vertex's text-to-speech API; voices selected per locale. WaveNet voices for premium tier; standard voices for free tier.
Value exchange
Google Vertex gets: large-scale edtech usage of Gemini + TTS + translation services. Koydo gets: native-language LLM quality for non-Latin scripts (where OpenAI sometimes weaker), 220+ TTS voices across 56 locales, redundancy for OpenAI outages, regional data residency options.
Fit note
Vertex is the secondary cloud provider. Per AI Runtime Law: AFM first → OpenAI fallback → Vertex secondary → deterministic template. Vertex's strongest application is TTS coverage (broader voice catalog than OpenAI) + non-Latin LLM quality.