Globalize.now icon

Globalize.now

Globalize.now is an AI localization tool that turns hardcoded app text into repo-owned locale files and keeps translations synced on every Git push.

Globalize.now

AI localization for developer workflows

Globalize.now is an AI localization and translation tool for application codebases. It is designed to turn hardcoded UI text into locale files, then keep those translations synchronized as the app changes.

The product positions itself as infrastructure that fits into existing developer workflows rather than a separate translation dashboard. It installs as a skill for AI coding agents, connects through Git and MCP-based workflows, and can open translation pull requests on every push so teams review language updates in the same place they review code.

Core capabilities

Repository scanning and key extraction

The product scans your codebase for hardcoded UI strings, generates translation keys, and scaffolds locale files so your app becomes translation-ready.

Push-based translation sync

It keeps new and changed text translated on every push, opening a translation pull request instead of requiring manual export steps.

Repo-owned locale files

Globalize.now stores translations as locale files in your repo, which lets teams review and edit them through normal Git workflows.

Glossary and translation memory

The pricing page says the system includes a context-aware AI glossary and translation memory, helping keep repeated text consistent and avoiding duplicate translation work.

Stack detection and framework support

The product detects existing next-intl, react-i18next, i18next, and Lingui setups, and it supports Next.js, React, and Vite projects.

Developer workflow integrations

It connects through agent and Git workflows, with support for Cursor, Claude Code, Codex, VS Code, GitHub, GitLab, and Lovable.

Practical workflows

  • Localizing an app from inside an AI coding tool

    A developer working in Cursor, Claude Code, or another supported agent can prompt the skill to scan the repo, extract strings, and generate locale files without leaving the editor.

  • Keeping translations current on every release

    A team shipping frequent changes can rely on push-triggered translation pull requests so new UI text is translated after each commit instead of waiting for a manual localization pass.

  • Working with an existing i18n setup

    A project that already uses next-intl, react-i18next, i18next, or Lingui can keep its existing runtime layer while using globalize.now to manage extraction and sync.

  • Adding repository-based i18n to a Lovable project

    A Lovable app can connect to GitHub, add the lovable-i18n skill and globalize MCP, and use PO catalogs plus a language switcher to make translated output part of the repository.

  • Reviewing translations as part of team code review

    An organisation with multiple contributors can keep translations in pull requests, review them through Git, and use the Team plan’s organisation-oriented features instead of relying on seat-based licensing.

Pros and Cons

Pros

  • Keeps translations in repo-owned locale files rather than a separate hosted translation layer.
  • Automates recurring translation updates on each Git push, reducing manual export and sync work.
  • Supports multiple developer environments and Git providers, including agent-based workflows and GitHub/GitLab sync.
  • Detects existing i18n setups and can work with next-intl, react-i18next, i18next, and Lingui instead of forcing a blank-slate migration.
  • Covers 50+ languages, including RTL languages, from the start.

Cons

  • The source does not show a full list of setup steps for every supported platform, so some integrations are only described at a high level.
  • Pricing and workflow details vary by plan and usage, so teams may need to inspect the usage calculator or app limits before estimating cost.

FAQ

How does setup work?

Globalize.now scans your repository for hardcoded UI text, generates translation keys and locale files, and keeps those translations synced on every Git push. The source text says you can stay in Cursor, Claude Code, or another AI coding environment while the agent handles the i18n workflow.

Are the translations stored in my repository?

According to the pricing page, translations live as locale files in your repo, so you keep them if you stop paying. The product also says locale files are owned by you and are not held hostage in a separate database.

What pricing options are available?

The pricing page describes Starter for one developer at €20/month and Team for organisations at €249/month. It also states there are no per-seat charges and no per-language charges.

What platforms and integrations are supported?

Globalize.now supports 50+ languages, including RTL languages such as Arabic, Hebrew, and Persian. The pricing page also lists Next.js, React, Vite, CLI, API, Git sync, GitHub, GitLab, Cursor, Claude Code, Codex, VS Code, and Lovable as supported surfaces.

Do I still need a runtime i18n library?

The source explains that Globalize.now is infrastructure that works alongside your runtime i18n library, such as next-intl, react-i18next, i18next, or react-intl. It scans the repo, emits locale bundles, and continues extracting and syncing as the code changes.

Quick Facts

Category
Developer Tool
Product type
AI localization and translation
Primary users
Developers and teams shipping web apps
Supported app stacks
Next.js, React, Vite
Supported workflow
Git-based sync with translation PRs
Source domain
globalize.now