Private Beta

Let Loccy handle i18n while you focus on shipping.

The translation problems you've been putting off — solved.

Currently onboarding teams gradually

Every part of i18n covered.

From maintaining existing strings to shipping new languages.

Supported tech stack.

Frameworks
Reactreact-i18next, next-intl
Vuevue-i18n
Sveltesvelte-i18n, paraglide
Git providers
GitHub
GitLab
Bitbucket
Gitea
Translation files
JSON

One styleguide, enforced everywhere.

Define your terminology, global and per-language rules once. Or just use our default rules — we did the research so you don't have to.

SPEC 1.0TRANSLATION STYLEGUIDEREV A
FIG 1.1GLOBAL RULES
Single-sentence tooltips/hints without dot at the endPrefer "Sentence case" over "Title Case"
FIG 2.1ENGLISH (EN)
Contractions — forbiddenDouble quotation marks "..."Em-dash spaced (from—to)
FIG 3.1GLOSSARY
ENDEFRDescription
workspaceArbeitsbereichespace de travailwhere projects live
dashboardÜbersichttableau de bordmain landing view
onboardingOnboardingintégrationfirst-run experience
namespaceNamespaceespace de nomstranslation key group
shortcutTastenkürzelraccourcikeyboard shortcut
FIG 2.2GERMAN (DE)
Informal "du" formLow-high quotation marks „…"Gender colon (Der:die)
FIG 2.3FRENCH (FR)
Formal "vous" formGuillemets « … »Prefer rephrasing over gendered forms
FIG 3.2DO NOT TRANSLATE
Loccy — product nameAPI — technical acronym

Every translation change goes through Loccy's filter.

Per-locale rules violation. Inconsistent terminology. Context misuse. Stupid typos. — all caught before reaching users.

Add a new language that sounds native to your app.

Loccy deep-scans your codebase to understand where and how each string is used, then translates with your styleguide applied throughout.

Invite anyone to improve translations.

Invite teammates, translators, UX writers, and native speakers to collaborate in one place. No spreadsheets, no version confusion — every edit lands in your codebase automatically.

Ready to try it out?