Overview

Workflows inside the Ollang Project Management Dashboard determine:

how Orders are processed,
which providers are used,
which AI models are selected,
how language pairs are configured,
and how localization pipelines operate.

A Workflow is a reusable operational configuration that defines how localization should happen for a specific language pair. Example:

English → French

CC / Transcription:
Ollang Agentic

Subtitle Translation:
OpenAI

AI Dubbing:
Gemini TTS

This allows organizations to:

standardize localization workflows,
benchmark provider quality,
and maintain consistency across multilingual operations.

What is a Workflow?

A Workflow is a reusable configuration that determines:

which providers are used,
which language pair is localized,
how localization is processed,
and how Orders are operationalized.

Instead of manually selecting providers every time, organizations can:

preconfigure workflows,
reuse them across Orders,
and standardize operational quality.

Workflow Scope

Workflows can currently be configured at:

Global Workflow

Default workflow configuration applied across the organization.

Folder-Level Workflow

Folder-specific workflow configuration overriding global settings.

Project-level workflows are not currently supported. Workflows can be configured globally or at the Folder level.

Global Workflows

Overview

Global workflows act as:

organization-wide default workflows.

These workflows automatically apply when:

no Folder-level workflow exists.

Example:

Global Workflow

English → French

CC:
Ollang Agentic

Subtitle Translation:
OpenAI

AI Dubbing:
ElevenLabs

This becomes:

the operational default for all applicable Orders.

Folder-Level Workflows

Overview

Folder-level workflows allow teams to configure localization differently for specific operational use cases. This is useful when:

different teams require different providers,
different content types require different quality standards,
or experimentation is needed.

Example:

Folder A

English → French

CC:
Speechmatics

Subtitles:
Open AI

AI Dubbing:
Gemini

Folder B

English → French

CC:
Ollang Agentic

Subtitles:
Ollang Agentic

AI Dubbing:
ElevenLabs

Even though:

the language pair is identical,

the workflow may differ depending on:

operational requirements,
content type,
and quality expectations.

Workflow Override Logic

Folder-level workflows always override:

Global workflows.

Hierarchy:

Folder-Level Workflow
        ↓
Global Workflow

Example:

Global:
English → French → Provider A

Folder:
English → French → Provider B

Result:

Folder Workflow is used.

Workflow Architecture by Order Type

Different workflows can be configured independently for different localization stages. Supported workflow categories include:

Video Captioning (CC)

Speech-to-text and caption generation workflow.

Subtitle Translation

Translation workflow for multilingual subtitle localization.

AI Dubbing

Voice synthesis workflow including Lip Sync and Audio Description.

Document Translation

Localization workflow for structured and document-based content.

Studio Dubbing

Workflow coordination for studio-managed dubbing operations.

Multiple Workflows for the Same Language Pair

Organizations may configure multiple workflows for the same language pair across different Folders. Example:

Folder A

English → French
CC: Ollang Agentic
Subtitles: Provider A
Dubbing: Gemini

Folder B

English → French
CC: Speechmatics
Subtitles: Provider B
Dubbing: ElevenLabs

This enables:

benchmarking,
experimentation,
quality optimization,
and use-case-specific localization.

Provider Architecture

Overview

Ollang acts as an orchestration layer. Rather than forcing a single provider, the platform enables organizations to:

choose providers,
benchmark providers,
compare results,
and optimize workflows.

This creates operational flexibility because:

The best provider today
may not be the best provider tomorrow.

Organizations can continuously optimize workflows based on:

quality,
speed,
language coverage,
and content type.

Speech-to-Text (STT) Providers

Speech-to-text providers run in the transcribe step and are used for Video Captioning, transcription, subtitle generation, and speaker diarization.

Provider	Languages	Best for
Agentic STT (default)	—	Complex multimedia, noisy audio, multiple language streams
Agentic STT-1.2 (experimental)	—	Benchmarking the next agentic generation
Visual STT (experimental)	—	Silent video and on-screen text
AssemblyAI	99	General-purpose transcription with speech intelligence
ElevenLabs Scribe v2	90+	Under-resourced languages, 32-speaker diarization
Speechmatics	70+	Accented speech; Melia 1 auto-switches languages
Speechmatics with LLM	70+	The same, steered by custom guidelines
AWS Transcribe	100+ locales	AWS-aligned pipelines, nine English locales

Speech-to-Text provider catalog

Accuracy tiers, language coverage, and hallucination risk for every transcription provider.

Translation Providers

Translation providers run in the translate step and cover subtitle translation, document translation, multilingual localization, and dubbing script generation. The catalog spans 27 engines across 10 model families.

