Skip to content
NewThe Linguana CLI and app templates

Your product. More languages.

Linguana is app localization software for developers and product teams. It finds static text at build time, translates it, and lets your team review and publish each language.

Create a project
Northwind appdevelopment

Good to see you, Maya

Northwind · Tracking Northwind app

  1. Build8 messages discovered
  2. 2Translate4 missing or rejected
  3. 3Review4 items need a decision
  4. Publishv12 is live

Language coverage

Latest build · development. Ready translations still require publishing.

LanguageReadyNeeds reviewMissingRejected
French fr7100
Spanish es7100
Japanese ja7100
Arabic ar3131
Projects
1
4 languages in Northwind app
Translation jobs
4
4 completed
Review queue
4
Decisions are waiting
Translation usage value
$31.40
Before included plan allowances

Recent translation work

Jobs for Northwind app

  • fr8 of 8 messages · Sep 27 Succeeded
  • es8 of 8 messages · Sep 27 Succeeded
  • ja8 of 8 messages · Sep 27 Succeeded

Usage this month

31% of the monthly capof $100
112 memory matchesUsage details

A working preview with sample data. Click through it: approve, run a translation, publish, or restore. These controls change sample data only.

Languages

Choose the languages your users speak.

100+languages supported.

See all supported languages
Languages include English, French, Spanish, Japanese, Standard Arabic, Portuguese, German, Romanian, Swedish, Danish, Bulgarian, Russian, and more.

How it works

One sentence. Every step stays visible.

Follow a string from your source build to a reviewed translation. Publish only when the language is ready.

Build

The compiler finds supported static text during your build.

The Vite and Next.js adapters extract supported static UI text. Variables, plurals, and rich text use explicit message APIs. The build uploads the extracted text for translation.

How text is found
Build #48Sample
React source filesrc/greeting.tsxUnchanged
1export function Greeting({ name }) {2  return (3    <header>4      <h1>Good morning, {name}.</h1>5      <p>Three invoices are due this week.</p>6      <button>Send reminder</button>7    </header>8  );9}

Found 3 strings · build uploaded

  • Good morning, {name}.greeting.tsx:4
  • Three invoices are due this week.greeting.tsx:5
  • Send remindergreeting.tsx:6

Translate

Choose a target language and check the translation estimate.

The estimate separates new translation work from compatible memory reuse. Review it in Jobs before starting; translation usage counts accepted target-language output.

Usage and costs
Translate latest buildSample
frFrenchesSpanishjaJapanesearArabic
New characters
2,840
Reused from memory
9,612
Estimated cost
$0.02
Monthly limit$12.40 of $50.00

This run fits. The final charge can't exceed the estimate you approve.

CancelStart translation

Review

See what is live, missing or waiting on a person, in every language.

Compare the original and the translation, then approve it, reject it or keep the source wording. Owners, admins, and editors can review in the dashboard without opening the code.

Review translations
StringsSample
Stringfresjaar
Good morning, {name}.LiveLiveNeeds reviewLive
Three invoices are due this week.Needs reviewLiveLiveMissing
Send reminderLiveLiveLiveMissing
LiveNeeds reviewMissing

Source · en

Three invoices are due this week.

French · needs review

Trois factures arrivent à échéance cette semaine.

Use sourceRejectApprove

Publish

Publish the reviewed catalog for the intended environment.

In Releases, choose Publish ready catalog and confirm the production target. New catalog requests use that release; an app with a cached catalog may need to reload.

Publish a language
Releases · productionSample

4 languages reviewed and ready

Publish ready catalog
  1. v12fr, es, ja, arPublished by Maya · 2 min agoLive
  2. v11fr, es, jaSep 28Restore
  3. v10fr, esSep 21Restore

Restoring changes what your app loads. Newer versions are kept.

One workspace

One build. Everyone who touches the words.

Engineers set it up once. The people who own the wording review it in the dashboard, without opening the code.
  • Developers

    Add the build plugin once. Text is found where it already lives.

  • Product teams

    Choose languages and set a monthly limit before anything runs.

  • Reviewers

    Compare source and translation, then approve, reject, or keep the original.

  • AI agents

    One prompt sets up Claude Code, Cursor, Codex, or Copilot.

