opral/inlang

Health v2 · maintenance only

Flags: no_releases no_license

Adoption not part of the score

1987 stars · 178 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

inlang is an open-format translation management system (TMS) that stores localization data in a vendor-neutral .inlang project file or directory inside your repository. It ships an SDK (@inlang/sdk), plugins for formats like JSON, ICU, i18next, and XLIFF, editor tools, and CI integrations so developers, translators, and AI agents share one localization source of truth.

Use cases

• manage app translations in git as code
• avoid vendor lock-in from traditional TMS platforms
• run CI checks for missing translations and placeholder issues
• let translators edit strings via a friendly editor while devs use the SDK
• import and export i18next, ICU MessageFormat, JSON, and XLIFF files
• give AI agents programmatic access to localization data

When to choose

• your team wants translations versioned in the repo alongside code
• you need an open, vendor-neutral localization format with SDK and plugin access
• you want CI automation and editor tooling around i18n files
• engineering, translators, and automation must edit the same source of truth

When to avoid

• you need a fully managed enterprise TMS with vendor management, translation memory, and procurement features
• you only need a simple i18n runtime library without translation management
• you require a no-code hosted localization dashboard as the primary workflow

Facets

framework · maturity active

internationalization sdk plugin-system developer-tools web-development developer-tools cross-platform editor-plugin cli tms translation-management i18n open-format lix vscode-extension ci-checks localization automation nodejs

Member repositories

For agents

markdown · JSON · MCP: product_card(name="opral/inlang")