Architecture
Overview
Section titled “Overview”LokAI is structured around a clear hierarchy of concepts that map directly to how software teams organize their work.
Workspace
Section titled “Workspace”A Workspace is the top-level container for a company or team. Everything in LokAI belongs to a workspace: projects, glossaries, style guides, and tenants.
Project
Section titled “Project”A Project represents a single product or application being localized. Each project has:
- Main languages — the source language(s) that humans own and maintain
- Target languages — languages translated automatically by the LLM
- Secondary languages — additional human-maintained languages
Translation Key
Section titled “Translation Key”A Translation Key is a single translatable string. Keys carry rich metadata:
- A maintainer (the developer or team responsible)
- A description and context
- Per-language translations with ownership and status
- Flags (
do_not_translate,do_not_customize)
Glossary
Section titled “Glossary”A workspace-level Glossary defines preferred and forbidden terms. The LLM respects these rules in every translation it produces.
Style Guide
Section titled “Style Guide”A Style Guide is a Markdown document that instructs the LLM on tone, formality, capitalization, and product-specific conventions.
Tenants
Section titled “Tenants”Tenants are B2B customers who need custom terminology in their translations. Each tenant defines term replacements with natural-language context that the LLM interprets at translation time.
Ownership Model
Section titled “Ownership Model”| Language type | Owner | Write access |
|---|---|---|
| Main languages | Human | Human only |
| Secondary languages | Human | Human only |
| Target languages | LLM | LLM only |
Next steps
Section titled “Next steps”- LLM Pipeline — how AI translation works end to end
- Managing Translation Keys — working with keys in practice