globalize.now is now an official Lovable Select Partner. Lovable approved us into its partner program on 6 October 2026. globalize.now is AI-powered localization infrastructure, and for Lovable builders that comes down to one thing. The app you built in a weekend can ship in 50+ languages without you learning what i18n is.

What does being a Lovable Select Partner mean?

It means Lovable has verified us and accepted us into the tier of its Solution Partner Program that a company has to earn.

Lovable launched its partner program in September 2026 with two tracks. Experts are independent builders. Solution Partners are companies that deliver for clients. According to Lovable, more than 500 solution partners had signed agreements before the program launched.

Solution partners move through four tiers, named Registered, Select, Premier and Elite. Everyone starts at Registered. Select requires verification by Lovable and comes with a listing in the partner directory. Certification is separate, and you complete it through a project built in Lovable.

We have done both. Our Lovable page is built and shipped with Lovable. Our directory profile is submitted and in Lovable's review, and it will appear in the partner directory once they approve it.

Why do Lovable apps get stuck in one language?

Because the text is written straight into the components, and getting it out is the hard part.

Lovable produces a working interface fast. Every button label, heading and error message sits inline in the code. Making that app multilingual is not a translation job at first. It is an engineering job. You pull every string out into keys, create a catalog per language, handle plurals, add a language switcher, and make the layout survive right-to-left scripts.

The obvious shortcut is to ask the AI to translate the app in place. That tends to rewrite components one by one, spend credits on every pass, and leave you with an interface that no longer matches what you built. We covered the mechanics in how to make your Lovable app multilingual without breaking it.

What happened when RajaRide tried it both ways?

The do-it-yourself attempt broke the interface, and the second attempt took a couple of hours.

RajaRide is a boat-sharing marketplace built on Lovable, with about 3,500 monthly users. It ran in 3 languages. The founder first tried to add more languages inside Lovable on her own. That attempt used around 200 credits, broke the UI and had to be reverted.

She then used the lovable-i18n skill with globalize.now. RajaRide went from 3 to 24 languages in a couple of hours. She did the setup herself by following our instructions.

That gap between the two attempts is the reason we built a Lovable integration at all.

How does it work inside Lovable?

You add one skill and one connector, then paste one prompt. You do not leave the Lovable editor.

  1. Connect your Lovable project to GitHub.
  2. Import the lovable-i18n skill in your Lovable workspace settings. You do this once per workspace.
  3. Add globalize.now as an MCP connector.
  4. Paste this into the Lovable chat.
Use the lovable-i18n skill and the globalize MCP to set up i18n and translate my app.

Lovable detects your stack (Vite SPA or TanStack Start), sets up Lingui, moves your interface text into catalogs and adds a language switcher. globalize.now translates the catalogs into the languages you pick.

The conversion happens once. After that, with your repository connected, push jobs translate the new strings you add as you keep building. The full walkthrough is in the Lovable integration guide.

What do you actually get?

Standard locale files in your own repository, in every language you chose.

  • Files you own. One PO catalog per language at src/locales/{locale}/messages.po. They are plain files in your repo. If you stop using us, they stay.
  • 50+ languages. Right-to-left languages such as Arabic and Hebrew are included.
  • Your terms respected. Brand and product names can be marked as never-translate, so "RajaRide" stays "RajaRide" in all 24 languages.
  • No per-language charge. Adding the tenth language costs the same per character as adding the first.

Is globalize.now a translation widget?

No. Nothing is translated in the visitor's browser after the page loads.

A widget swaps text at runtime, which means a flash of the original language and a layout that shifts as the words change length. We work a layer below that. Lingui serves the translations at runtime. globalize.now produces the keys and locale files Lingui reads, and keeps them translated. The translated text is part of your build, like the rest of your app.

For the longer version of why this matters for apps that change every day, read why your Lovable app's translations break every time you ship.

What does it cost to try?

Nothing to start. New accounts get €5 of translation credit, with no card required.

That is enough to convert an app and see it in several languages before you decide anything. Current plans are on the pricing page.

What comes next?

The directory listing, then a public customer story.

Once Lovable approves our profile, globalize.now will be listed in the Lovable partner directory as a localization partner. We are also preparing a partner story with RajaRide for Lovable's partner stories page.

Lovable removed the wait between an idea and a working product. We remove the wait between a working product and a product the rest of the world can read. If you build with other AI tools as well, the same pipeline works outside Lovable, and globalize.now for vibe coders is the place to start.

globalize.now turns hardcoded app copy into translation-ready locale files and keeps them updated as you ship.

Try globalize.now free