> For the complete documentation index, see [llms.txt](https://www.i18next.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.i18next.com/overview/for-enterprises.md).

# For Enterprises

## Is i18n enough?

We believe not. The closer the release date of your product gets the more obvious it gets, that instrumenting your code for localization is not enough.

There are more points to address:

* How does the translation process work?
* How do the source files get to the translators and back?
* How do you keep track which parts are already translated and which parts are not - and additional are all target languages fully translated?
* How do you deploy new languages after release?
* How do you handle versioning?
* How do you update / fix typos in translations after deployment?

Translation Management Systems (TMSes) address exactly this set of problems. The todays landscape has many options — most are now built for continuous localization rather than one-time document translation, and the differences are in how each one integrates with the developer runtime, plural format handling, CDN delivery, branches and versions, AI translation, MCP integration, and so on.

> For a detailed comparison of TMS options against i18next-specific criteria — including `saveMissing` integration, `i18next-cli` support, native plural handling, in-context editors, CDN delivery, and the new generation of MCP servers — see [Translation Management Systems](/overview/translation-management-systems.md).

## Locize

![](/files/-L9iS9uLqGNjseomOY6O)

[Locize](https://www.locize.com/i18next?utm_source=i18next_com\&utm_medium=gitbook\&utm_campaign=overview_for_enterprises) is the localization-as-a-service platform built by the i18next team. The close integration with i18next removes the glue code that other TMSes require and funds the continued development of the library itself.

{% embed url="<https://www.youtube.com/watch?v=lCuHSZvSiVg>" %}

Locize brings you:

* A beautiful editor to edit your translations
* Continuous localization workflow — translation updates ship via CDN without redeploying code
* An in-context editor to edit translations directly in your live application
* Progress and usage reporting; runtime per-key "last used" tracking via the `locize-lastused` plugin
* Native i18next plural format support (v3 and v4) plus per-locale CLDR plural expansion across all target languages
* Branches, versions, and multi-tenant (per-customer overrides) in one platform
* Missing keys flow into Locize automatically — full `saveMissing` closed-loop via `i18next-locize-backend`
* AI translation with bring-your-own-key (OpenAI, Gemini, Mistral, Lara, DeepL) and a 22-tool MCP server in the [official Model Context Protocol Registry](https://registry.modelcontextprotocol.io/v0/servers?search=locize) for editor-native workflows from Claude Code, Cursor, or VS Code Copilot
* CDN-hosted translations on Standard, Pro, and private tiers — or self-host if you prefer

While Locize provides the security and scale required by global enterprises, we believe professional localization should be accessible to everyone. That’s why we’ve introduced a **Free plan** alongside our new fixed and usage-based plans — [see pricing](https://www.locize.com/pricing?utm_source=i18next_com\&utm_medium=gitbook\&utm_campaign=overview_for_enterprises) — allowing you to start small and scale predictably as you grow.

Check out how it works => <https://www.youtube.com/watch?v=lCuHSZvSiVg>

*Together, 'i18next' and '*[*Locize*](https://www.locize.com/i18next?utm_source=i18next_com\&utm_medium=gitbook\&utm_campaign=overview_for_enterprises)*' empower your business to effortlessly reach international audiences. They help you speak the language of your customers, making your business more accessible, relatable, and successful in global markets.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.i18next.com/overview/for-enterprises.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.