Hey Product Hunt. I'm Amador, and I built Translaas because changing a button label should not mean another deploy. Most translation tools treat copy like a spreadsheet you export into the repo. Translaas is the other way around: you manage strings in one workspace, add as many languages as you need, then ship them to the app at runtime through official SDKs. Simple strings, plurals, and parameterized copy all live in the same catalog. Translate missing fills the rest of the languages while you keep working. What I care about in this launch: - A console built for shipping apps, not marketing sites - Runtime delivery so a copy fix does not wait on a release - SDKs plus CLI and MCP, so this fits next to the code instead of beside it The gallery video is a first-run: workspace, project, entries, then translate missing. There is a 7-day trial if you want to click through it yourself. I'd love a sharp take: if you ship a multilingual app today, what still forces a redeploy for a string change? The toolchain, the review process, or the way translations are packaged? Happy to answer anything. Thanks for looking.

Translaas

Translation management built for shipping apps

Translation management built for shipping apps