Translation memory, terminology, and MQM review in one editor. Bring your own AI keys or pay only for what you use. Linguists keep every final call.
We're building locAGI to be the cloud-hosted, audit-ready translation platform the largest localisation programmes need but can't get from today's CAT/TMS vendors. A single managed stack for terminology governance, AI-assisted translation, MQM scoring, and post-processing — with linguists in charge at every step, transparent usage-based billing, and a free tier that actually does real work.
The full CAT environment: source/target editor, TM with concordance, terminology, comments, MQM review. Native — not bolted on.
Scheduled for Q2 2027. We’re stabilising the surface and completing the security audit. Design-partner access is open now — apply here ›
The honest version: substantial pieces are still in flight. We ship in the open so design-partners can see exactly where we stand — not where we’d like to look.
Before any AI touches a segment, we centralise every confirmed term, acronym, and forbidden phrase in a termbase. That way every downstream step — MT, AI post-editing, QA — speaks the same vocabulary as the client.
| EN | DE | Note |
|---|---|---|
| contraindication | Gegenanzeige | § regulatory |
| active ingredient | Wirkstoff | — |
| DO-NOT-TRANSLATE: MedPortal | MedPortal | 🔒 brand |
A template is the client's style guide in one payload: free-text instructions, linked termbases, acronym handling, date / number / currency localisation, register, tone. Link a template once — every AI step after that behaves like the client expects.
MT/AI reads the XLIFF TM match score for each segment and adapts intensity: high matches are barely touched, low matches get a full rewrite. 100% matches stay locked by default. You keep the leverage your linguists already earned in their CAT tool.
When you want every segment rewritten to a target register — not just the low matches — AIPE runs the whole file through an AI model you pick, building a per-file glossary as it goes so terminology and tone stay consistent across long documents — whether the file is 50 segments or 50,000.
Linguists shouldn't waste time on problems a machine can catch first. The Post-Processing stage applies deterministic fixes that need no judgement: tag balance, number consistency with the source, leading / trailing space, consistent punctuation.
| Check | Segments | Verdict |
|---|---|---|
| Tag balance | 3,412 | ✓ clean |
| Numbers match | 3,412 | ⚠ 4 to review |
| Leading/trailing ws | 3,412 | ✓ clean |
| Smart quotes | 3,412 | ⚙ 27 normalised |
AI drafts, humans decide. The cleaned bilingual XLIFF opens in whatever CAT tool the linguist prefers — memoQ, Trados Studio, XTM, Phrase, Wordfast, Smartcat — where they confirm, override, or rewrite the AI output with full TM leverage, concordance, and inline term highlighting. This step is outside locAGI by design: we don't lock you into any one vendor.
| # | Source | AI draft | Linguist |
|---|---|---|---|
| 142 | The patient must take the medication before meals. | Der Patient muss das Medikament vor dem Essen einnehmen. | ✓ confirmed |
| 143 | Consult your doctor. | Konsultieren Sie Ihren Arzt. | ✎ edited |
| 144 | Store at room temperature. | Bei Raumtemperatur lagern. | ✓ confirmed |
After the linguist, a second AI pass reads the finished translation as a reviewer would. It flags potential issues using the industry-standard MQM framework — typed errors with severity 1-5, a suggested revised target, and a comment. You approve, override, or mark as false positive. Export as Excel and annotated bilingual XLIFF.
The final XLIFF carries the linguist's confirmed translation, the QA reviewer's findings baked in as CAT-native comments (so they show up in memoQ, Trados, XTM — wherever the client opens the file), and the quality score as metadata. The Excel export gives the project manager the same findings in a format they can share, filter, and archive.
Six engineering decisions that make locAGI safe to put on your own server, hand to your compliance team, and trust with regulated content.
Long files don't drift. The AI engine carries your project termbase + a running glossary harvested from earlier segments so terminology and tone stay consistent across a 10,000-segment document — not just within a single paragraph. Partial failures retry per-segment so nothing is dropped silently, and the output is deterministic on a repeat run with the same inputs.
Bring your own keys (BYOK): your OpenAI / Anthropic / Google API keys, the call goes straight to the provider, the card you have on file with them is the one charged. Or let locAGI provision the tokens for you on a pay-as-you-go meter — one bill, no procurement work, mix-and-match across users in the same workspace. Your compliance team — not us — decides which providers are allowed for which data.
Need a new rule, a new export format, a new MQM category? Plugin hooks for import, export, QA checks, and MT providers. Customer suggestions that benefit the whole platform are implemented free of charge, typically within a week. You're not paying twice for the roadmap.
Multiple linguists in the same project at the same time — presence indicators show who's where, autosave on every keystroke, live status broadcasts so a reviewer sees your translation the moment you confirm it. Comment threads with @mentions for clarification questions. For freelancers outside your workspace, share findings via secure signed link or hand off a commented bilingual XLIFF + Excel package for offline work in their own CAT — either way the edits flow back automatically.
Every action the UI can perform is available over HTTP: create a project, upload any supported source file (Word, Excel, Markdown, HTML, XLIFF / MQXLIFF / SDLXLIFF, TMX, TBX, and more), launch AI-assisted translation, poll QA status, fetch findings, trigger exports. Wire locAGI into your TMS, your CI, or your project-management tool.
locAGI ingests source documents directly — Word, Excel, Markdown, HTML, JSON, YAML, XML, CSV, plain text. No separate file-prep step, no "first run it through OpenXLIFF yourself." For bilingual workflows you also get the full CAT-tool interop stack: XLIFF 2.0, MQXLIFF (memoQ), SDLXLIFF (Trados), TMX (any TM), TBX (any termbase). Round-trip preserves every tag, every placeholder, every locked segment.
Upload one source file, add as many target languages as you need — locAGI runs MQM review across all of them in one workspace. One translation memory shared across the project, one termbase per project, one MQM scorecard per language. Reviewers see all locales side-by-side; project managers see one rollup. No more juggling six CAT-tool installs to QA six languages, no per-pair licensing math.
Hit one button and the AI rewrites the target using your project glossary, style guide, and the surrounding context. Need an explanation rather than a fix? Open the segment chat and ask the AI a question in plain English — "why did you pick this term?", "what's the formal register equivalent?", "is this idiomatic?". Each segment also gets a predicted next translation you can accept, edit, or ignore. Everything respects your BYOK or pay-as-you-go choice from above.
Sign up free and invite your whole linguistic team — internal staff and contracted freelancers — without paying per head. AI usage runs on tokens we provision (pay-as-you-go) or on your own OpenAI / Anthropic / Google API keys (BYOK). Storage is generous out of the gate; you only pay when you exceed it. Transparent meter, no surprise overage fees.
locAGI is an integrated cloud CAT platform — translation memory, terminology, MQM review, AI-assisted translation — free to sign up, with pay-as-you-go AI or bring-your-own-key. Your projects, your linguists, your linguistic standards — locAGI runs in the background.