Serve it
LM-Kit One: the sanctioned translator
One authenticated endpoint replaces the banned tools: intranet forms, helpdesk macros, and pipelines all call the same governed service, and the audit trail shows translation happening inside the walls.
Use case
Translate everything. Leak nothing.
Most companies quietly banned free translators without providing an alternative, so confidential text still gets pasted into them daily. This is the alternative.
The oldest leak vector in the office.
Translation demand is constant, the sanctioned tools are absent, and the free ones are one paste away. That gap is a policy on paper and a leak in practice.
- Confidential by default. The texts that need translation, contracts, support threads, board notes, incident reports, are precisely the ones that must not reach a third-party service.
- Bans without alternatives fail. Blocking translator sites moves the pasting to personal phones; only a sanctioned tool that is actually better ends the behavior.
- Terminology drifts. Generic engines translate your product names, legal terms, and internal vocabulary differently every time; example-guided translation keeps your glossary in force.
- Per-character meters cap adoption. When translation is billed by volume, teams translate less than they should; localization and multilingual support suffer first.
- Speech is the forgotten half. Multilingual meetings and calls need live speech translation, not a transcript mailed to a vendor afterward.
Detect, translate, keep the terms, deliver.
One local engine covers the text path and the speech path, so nothing about being multilingual requires being exposed.
02
Translate
100+ languages on-device, for snippets, threads, and whole documents.
03
Keep terms
Example pairs teach the engine your glossary, so vocabulary stays yours.
One engine, two ways to deploy it.
The scenario decides the form: a translation endpoint for the whole company, or translation living inside your own software.
Embed it
LM-Kit.NET: translation as a feature
Ship in-product translation in your .NET application: document tools, support consoles, field software that works offline, with no per-character cost attached to your feature.
What makes it the sanctioned tool.
Better than the banned option, not just safer: that is what actually changes behavior.
Private
Zero external calls
The text never leaves your infrastructure; verify it with your own firewall rules rather than a vendor's privacy page.
Consistent
Your glossary, enforced
Example-guided translation applies your terminology on every pass, so product names and legal phrases stop mutating between documents.
Complete
Text and speech, one engine
Documents, threads, and live meetings share the same local pipeline; being multilingual stops being a data-handling event.
Both forms, working code.
One REST call for the company endpoint; one class with a glossary for the embedded form.
The company translation endpoint, callable from any tool or script.
curl http://your-server:5189/lmkit/v1/translate \
-H "Authorization: Bearer your-server-token" \
-H "Content-Type: application/json" \
-d '{"input":"Le contrat prend effet à la signature.",
"language":"English"}'The embedded engine, with example pairs teaching your terminology.
using LMKit.Model;
using LMKit.Translation;
var model = LM.LoadFromModelID("qwen3.5:4b");
var translator = new TextTranslation(model);
string english = translator.Translate(supportThread, Language.English);
string german = translator.Translate(contractClause, Language.German);The technology underneath.
The pipeline composes documented capabilities you can inspect on their own.
Translate
Text translation
100+ languages with example-guided terminology, entirely on-device.
How translation worksDetect
Language detection
Text and documents identified across 100+ languages before routing.
How detection worksSpeak
Speech translation
Live translation of meetings and calls while they are transcribed.
How speech translation worksDocuments
Document conversion
PDFs and Office files become translatable text and return to shape.
How conversion worksPolish
Text enhancement
Tone and style rewriting keeps translated output in your voice.
How enhancement worksRelated
Meeting transcription
The speech-side use case this one completes for multilingual teams.
The transcription use caseFrequently asked questions.
How is this different from blocking online translators?
A ban removes the tool but not the need, so the pasting moves somewhere less visible. A sanctioned endpoint that is faster, respects your terminology, and costs nothing per use replaces the behavior instead of hiding it.
Which languages are covered?
The translation engine covers 100+ languages, with automatic language detection for routing and speech translation for live audio. Quality per language pair depends on the model you choose; evaluate on your real content.
Can it keep our product names and legal terms consistent?
Yes. Example-guided translation takes pairs from your glossary and applies them across every pass, so domain vocabulary stops mutating between documents and translators.
What does high-volume translation cost?
There is no per-character meter. Whether it is one clause or the entire support archive, the cost is your hardware's time, which is what makes company-wide adoption viable.
Private AI, multilingual