Use case

Web SaaS across several markets

Your product runs on React, Next.js, Vue or Svelte, and you open markets faster than you open translation tickets.

The problem

Every feature adds strings, and nobody knows which ones are missing until a customer sees them in English.
Terminology drifts from one sprint to the next because nothing holds it between passes.
Shipping a text fix takes a deployment, so a window, so a delay.

What Sonenta changes

One namespace per feature, and keys called without a translation show up in the dashboard during development.
The glossary and project context persist, so the agent translates sprint 12 with sprint 1's terminology.
Nearby markets are handled as regional variants: pt and pt-BR, en and en-GB, as an overlay with BCP-47 fallback.
Approval before publishing is enabled per project as the team grows, and publishing roles are set per project.

Where to start

// src/main.tsx : un namespace par fonctionnalité
import { SonentaProvider } from "@sonenta/react-i18next";

<SonentaProvider
  projectUuid="proj_xxx"
  token={import.meta.env.VITE_SONENTA_TOKEN}
  defaultNS="checkout"
>
  <App />
</SonentaProvider>

Known limits

Rate limits count per organisation, not per API key: issuing a second key does not double your budget, it shares it.
MCP writes start on the Hobby plan. The Free plan gives you MCP in read-only.

Going further

Down to the last word.

Ready to adapt your product to every user?

Start free in minutes. No credit card, no commitment, and your exports always open.