Translation Management System
Translations as infrastructure: teams edit copy in one hub, and apps download a cached JSON bundle per language, with no redeploys.
In plain words
Apps that speak many languages often hide their text inside code, so fixing a typo means a new release. This hub keeps all the text in one place that non-engineers can edit, and apps simply download the latest version for each language.
Interactive preview
How Translation Management System works
Interactive · illustrative sample data
The challenge
Translations in code or spreadsheets mean store releases for typo fixes, bloated bundles, and no audit of customer-facing copy changes.
Our approach
Centralise phrases by key, language and tags, then serve compiled per-language bundles through a cached, ETag-aware export API.
Step by step
From first click to finished job
- 1
Editors update copy
In the Vue 3 admin, no engineer needed.
- 2
Bundles are compiled and cached
Per language in Redis.
- 3
Apps fetch the latest
Via the export API with ETags.
Capabilities
What it does
Phrase management
Keys, languages, tags and namespaces with search and bulk edit.
Export API
One JSON bundle per language, filterable by tags.
Built for scale
Validated with 100k+ rows; indexed queries and Redis-cached bundles.
HTTP caching
Cache-Control and ETags, so clients get 304 Not Modified when nothing changed.
Engineering
Key decisions
Cache-friendly by design
Copy changes ship hourly while app releases stay monthly.
Architecture
Tech stack
API
- Laravel
- PostgreSQL
- Redis
- OpenAPI
Admin & delivery
- Vue 3
- TypeScript
- Docker
Outcome
What it delivers
- Copy fixes without app releases
- Fast, cacheable bundles even at 100k+ phrases
Deep dives
Read the engineering notes
Translation API at Scale — 100k+ Keys Without Redeploys
Designing a translation hub with Laravel, PostgreSQL, Redis, and a public JSON export API so mobile and web apps fetch language bundles without shipping new builds.
Services behind it