Route every step to a model that fits, under your provider contracts.
LLM routing for delegated work. Your application hands over a Task and gets one result back. Duale AI runs each part of the Task on a model you enabled.Bring the providers you already trust
Your company keeps its agreements and its rates. Duale AI works within them.Your own models included
Connect the model providers your company already uses, and the models you host yourself. See what each provider supports.
Only the models you enable
Your team decides which models join your model pool. Duale AI never calls a model outside it.
Keys kept out of your applications
Your platform team stores each provider key once, encrypted in the Platform. Duale AI calls the models on behalf of your applications.
Long documents on one model, quick updates on another
Duale AI weighs the skills each part needs against your own priorities for quality, cost and speed.Reading a long document can go to a model built for that, and a simple update to a fast, economical one. Legal analysis, finance, code and multi-step work with Tools can each run on a different model you enabled. See which skills you can ask for.
Your finance team sees inference on your provider invoices and a fixed price per Task from Duale AI, whichever models did the work.
Change models without touching your application
Try a new model on your own Tasks, then keep it or switch back.Usage analytics records which model ran each Task. LLM Coach compares the models in your pool, so you decide each change with evidence in hand.
Illustrative example. Your catalogue team delegates product-sheet translation Tasks every day.
- Day 1. A new model is released. Your platform team adds it to the model pool for evaluation and runs last week’s translation Tasks on it.
- Day 2. LLM Coach shows the new model beside your current ones. The team enables it.
- Day 4. Your reviewers correct more product names than usual. The team switches back to the previous model.
- All week. The catalogue application sent the same Task and received the same result format. Nobody changed its code.
Keep the work moving when a provider has trouble
Duale AI retries a failed call on a model you enabled, within your Task's deadline.The retry can run on the same model or on another one. With models from more than one provider enabled, the work can continue at one provider while another is down.
See it in the work your teams delegate
Each use case shows the result a team gets back.Due diligence
You get one due diligence memo with every finding sourced. Each data room document goes to a model that fits it.
R&D
You get one evidence map with every claim sourced. Reading long papers and writing the synthesis can each run on the model that fits them.
Legal
Your lawyers get one list to act on, each point quoted from its source. Each review runs only on models your company enabled.
Before you connect your model providers
One fixed price per Task
A standard Task costs €0.10 and a fast Task €0.20, excluding VAT. See pricing
Your providers, your contracts
Your model providers bill you directly for inference.
Your choice of hosting
Use the managed service, hosted in the European Union, or run the Platform in your own infrastructure.
Model routing questions
Yes, and the rest of your work can still use every model you enabled. Check in Usage analytics which model ran each Task, and see how to isolate work bound to one model.
No. They process your data under your own agreements, not under Duale AI’s. See how the Trust Center covers the providers you choose, and read the AI services section of the subprocessor list.
No. A stored key is never shown again, even to the people who manage your models; they can only replace it. Read how a stored key stays hidden.
Yes. Charts, photos and scanned pages in your documents reach a model you enabled that reads images, so the result draws on them too. See how agents read your documents with Libraries, and see what decides whether an image reaches a model.