Blog

  1. Over-the-air translation updates without a redeploy

    A release freezes approved translations into a versioned bundle behind an access key. The Go, Rust and NestJS clients load it on start and refresh it in the background, so a corrected string reaches a running service without a deploy.

  2. Localization in CI/CD: fail the build on missing translations

    Push source strings on every merge, pull translations on a schedule or before a release, and stop the pipeline when a language falls below a threshold. A working setup with the Ownlate GitHub Action and the Docker image.

  3. An MCP server for translations: managing strings with Claude Code

    Connect Claude Code, Cursor or any MCP client to Ownlate's hosted MCP server, then add a string, translate it, check it and publish a release without leaving your editor, with approval left to a person.

  4. Git localization workflow: keep translation files in your repo

    Translation files belong next to the code that reads them. This guide walks through a Git localization workflow with Ownlate: map files in ownlate.yml, push new keys, translate and review, and get the result back as a pull request.