Why teams switch

Your code, budget, and release stay yours.

Upload extracted text from your build, review translations in the dashboard, then publish a versioned catalog.

Create a project
  1. No keys to maintain

    No components to rewrite.

    01

    The build plugin finds supported text where it already lives. Dynamic text has explicit APIs and clear diagnostics.

    greeting.tsxunchanged
    export function Greeting() {
      return <h1>Good morning</h1>;
    }
    1 string foundno keys added
  2. Control additional usage

    Set a limit for each resource.

    02

    Usage & billing tracks translated characters, hosted build minutes, and preview hours separately. On a paid subscription, owners and admins can allow additional usage within spending limits.

    Translation runEstimate
    New characters
    182,400
    Reused from memory
    41,920
    This run
    $1.46
    Monthly limit$24.56 of $40
  3. Keep earlier releases available

    Restore a catalog from release history.

    03

    Choose Restore beside an earlier version and confirm. The release pointer changes without deleting newer catalogs. Restoring a catalog does not refund translation work.

    Releases · Productionfr · es · ja
    1. v12Published by MayaLive
    2. v11Published by JonRestore
    3. v10Published by MayaRestore

By the numbers

More gets shipped when the words keep up.

Languages, frameworks, and a published rate you can check before the first run.

Locales

In the registry, each labeled by support level.

121

Frameworks

React, Next.js, Vue, Svelte, Solid, and TanStack Start.

6

Translation keys

For supported static text. Dynamic messages use explicit APIs.

0

Per million

Newly translated, accepted target characters after your plan allowance.

$8

Linguana CLI

Start a new app, already translated.

One command scaffolds a blog, SaaS page, or storefront in your framework, with four languages built in. Connect it to your project when you are ready.
npx @linguanahq/cli create app
~
$ npx @linguanahq/cli create app my-blogChoose a templateElsewhere — BlogChoose a frameworkSolidJSPackage managernpmConnect Linguana or try a demo?Try the demoCreate your appInstall dependenciesYour app is ready.   cd my-blog   npm run dev

Get started

Start the way you prefer.

Follow the guide for your framework, or hand one prompt to your coding agent. Either way, your components stay as written.

React

React on Vite · runs inside your Vite build

React guide
  1. Install the runtime

    The framework bindings and the catalog loader.

  2. Add the build plugin

    Finds your text at build time. No keys, no wrappers.

    bun add --dev @linguanahq/vite
  3. Register the adapter

    Place Linguana before your framework's own plugin.

    vite.config.ts
    import { defineConfig } from "vite";
    import { linguana } from "@linguanahq/vite";
    import { react as linguanaReact } from "@linguanahq/vite/react";
    import react from "@vitejs/plugin-react";
    
    export default defineConfig({
      plugins: [
        linguana({
          adapter: linguanaReact(),
          projectId: "your-project-id",
          environment: "development",
          sourceLocale: "en",
        }),
        react(),
      ],
    });

Pricing

Simple pricing, built to scale.

Simple plans, clear limits. Start small and give your team more room to build as you grow.

For trying Linguana

$0forever

Free

For side projects and trying Linguana on a real app.

Translated characters / month
50K
Builds
Local builds only

Newly translated, accepted target-language output. Exact memory reuse doesn’t count.

  • Local builds
  • Review and publish in the dashboard
  • Exact translation-memory reuse

For shipping products

$19/ organization / month

Pro

Translate your product with predictable monthly allowances.

Translated characters / month
2M
Hosted build minutes / month
30

Newly translated, accepted target-language output. Exact memory reuse doesn’t count.

Then $8 per million translated characters.

  • Everything in Free
  • Team review
  • Versioned releases and rollback
  • Organization spending limits
Recommended

For growing teams

$49/ organization / month

Team

A larger translation allowance for teams shipping more languages.

Translated characters / month
5M
Hosted build minutes / month
300

