Launched this week
LayerAI
Local-first web translation you finalize and reuse
8 followers
Local-first web translation you finalize and reuse
8 followers
LayerAI is a local-first Chrome extension for web translation: collect text, batch AI draft, finalize yourself, then auto-apply confirmed translations on revisit. Unlike one-shot page translators, you keep editable translation assets, glossary control, a background queue for large sites, and BYOK / local Ollama — so terminology and privacy stay under your control.
Free Options
Launch Team / Built With
love the editable glossary and batch workflow, super useful for translating docs with consistent terminology. one thing that would help a lot: a diff view before applying, so i can see exactly which strings changed and quickly catch any hallucinations from the ai draft before they go live on revisit
@hayrettinyqn0v Thanks Hayrettin — editable glossary + batch draft is the core loop we care about. Diff-before-apply is a great call: especially useful for catching AI hallucinations before they land on revisit. Putting it on the shortlist. If you have a preferred UX (side-by-side vs inline highlight), tell me which you’d actually use daily.
the way you keep the translation assets editable and let people own their glossary is genuinely smart. most translators treat it like a fire and forget thing but this feels closer to how translators actually work on big sites.
Love that it keeps my edits for next time instead of re-translating the same UI strings on every visit. The local Ollama option is a big plus for the docs I work with.
@fratgzelsodszj Thanks Fırat — that’s exactly the workflow we built for. Glad local Ollama helps. If you try it on a real docs/admin site, tell me what still feels clunky (queue, glossary, or re-apply). Happy to prioritize.
The editable translation assets with glossary control are a really thoughtful choice, finally someone gets that translators need to own their terminology instead of trusting a black box each time.
@nurcanc8nn Thanks Nurcan — that was the design goal. Terminology shouldn’t reset every visit; you should own the glossary and the finalized lines as reusable assets. If you try it on a real project, tell me where glossary still feels weak (import, match rules, or per-site scopes).