How i18n-keyless Works with Agentic Coding and AI Translation

Updated

i18n-keyless is an internationalization service built around one idea: instead of managing translation keys and locale JSON files, you write natural-language text directly in your code and let AI handle the translations. It's designed so that coding agents (and humans) get i18n right the first time, with one file to edit, no locale JSON to load, and no merge conflicts. It's free to self-host, or from €4/month as a hosted service.

The core mechanism: no keys, no locale files

Traditional i18n forces you through a key system. You write something like someheader.welcome.title in your code, then maintain a separate mapping of that key to real text in every language. i18n-keyless removes that layer:

  • You write real words in your code. The text you see in the app is the text in the source.
  • AI handles translation. Translations are left to AI rather than manually managed key files.
  • One file to edit. There's no locale JSON to load and no key registry to keep in sync.

The practical consequence: when you read your codebase, you read natural language, not keys. If a sentence is grammatically wrong, you can see and fix it directly — with a key system, you'd be staring at header.welcome.title and never notice.

Why this matters for agentic coding

Coding agents work best when the task is legible. A key-based i18n system adds a layer of indirection that agents (and humans) routinely get wrong: generating keys, keeping them unique, wiring them into the right locale files, and avoiding merge conflicts when multiple branches touch the same JSON.

i18n-keyless is positioned as "keyless i18n your coding agent gets right the first time." Because there's no key registry and no locale JSON to load, an agent editing your code doesn't have to reason about a parallel translation structure — it edits the text where it lives. The stated goal is that you can add i18n from day one without any impact on your development pace.

What the failure modes look like

The site frames the tradeoff honestly:

Scenario Key-based i18n i18n-keyless
Missing translation Users see someheader.welcome.title Worst case offline: untranslated real words
Reading code You read keys, not sentences Codebase stays natural-language
Adding a key Back-and-forth per key No key system to maintain
Merge conflicts Locale JSON conflicts No locale JSON to merge

The worst case for i18n-keyless is that, offline, a user sees untranslated real words rather than a raw key string — which is a more graceful degradation than a broken key leaking into the UI.

SDKs and frameworks supported

The service exposes one API with twelve SDKs:

  • React — React Native, Expo, Next.js, Remix, TanStack Start, Astro
  • Vue — Nuxt
  • Angular
  • Plain HTML — Svelte, Alpine, htmx, one script tag
  • Node.js
  • Laravel (PHP)
  • Rails (Ruby)
  • Flutter (Dart)
  • Swift — iOS, macOS, Vapor
  • Kotlin — Android, Ktor
  • Python — Django, Flask, FastAPI
  • Go

Setup is advertised as a 5-minute implementation.

The MCP server

i18n-keyless offers an MCP server to cover i18n needs. MCP (Model Context Protocol) is the interface coding agents use to call external tools, so this is the piece that lets an agent interact with your i18n setup directly rather than through manual file edits. If you're running an agentic coding workflow, this is the integration point to check first.

Pricing and the shutdown question

Two things are stated directly on the site:

  • Free self-hosted, or from €4/month for the hosted service.
  • The site addresses "What if the service shuts down?" as a heading — the self-hosted option is the structural answer: if you run it yourself, the service shutting down doesn't take your i18n with it.

If you're evaluating this for a production app, the self-hosted path is the one that removes the vendor-dependency risk. The hosted tier is the convenience option at a low monthly cost.

When this fits and when it doesn't

It fits if: you're building with a coding agent in the loop, you want i18n from day one without a key-management phase, and you value a codebase that reads as natural language. The 5-minute setup and no-merge-conflict property matter most on fast-moving teams.

Think twice if: you need strict, human-reviewed translation control over every string, or you have compliance requirements that mandate a specific translation workflow. i18n-keyless deliberately hands translation to AI — that's the feature, and it's also the constraint.