Newly translated, accepted target-language output. Exact memory reuse doesn’t count.

Then $8 per million translated characters.

  • Everything in Pro
  • 5,000,000 translated characters each month
  • More hosted build time
  • Organization roles and review

Talk to us

CustomLet’s talk

Enterprise

Discuss custom usage and terms for your organization.

Translated characters / month
Custom allowance
Hosted build minutes / month
Custom allowance

Allowances tailored to your team.

  • Custom usage and contract terms
  • Organization roles and audit history
  • Discuss your support requirements

Estimate your usage

What will you ship each month?

Estimate newly translated target characters across every language and time spent on hosted builds. Exact translation-memory reuse does not use your character allowance.

Pro includes 30 minutes; Team includes 300. Local builds use no hosted minutes. New translations generated in local previews still use your character allowance.

Or start from a translation volume

Translation estimatePro

$27.00/ month

Pro plan
$19.00
Included characters
2,000,000
Additional characters (1M × $8/M)
$8.00
Included build minutes
30
Additional builds (0 min × $0.05/min)
$0.00

Usage authorization limits apply before included allowances; they are not invoice caps.

Questions

Before you connect a project.

Clear answers on source code, releases, supported frameworks, the CLI, and cost.
Who is Linguana for?

Linguana is for developers, product teams, and translators who want to localize web applications without rewriting source text into translation keys.

Do I need a credit card to start?

Start on Free — no credit card required. Create an account, then create your workspace and project. Free signup needs no payment details or sales approval.

Do I need a card or sales approval for Pro or Team?

Pro and Team are optional paid upgrades with self-serve checkout. A payment method is required at checkout; sales approval is not required. Enterprise plans are arranged through sales.

Is email verification required?

Email/password signup currently does not require a separate email-verification step. Google signup follows Google’s authentication flow.

How do I sign up and create my first project?

Open the self-serve signup page, create an account, complete workspace setup, and create a project. Run npx @linguanahq/cli@latest login and npx @linguanahq/cli@latest link in your app’s folder, or follow the SDK installation guide. No sales conversation is needed to start on Free.

Which frameworks are supported?

The public SDK supports React, Next.js, Vue, Svelte, Solid, and TanStack Start. Demo templates can run locally without an account; connecting an app to hosted translation requires an account and a project.

Will I need to rewrite my source files?

Linguana extracts supported static text at build time. Your components stay as written. Dynamic content uses explicit APIs, and unsupported patterns receive diagnostics. See dynamic text and links.

Which frameworks can I use?

The public SDK supports React, Next.js, Vue, Svelte, Solid, and TanStack Start. The framework guide shows the setup for each one.

Does Linguana work with Next.js?

Yes. @linguanahq/next supports the Next.js 16 App Router with React 19, in Server and Client Components, on Turbopack or webpack. Wrap next.config with withLinguana and add one root provider. Pages Router and localized URL routing are not included yet. Read the Next.js guide.

What does the Linguana CLI do?

npx @linguanahq/cli create app scaffolds a complete blog, SaaS page, or storefront in React, Vue, Svelte, SolidJS, or TanStack Start. Demo mode runs with bundled translations and no account. When you are ready, login and link connect the app to your project, and doctor checks the setup. See the CLI guide or browse the templates.

When do translations reach my users?

Only after someone publishes a reviewed catalog. Releases are versioned, and you can restore an earlier version. Read the publishing guide.

How does hosted translation pricing work?

Free, Pro, and Team include monthly allowances of newly translated, accepted target-language output. Exact translation-memory reuse does not consume that allowance. Local builds use no hosted build minutes, but new translations generated during local preview still consume translated characters. Hosted builds and running previews use separate workspace allowances. The dashboard shows the maximum usage before a build starts. Translation usage limits apply before plan allowances and are not invoice caps. Compare current plans and translation estimates.

Updated

Every language, one build

Your app, finally speaking every language.

Bring your source code or hand a prompt to your AI coding agent. Your team decides what reaches users.
Create a project
Read the docs