Skip to main content
Ollang is an orchestration layer, not a single-vendor pipeline. Every Order is assembled from independent provider choices — one per pipeline step — so you can mix a best-in-class transcription model with an efficient translation model and a premium voice, and change any one of them without rebuilding the workflow. This catalog documents the providers that are selectable in Workflows today and what each is genuinely good at.

Speech-to-Text

8 selectable transcription providers, from multi-agent to single-model.

Translation and LLMs

27 translation engines and frontier LLMs across 10 model families.

Text-to-Speech

6 voice synthesis engines for AI Dubbing and Audio Description.

Audio Processing

Stem separation that preserves music and effects under dubbed dialogue.

​
The four pipeline steps

Providers are grouped by the step they run in. An Order only runs the steps its Order Type needs.
A Document Translation Order touches only translate. A Closed Captions Order touches only transcribe. An AI Dubbing Order can run all four, so its provider selection is really four decisions rather than one.

​
Reading a provider entry

Every provider in this catalog carries the same three attributes.
The stable machine identifier, for example elevenlabs or anthropic/claude-opus-5. This is the value returned by the List Consumption endpoint and accepted by its filter[provider] parameter, so it is what you match on when you reconcile provider activity programmatically. Display names change; provider tags do not.One tag is reused across steps: aws identifies both Amazon Transcribe in the transcribe step and Amazon Translate in the translate step. Filtering on aws returns rows from both, so narrow with filter[orderType] or check the service field.
Which Order Types can select the provider. Most translation engines serve document, subtitle, and aiDubbing, but there are real exceptions — DeepL is document and subtitle only, and Llama 4 is not available for dubbing scripts. See Order Types for the full enum.
— the provider Ollang uses for that step when a Workflow does not override it.New — recently added and fully supported.Experimental — available for evaluation, behavior may change, and output should be reviewed before it goes to production.

​
Defaults

If you never configure a Workflow, Orders run on these: These defaults favor quality and robustness. Each catalog page also identifies the efficiency-oriented alternatives that suit high-volume or lower-stakes content.

​
Choosing a provider

1

Start from the content, not the benchmark

Leaderboard position rarely predicts localization quality for your material. Clean studio narration, noisy field audio, and code-switched conversation reward completely different models.
2

Check language coverage first

This is the most common reason a Workflow has to be reconfigured. Coverage across the catalog ranges from 7 languages to well over 100, and the highest-accuracy tier of a provider is often narrower than its headline language count.
3

Set a Global Workflow as your baseline

Configure one organization-wide default that is safe for most content, then override per Folder where a specific team or content type needs something different. See Workflows and Provider Architecture.
4

Benchmark with parallel Folders

Run the same source through two Folders with different providers and compare AI QC scores and human edit distance. This is the only measurement that reflects your content and your reviewers.
5

Re-check quarterly

The catalog moves fast — several entries here did not exist six months ago. A provider decision that was correct last quarter is worth re-testing rather than assumed.
Changing a Workflow only affects future Orders. Orders already created keep the providers they were created with, so a provider swap is never retroactive and never changes a deliverable you have already reviewed.

​
Scope of this catalog

The pages in STT APIs, Translation APIs, TTS APIs, and Audio Operations also document engines from the wider localization ecosystem that Ollang can integrate with on request. Those reference pages are useful background, but only the providers listed in this catalog are selectable in Workflows without a custom integration. If you need an engine that is documented but not in the catalog, contact your account team — adding a provider to a workspace is a configuration change, not a product change.