Shipping a data-heavy tool across 5 locales, English, Dutch, German, French, Spanish, over 168 countries makes a translation platform feel inevitable. But a SaaS translation tool adds a dependency, a monthly bill, and a bottleneck: every content change means exporting strings, waiting on translators, importing segments, and validating five rollbacks.
Invert the model instead. Treat translation as deployment config, not a separate pipeline.
Glossary as config, executor plus gate
Store terminology and translation rules as a JSON glossary in version control. That glossary is the single source of truth for how a concept maps across locales.
Two agents do the work:
