Open-Source CMS · aymericzip

intlayer

Intlayer is a TypeScript-based i18n library that manages translations at the component level with built-in AI assistance and a visual CMS editor. It supports Next.js, React, Vite, and other frameworks with per-locale content files and type-safe dictionary generation.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/aymericzip/intlayer

784

GitHub stars

120

Forks

TypeScript

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	aymericzip/intlayer
Owner	aymericzip
Primary language	TypeScript
License	Apache-2.0 — OSI-approved
Stars	784
Forks	120
Open issues	13
Latest release	v9.0.0-canary.11 (2026-07-01)
Last updated	2026-07-08
Source	https://github.com/aymericzip/intlayer

What intlayer is

Intlayer provides a compiler-based approach to i18n, extracting content declarations from components and generating type-safe dictionary files. It integrates with multiple frameworks via plugins and offers per-locale content files with TypeScript autocompletion and tree-shakable output.

Quickstart

Get the intlayer source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/aymericzip/intlayer.git2cd intlayer3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-framework Multilingual Applications

Deploy type-safe internationalization across React, Next.js, Vite, Vue, or Nuxt codebases where teams need consistent content management and IDE autocompletion without duplicating translation logic.

Team-based Content Authoring Workflows

Organizations requiring non-developer input into content and translations can leverage the included visual CMS editor, reducing bottlenecks between engineering and content/marketing teams.

CI/CD-integrated Translation Pipelines

Applications that need automated translation workflows, version control integration for i18n artifacts, and reproducible per-locale builds benefit from Intlayer's compiler and per-locale file structure.

Implementation considerations

Requires TypeScript and a build pipeline; Node.js environment mandatory. Verify framework-specific plugin stability (Next.js, React, Vite, Vue, Nuxt supported; others may need custom integration).
Content is declared in JavaScript files and compiled at build time. Plan for developer workflow changes: developers write content in component files, which are then extracted into locale-specific dictionaries.
AI-powered translation feature exists but scope, API requirements, and pricing/quota model are not detailed in provided data. Requires hands-on evaluation before relying on this for production workflows.
Per-component approach with tree-shakable output is suited for single-page apps and component libraries but may need adjustment for server-side rendering or static generation workflows.
CMS editor is described as 'free' and 'included' but hosting, scalability, and whether it is cloud-hosted or self-hosted are not specified. Clarify infrastructure expectations.

When to avoid it — and what to weigh

Simple Static Site or Low Volume Locales — Projects with only 1–2 languages or minimal translation requirements may find Intlayer's setup and CMS overhead excessive compared to simpler JSON/YAML libraries.
Heavy Real-time Translation Requirements — If your application demands live language switching or real-time translation API consumption at scale, Intlayer's per-component model and build-time approach may not align with that use case.
Strict Framework Constraints — Legacy or niche frameworks (Angular, Ember, older custom systems) without explicit Intlayer integration may require significant custom work to adopt. Check framework compatibility before committing.
Minimal or No Build Step — Intlayer requires a compiler step and build-time content extraction. Purely runtime-only or zero-build environments cannot use this tool effectively.

License & commercial use

Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved open-source license that permits commercial use, modification, and distribution under stated conditions.

Apache-2.0 explicitly permits commercial use. However, this covers only the library itself. The AI translation service and CMS editor may have separate terms of service or pricing; consult official documentation or contact maintainers to clarify any hosted service restrictions.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

Security review required. AI translation and CMS editor involve external data handling; verify encryption, authentication (token/key management), data residency, and access control. The compiler and per-component content system are build-time; no runtime injection attacks are apparent, but source code review is recommended before adopting in security-sensitive contexts. No security audit or responsible disclosure policy mentioned in provided data.

Alternatives to consider

i18next

Mature, framework-agnostic i18n library with plugin ecosystem, large community, and extensive docs. Lacks built-in visual CMS editor and requires manual JSON/YAML management; more traditional but lower overhead.

react-intl

React-specific i18n library with strong TypeScript support and format.js tooling for message extraction. Narrower scope than Intlayer (React-only) but more battle-tested in production React applications.

next-intl

Next.js-focused i18n solution with server/client component support and route-based localization. Tighter Next.js integration but not cross-framework; lighter weight than Intlayer if locked into Next.js.

Software development agency

Build on intlayer with DEV.co software developers

Start with the framework-specific setup guide on intlayer.org, test the visual editor, and clarify AI translation pricing and CMS hosting before committing to production.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

deco velite Instatic

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source CMS Web App Development AI Development API Development Talk to DEV.co

intlayer FAQ

Does Intlayer work with my framework?

Officially supported: Next.js, React, Vite, Vue.js, Nuxt, Preact, Express, React Native. Check intlayer.org docs for your specific framework. Unsupported frameworks may require custom plugin work.

Is the visual editor truly free and self-hostable?

README states 'free CMS & visual editor' but hosting model (cloud vs. self-hosted), infrastructure costs, and SLA details are not provided in available data. Contact maintainers or review official pricing page for clarity.

Can I use Intlayer in production today?

Latest release is a canary build (v9.0.0-canary.11), suggesting active development. Stable releases exist but verify stability for your use case. Review changelog and consider pinning minor versions to avoid breaking changes.

How does the AI translation feature work and what are the costs?

README mentions 'AI-powered translation' but no details on API provider, token limits, pricing, or setup are provided. This requires hands-on evaluation; do not assume it is free or unlimited.

Work with a software development agency

Adopting intlayer is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source cms software in production.

Ready to Evaluate Intlayer for Your Multilingual App?

Start with the framework-specific setup guide on intlayer.org, test the visual editor, and clarify AI translation pricing and CMS hosting before committing to production.

Talk to DEV.co Schedule a Consultation