Translation management · Edge-native
Manage the copy of your app, shop and website in one place – in every language. Maintain once, ship everywhere. No more copy-paste across three systems.
button.submit button.cancel error.required The problem
A new button label has to be updated separately in the app, the shop and TYPO3. Three times copy-paste, three new places to get it wrong.
Which strings are still open in French? Which were never reviewed? Without an overview, localization is flying blind.
Copy lives in repos and exports. Non-developers can’t reach it – or it ends up in a spreadsheet over email.
How it works
Create keys, translate into every language, set status (draft → reviewed). One place, one source of truth.
One click creates an immutable release – versioned JSON bundles per language, written to the CDN.
App, shop, TYPO3, CI fetch their language – at runtime from the CDN or via token in the build. Bypassing the server.
The server only sits in the write path. Delivery comes straight from the CDN – hot, cheap, scales.
Integration
Your app loads the finished copy straight from the CDN. No forced SDK, no server in between – flat JSON that any framework understands.
// 1) Fetch the pointer manifest – automatically follows the latest release
const base = "https://cdn.your-domain.tld";
const ptr = await fetch(`${base}/my-project/manifest.json`)
.then(r => r.json());
// 2) Load the language you want – done
const de = await fetch(`${ptr.base}/de.json`).then(r => r.json());
// { "checkout.button.submit": "Submit", ... }What’s inside
Every string in every language – with the source next to it, search and an “untranslated” filter.
See per language how much is translated and reviewed. Optionally publish reviewed only.
Invite colleagues and translators. Owner, admin, member, translator – per organization.
Every version stays available, cacheable forever. Clients follow “latest” or pin a version.
Machine pull for pipelines and CI via bearer tokens. OpenAPI docs included.
Flat JSON as the standard – adapters (e.g. TYPO3 XLIFF) translate into any ecosystem.
Who it’s for
No spreadsheets, no merge conflicts in language files. Pull via token into the pipeline, versioned releases to pin.
Maintain copy in the browser, keep an eye on status, review – without ever touching code.
Multiple projects, multiple clients, separate organizations – one tool for all of them.
FAQ
No. You still load JSON language files – just from one central source instead of scattered files. Existing i18n libraries keep working unchanged.
The focus is delivery: releases are immutable, versioned and served straight from a CDN – fast, cheap and across many systems (app, shop, website).
The default is flat JSON. Adapters for other formats – such as XLIFF for TYPO3, i18next or ARB – plug into the open API or are in progress.
Yes. Every release is immutable and versioned. Clients can follow “latest” or pin a fixed version – ideal for reproducible deploys.
Yes. Invite your team and assign roles (owner, admin, member, translator) per organization. Everyone maintains copy in the browser.
You can get started for free right now and create a project. Create, translate, publish – no credit card.
Create a project, add languages and publish your first release in minutes.
Get started free