Family	Selectable models	Languages
Ollang Agentic (default)	Agentic Localization, Agentic Turbo	100+
OpenAI	GPT-5.6 Sol and Luna, GPT-5.4, GPT-5.2, GPT-5, GPT-4.1, o4-mini	Broad
Anthropic Claude	Claude 5 Fable, Opus, Sonnet; Claude 4.7 / 4.5 Opus; 4.5 / 4 Sonnet	Broad
Google Gemini	Gemini 3.1 Pro, 3.7 Flash, 3 Pro, 2.5 Pro	100+
DeepL	DeepL, DeepL Extended	240+
Amazon	Amazon Translate	75
Cohere	Command A	23
Mistral	Mistral Medium 3.1	50+
Qwen	Qwen3-235B-A22B	119
Llama	Llama 4	12

Two families have order-type restrictions: DeepL serves Document and Subtitle Orders only, and Llama 4 does not serve AI Dubbing. Everything else covers all three.

Translation provider catalog

Model-by-model capability notes, context windows, and order-type support.

Text-to-Speech (TTS) Providers

TTS providers run in the textToSpeech step and are used for AI Dubbing, Audio Description, and multilingual speech generation.

Provider	Languages	Voices	Best for
ElevenLabs Multilingual V2 (default)	29	Cloneable	Premium narration, cross-language voice identity
Cartesia Sonic 3.6	44	Cloneable	Natural conversational delivery, fast turnaround
Gemini TTS	99	30	Widest language reach, multi-speaker dialogue
Azure + ElevenLabs	90+ locales	200+	Voice variety, SSML timing control, custom voices
Deepgram TTS	7	88	Deep English and Spanish accent coverage
OpenAI TTS	50+	13	Instruction-steered delivery at high volume

Text-to-Speech provider catalog

Model versions, voice catalogs, and cloning support.

Audio Processing

AI Dubbing Orders begin with the split step, which separates the dialogue stem from the music-and-effects bed so the original score and sound design survive localization. LALAL.AI (default) — multi-network stem separation with direct synthesis, selectable noise cancelling, and dereverberation.

Audio Processing provider catalog

How stem separation shapes the final dubbing mix.

Workflow Lifecycle

Important Operational Rule

Workflow updates only affect future Orders.

Already-created Orders:

remain unchanged,
preserve their operational workflow,
and continue using the workflow selected at Order creation.

AI Quality Benchmarking

Organizations commonly benchmark providers using:

AI QC Evaluation,
Human QC Annotation,
analytics,
and localization performance tracking.

This helps teams understand:

Which provider works best
for which language pair,
content type,
or workflow.

Because the AI ecosystem evolves rapidly:

The best-performing provider today
may not remain the best tomorrow.

The platform is intentionally designed for:

experimentation,
optimization,
and provider flexibility.

Example Enterprise Workflow

English → French

CC:
Ollang Agentic

Subtitle Translation:
OpenAI

AI Dubbing:
Gemini TTS

QC Evaluation:
Enabled

Example Multi-Folder Benchmarking

Folder A → Marketing Content
English → French
Dubbing: Gemini

Folder B → Entertainment Content
English → French
Dubbing: ElevenLabs

Teams can later compare:

localization quality,
human edit percentage,
QC outcomes,
and operational performance.

Important Operational Notes

Can workflows be configured at Project level?

No. Workflows can currently be configured at Global level and Folder level only.

Do Folder-level workflows override Global workflows?

Yes. Folder-level workflows always take precedence.

Can organizations configure multiple workflows for the same language pair?

Yes. Different Folders may use different workflows for the same language pair.

Do workflow changes affect existing Orders?

No. Workflow updates only affect future Orders.

Can providers be selected independently for CC, Subtitle Translation, and AI Dubbing?

Yes. Different workflow stages can use different providers.

Does Ollang force one provider?

No. Ollang acts as an orchestration layer and allows organizations to choose providers based on operational goals.

​Overview

​What is a Workflow?

​Workflow Scope

Global Workflow

Folder-Level Workflow

​Global Workflows

​Overview

​Folder-Level Workflows

​Overview

​Workflow Override Logic

​Workflow Architecture by Order Type

Video Captioning (CC)

Subtitle Translation

AI Dubbing

Document Translation

Studio Dubbing

​Multiple Workflows for the Same Language Pair

​Provider Architecture

​Overview

​Speech-to-Text (STT) Providers

Speech-to-Text provider catalog

​Translation Providers

Translation provider catalog

​Text-to-Speech (TTS) Providers

Text-to-Speech provider catalog

​Audio Processing

Audio Processing provider catalog

​Workflow Lifecycle

​Important Operational Rule

​AI Quality Benchmarking

​Example Enterprise Workflow

​Example Multi-Folder Benchmarking

​Important Operational Notes

Overview

What is a Workflow?

Workflow Scope

Global Workflows

Overview

Folder-Level Workflows

Overview

Workflow Override Logic

Workflow Architecture by Order Type

Multiple Workflows for the Same Language Pair

Provider Architecture

Overview

Speech-to-Text (STT) Providers

Translation Providers

Text-to-Speech (TTS) Providers

Audio Processing

Workflow Lifecycle

Important Operational Rule

AI Quality Benchmarking

Example Enterprise Workflow

Example Multi-Folder Benchmarking

Important Operational Notes