What did Hlido score Intlayer?

Intlayer scored 73/100 (STEADY) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

Intlayer

Name: Intlayer review
Item: Intlayer
Rating: 73
Author: Hlido Editor

Coding · tested 2026-08-22 · re-test due 2026-11-22 · by the Hlido desk, not the vendor

In short: A thoughtfully designed, open-source per-component i18n framework — type-safe, AI-assisted translation, and a visual CMS — that quietly fixes how React/Next/Vue/Svelte apps handle localization.

5 PASS · 0 FAIL of 5 public-surface claims

Visit Intlayer → scorecard.json

Quick answer

Intlayer scores 73/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-22). STEADY (73) for a coherent, well-crafted, openly published framework with a differentiated per-component model, type safety, multi-framework support, a working playground and clear signs of active maintenance.

Hlido Editor · 2026-08-22

Intlayer is a developer-tooling project that rethinks internationalization around the component rather than the giant central JSON file. You declare translations next to the component that uses them, get full type safety, can auto-translate with AI, and invite non-developers to edit through a visual CMS. That per-component model is a genuinely opinionated take in a space long dominated by react-i18next / next-intl / FormatJS, and the surface backs it up: a clean quickstart (npx intlayer init), support advertised across React, Next.js, Vue and Svelte, 20+ locales, a live playground/sandbox, and an actively shipped codebase (v9.3.3, ~800 GitHub stars). It reads as a well-maintained, single-author-led OSS project with real craft. The honest caveats are the ones that apply to most young frameworks: the ecosystem and adoption are still modest next to the incumbents, the 'translate with AI' quality and the bundle-size claims are asserted rather than demonstrated on the surface, and betting an app's localization layer on a fast-moving pre-1.0-feeling framework carries lock-in risk. For teams that feel the pain of central-file i18n, it's a credible, low-cost thing to trial.

Why STEADY

STEADY (73) for a coherent, well-crafted, openly published framework with a differentiated per-component model, type safety, multi-framework support, a working playground and clear signs of active maintenance. Not higher because adoption and ecosystem are modest against entrenched incumbents (react-i18next, next-intl) and the differentiating claims (AI-translation quality, bundle impact) are unverified from the surface. Not FADING: the project is current, actively shipping, and technically credible.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — Per-Component i18n — Type-Safe, Translate with AI, Edit Visually
PASS Cta present (required) — Get started / npx intlayer init
PASS Pricing or access — Open source; free to install
PASS Evidence or demo — Live playground/sandbox + code examples; 4 screenshots captured

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-9ef4c034f3c7f138-intlayer-org). Our own captures — not vendor marketing material.

Intlayer — run screenshot 1 (home.png) — home.png

Intlayer — run screenshot 2 (page_.png) — page_.png

Intlayer — run screenshot 3 (page_.png) — page_.png

Intlayer — run screenshot 4 (page_playground.png) — page_playground.png

What it does well

Per-component i18n model — translations live next to the component, not in one sprawling central file
Full type safety over content keys, a real advantage for large TypeScript codebases
Multi-framework support advertised: React, Next.js, Vue and Svelte
Frictionless entry (npx intlayer init) plus a live playground and visual CMS for non-dev editors
Open source with visible, active maintenance (v9.3.3, ~800 stars) and 20+ supported locales

What it fails at

Adoption and ecosystem are modest next to react-i18next / next-intl incumbents
'Translate with AI' quality is asserted, not demonstrated — no visible evaluation of translation fidelity
Bundle-size / performance claims are stated on the surface without benchmarks to back them
Adopting a young framework for the localization layer carries migration and lock-in risk if it stalls

Best for

React/Next.js/Vue/Svelte teams frustrated by monolithic central i18n files
TypeScript-heavy codebases that want type-safe content keys
Projects that need non-developers to edit copy through a CMS
Developers who want to trial AI-assisted translation with a low-friction setup

Not recommended for

Teams that need the largest ecosystem, plugin surface and community answers (incumbents win here)
Risk-averse projects unwilling to depend on a young, fast-moving framework for a core layer
Use cases needing audited, human-reviewed translation quality guarantees out of the box

Pricing & access

Pricing findable on the public surfacePASS Open source; free to install (tested 2026-08-22)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-22.

Compared to

React I18next ecosystem-maturity-vs-ergonomics
react-i18next is the battle-tested default with the largest ecosystem; Intlayer trades that maturity for a cleaner per-component model, type safety and built-in AI translation + CMS. Choose react-i18next for ecosystem safety, Intlayer for developer ergonomics.
Next Intl next-only-vs-multi-framework
next-intl is tightly focused on Next.js with strong App Router support; Intlayer is broader (React/Vue/Svelte too) and adds the visual CMS and AI translation. Choose next-intl for a Next-only stack, Intlayer for multi-framework or CMS-driven content.

Agent relevance

CLI SDK Behavioral-testable

Agentic-Commerce Readiness 59/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Intlayer is a developer library/CLI, not an autonomous agent. It is highly automatable — a coding agent can scaffold and run it via npx intlayer init, edit .content.ts files, and drive the AI-translation step programmatically. The open-source repo makes it behaviorally testable. No MCP server or hosted API is exposed.

Agent-friendly score: 7/10

Evidence

Per-component i18n model — source (2026-08-22) verified
Type-safe content with AI translation and visual editor — source (2026-08-22) verified
Multi-framework support (React/Next/Vue/Svelte) — source (2026-08-22) verified
npx intlayer init quickstart — source (2026-08-22) verified
Open source, actively shipped (v9.3.3) — source (2026-08-22) verified

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-22

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/aymericzip-intlayer.svg)](https://hlido.eu/check/?agent=aymericzip-intlayer)

HTML

<a href="https://hlido.eu/check/?agent=aymericzip-intlayer"><img src="https://hlido.eu/badge/aymericzip-intlayer.svg" alt="Hlido trust score"></a>