Missing-key runtime
The SDK detects every absent key in production and pushes it to your dashboard in real time. Nothing slips through the cracks anymore.
developer-first i18n
i18n for devs who ship.
No more bloated platforms. Verbumia centralizes your translations, captures missing keys at runtime and plugs natively into your AI via MCP. Flat pricing, open exports, zero lock-in.
Open source · MIT · SDKs, CLI and MCP server
-
checkout.review.shipping_etaes-MX seen 2s ago×1 untranslated -
invoice.tax_label.qstfr-CA seen 8s ago×4 untranslated -
onboarding.step3.ctade-DE seen 21s ago×1 untranslated -
pricing.tier.team.badgept-BR seen 47s ago×12 untranslated
<VerbumiaProvider /> fallback rendered Works with
- react-i18next
- next-intl Coming soon
- vue-i18n Coming soon
- svelte-i18n Coming soon
- node-i18next Coming soon
Integration
Five minutes, one dependency.
Install the SDK, wire the handler, ship. Missing keys flow back to your dashboard in real time — without touching your existing i18n pipeline.
- 1 Install the SDK
- 2 Wire the handler
- 3 Ship
i18n.ts 1// 1. Install2npm i @verbumia/react-i18next 4// 2. Wrap your app with <VerbumiaProvider />5import { VerbumiaProvider } from "@verbumia/react-i18next"; 7export function App() {8 return (9 <VerbumiaProvider10 projectId="proj_xxx"11 apiKey={import.meta.env.VITE_VERBUMIA_KEY}12 >13 <YourApp />14 </VerbumiaProvider>15 );16} 18// 3. Ship — missing keys flow to your dashboard, debouncedmcp.json 1// ~/.config/claude/mcp.json2{3 "mcpServers": {4 "verbumia": {5 "command": "npx",6 "args": ["-y", "@verbumia/mcp"],7 "env": { "VERBUMIA_TOKEN": "vrb_live_…" }8 }9 }10} list_projects get_project_info list_missing_keys propose_translation validate_translations
MCP
MCP-native
Our MCP server is built in parallel with the API. Wire Claude, Cursor or any agent into your project in two lines — you keep your compute, we keep our margins.
MCP-native
Our MCP server is built in parallel with the API. Wire Claude, Cursor or any agent into your project in two lines — you keep your compute, we keep our margins.
Predictable pricing
No per-word billing, no end-of-month surprises. Four tiers, unlimited languages from Hobby up.
Pricing
Honest, predictable, no per-word billing.
Free stays free. Paid plans start at $9/month. Every language, always included.
Free
To explore Verbumia on a side project.
5 GB CDN/mo
$0
Hobby
For a serious project that's growing.
50 GB CDN/mo
$9 / month
Pro
For startups juggling multiple apps.
250 GB CDN/mo
$29 / month
FAQ
What you've been asking.
Is the SDK actually open source?
Yes. The @verbumia/react-i18next SDK, the @verbumia/cli and the MCP server ship under MIT. Fork them, audit them, embed them — your call.
How do I migrate from Lokalise?
Our import reads your Lokalise project directly via their API: keys, translations, languages, namespaces. Count 5 minutes for an average project, zero data loss. Crowdin and Phrase land in V2.
How is pricing calculated — per word or per key?
Per key, and only above a threshold. Languages are unlimited from the Hobby tier ($9/mo) up. No per-word billing, no language surcharge, no end-of-month surprise — it's one of our product commitments.
What does "MCP-native" actually mean?
Our MCP server was designed in parallel with the API, not bolted on. Wire Claude Desktop or Cursor in two lines; the agent can search keys, translate, open the missing-key queue — using your compute, not ours.
What happens if I exceed my plan?
Nothing breaking. Your translation reads keep serving as usual — we don't break your prod. You get a notification, and your writes (new keys, updates) pause until you upgrade or trim your volume. No automatic overage charge.
Am I locked into Verbumia?
No. Export anytime to JSON i18next, Vue, react-intl, XLIFF, PO, Strings, XML or CSV. No proprietary format, no lock-in.
Stop pasting translation keys by hand.
Verbumia catches the missing ones, plugs your AI in, and keeps your exports open. Five minutes to ship.