{"slug": "vibe-coding-did-not-kill-making-money-out-of-engineering-open-source-and-saas", "title": "Vibe coding did not kill making money out of engineering, open source and SaaS", "summary": "I18n-keyless launched a keyless internationalization tool for agentic coding that stores UI copy directly in components instead of locale JSON files, with a free self-hosted option and paid plans starting at €4 per month. The tool ships MIT-licensed SDKs on npm, PyPI, RubyGems and pub.dev, an open-source server runnable via Docker with SQLite or Postgres, and an MCP server, and it claims a 5-minute setup versus at least 1 hour of senior developer time for key-based systems. The company says the approach eliminates shared locale files so multiple coding agents on separate branches cannot produce merge conflicts in en.json.", "body_md": "# The cheapest and most efficient i18n for agentic coding\n\nKeyless i18n your coding agent gets right the first time: one file to edit, no locale JSON to load, no merge conflict\n\nFree self-hosted, or from €4/month.\n\n5-Minute Setup\n\nYour whole i18n implementation in 5 minutes. Not kidding.\n\nNo Keys System\n\nYour brain shouldn't be involved for such meaningless tasks.\n\nGlobal From Day One\n\nShip to international markets without extra effort.\n\n## Setup i18n, keep your codebase clean and ship fast\n\nMultiple PITA exist with the current i18n solutions. Pains are so big that you delay i18n as much as possible.\n\n### It consumes time you should spend on the beach\n\nSetup the keys' system: at least 1 hour of senior dev time\n\nBack and forth for each new key: 1 minute per key, x500 keys, x2 languages = 17 hours\n\nWith i18n-keyless, you don't care about the i18n system at all. You can go on the beach and order a mojito.\n\n### Today most of the systems use keys to translate the text\n\nThis is painful to generate. This is painful to maintain.\n\nWhen you see a text in the app, and you want to update it, you need to find the corresponding key.\n\nWith i18n-keyless, you don't care about the i18n system at all. Use your brain for something more interesting.\n\n### Leave translations to AI\n\nWith the key system, you need to manage the translations in the app.\n\nOtherwise your users will see someheader.welcome.title in their app.\n\nWith i18n-keyless, worst case scenario offline you see untranslated real words. Normal pace, you don't care about the i18n system at all. Just write good headlines, focus on marketing, get sales.\n\n### Codebases are beautiful... until i18n keys' infection\n\nWith the key system, when you read the code and the content, you have to read keys, not natural language.\n\nSometimes you should make a fix because a sentence is not grammatically correct. But you don't know that because you read keys.\n\nWith i18n-keyless, you don't care about the i18n system at all. Codebase stays beautiful.\n\n## What if the service shuts down?\n\nNothing you have goes away.\n\n### SDKs are MIT\n\nEvery SDK stays on npm, PyPI, RubyGems, pub.dev and the other registries. Fork them, keep them, they are yours.\n\n### Server is open source\n\nThe very same Docker image that runs i18n-keyless.com. Run it on your machine with SQLite or Postgres, your AI key, your data at home.\n\n### One project free forever\n\nFully free, unlimited projects. Donations are voluntary and keep the project alive. The licence is verified offline — the server never calls home. Export all translations to JSON at any time.\n\n## MCP server to cover all your i18n needs\n\nPlus six other reasons why the system is so optimized for agentic coding.\n\n### No name to invent\n\nA key is a naming decision with no right answer. Two agents write login.submit and auth.button.send for the same button. Without keys there is no decision to make.\n\n### One file to edit, not twenty\n\nA keyed change touches the component plus every locale JSON, and agents forget files. Here a copy change is a single-file edit.\n\n### Zero merge conflicts in agent fleets\n\nFive agents on five branches all edit en.json: a guaranteed conflict. There is no shared file, so worktrees and background agents never collide.\n\n### Cheap in tokens\n\nTo reuse a key, an agent must load the locale files into context on every edit. Keyless loads nothing: the text is right there in the component.\n\n### Readable diffs\n\nThe pull request shows real sentences. A human or a review agent can judge the copy without digging for what a key stands for.\n\n### One rule in your CLAUDE.md\n\nEvery i18n rule you write is a rule the agent can break. This one needs a single line — and the fallback is the real text, so a miss cannot show a.b.c on screen.\n\n### The only i18n rule your agent needs\n\n```\n# CLAUDE.md\nWrite the UI copy in English and wrap it in … from i18n-keyless-react.\nThat is the whole i18n setup.\n```\n\n### Your agent can operate it, not only write it\n\nThrough the MCP server, the agent lists missing translations, reads one, overrides a bad one, or imports the copy you already have — with its own OAuth login, no key to paste.\n\n[Read the MCP guide](https://docs.i18n-keyless.com/docs/guides/mcp)\n\n## Launch globally from day one\n\nStop delaying i18n because of complexity. Implement in 5 minutes, not days. Maintain your development velocity as if i18n wasn't implemented.\n\n- 5-minute implementation. Not kidding.One simple config object and you're done.\n- Maintain development velocityCode as if i18n wasn't implemented at all.\n- Ship to global marketsNo refactoring needed as you scale to new languages.\n- SSR & SEO readyWorks with Next.js, Remix, TanStack Start and Astro. Server-render any language for search engines — same 5-minute setup.\n\n### Traditional i18n\n\n### i18n-keyless\n\n## It's no brainer to setup\n\nJust the simplest config object and you're ready to go global.\n\nAnd even more, your agent will set it up for you.\n\n### 1. Basic Setup\n\n```\nimport * as I18nKeyless from \"i18n-keyless-react\";\n\nI18nKeyless.init({\n API_KEY: \"YOUR_API_KEY\",\n storage: window.localStorage,\n languages: {\n primary: \"en\",\n supported: [\"en\", \"fr\"],\n },\n});\n```\n\n### 2. Component Usage (React here; the same in Vue, Angular, Flutter, Swift and Kotlin)\n\n``` js\nimport { I18nKeylessText } from \"i18n-keyless-react\";\n// import { T } from \"i18n-keyless-react\"; // also works\n\n// Just write in your primary language\n\n Welcome to our website\n\n```\n\n### 3. Server-side Usage (Node.js here; the same call in Laravel, Rails, Python and Go)\n\n``` js\nimport { awaitForTranslationOrFallbackToOriginal, type Lang } from 'i18n-keyless-node';\n\nconst title = await awaitForTranslationOrFallbackToOriginal('Come see my app!', user.lang as Lang);\nconst body = await awaitForTranslationOrFallbackToOriginal('So many new stuff!', user.lang as Lang);\n\nawait sendExpoPushNotification({ user, title, body });\n```\n\n### 4. For text outside components\n\n``` js\nimport { getTranslation } from \"i18n-keyless-react\";\n\nexport default function Navigation() {\n return (\n \n \n \n );\n}\n```\n\n### 5. Pick your SDK: one install line, the same API everywhere\n\n- React, React Native, Expo, Next.js, Remix, TanStack Start, Astronpm install i18n-keyless-react\n- Vue, Nuxtnpm install i18n-keyless-vue\n- Angularnpm install i18n-keyless-angular\n- Plain HTML, Svelte, Alpine, htmx, one script tagnpm install i18n-keyless-browser\n- Node.jsnpm install i18n-keyless-node\n- Laravel, PHPcomposer require i18n-keyless/laravel\n- Rails, Rubybundle add i18n-keyless-rails\n- Flutter, Dartflutter pub add i18n_keyless\n- Swift, iOS, macOS, VaporSwiftPM: arnaudambro/i18n-keyless-swift\n- Kotlin, Android, Ktorio.github.arnaudambro:i18n-keyless-kotlin\n- Python, Django, Flask, FastAPIpip install i18n-keyless\n- Gogo get github.com/arnaudambro/i18n-keyless/ports/go/v3\n\n### How translations work\n\ni18n-keyless is a library, combined with an API service, that allows you to translate your text without the need to use keys.\n\nIf the translation is not found, there will be an asynchronous fetch to I18nKeyless' API to get the translation by an AI API call.\n\nThis operation is made usually in dev mode, while you're coding. If you missed one, in production only the first user missing the translation will see a glitch, then it'll be available instantly to users all over the globe.\n\n## Your store listing in every language, on every release\n\nEvery update means new release notes, a description and keywords — for each language, on both stores. That is what stops you from adding languages. Not the app.\n\n- Release notes for every language, in one callWrite the update once. awaitForTranslation returns it in each language you sell in, and your store config feeds it to EAS or fastlane.\n- 48 languages, mapped to the App Store slotspt-BR and pt-PT are two listings; en-GB, en-AU and en-CA are three. toAppStoreLocale puts each translation in the right one.\n- Fix a bad translation without a releaseIn the app, one override in the dashboard is live at once — no hotfix build, no store review. In the listing, re-run the push.\n- Not priced per wordA translator charges about €0.10 a word. 2,000 strings times 10 languages is a budget a solo developer does not have. Here words are not counted.\n\n### The whole recipe for an Expo app\n\n```\n// store.config.js — EAS Metadata awaits an async config\nconst { init, awaitForTranslation, toAppStoreLocale } = require(\"i18n-keyless-node\");\n\nconst LANGS = [\"en\", \"fr\", \"de\", \"ja\", \"pt-BR\"];\nconst DESCRIPTION = \"Bibi translates your app while you sleep…\";\n\nmodule.exports = async () => {\n init({ API_KEY: process.env.I18N_KEYLESS_KEY, languages: { primary: \"en\", supported: LANGS } });\n const info = {};\n for (const lang of LANGS) {\n info[toAppStoreLocale(lang)] = {\n title: await awaitForTranslation(\"Bibi\", lang, { context: \"App Store app name, 30 characters max\" }),\n subtitle: await awaitForTranslation(\"Keyless i18n\", lang, { context: \"App Store subtitle, 30 characters max\" }),\n description: await awaitForTranslation(DESCRIPTION, lang, { context: \"App Store description\" }),\n };\n }\n return { configVersion: 0, apple: { info } };\n};\n```\n\nThe same call writes fastlane metadata files for Google Play. Caps are advisory: put the limit in the context and check the length before you push.\n\n## Interactive Sandbox\n\nSee how i18n-keyless works in real-time\n\nOpen a live, editable StackBlitz project to see translations resolve as you type.\n\n## Why I built this\n\n\"I always postponed i18n until my client wanted it so much that I had no choice. I hate reading the code with i18n keys inside, and I hate maintaining JSON files as much as seeing how expensive are i18n translations providers. So I had to build mine, and I FREAKING LOVE IT. All my apps are i18n by default now.\"\n\nArnaud Ambroselli\n\nFounder of i18n-keyless\n\n## Simple, predictable pricing\n\nOne flat price for your scale.\n\nEvery feature in every plan.\n\nNo per-word fees, no token math.\n\n### Own it: fully free, unlimited projects, donate if you want.\n\nThe same API, dashboard and MCP server, in one Docker container with SQLite, on your server, with your own AI key. Fully free, unlimited projects, no subscription, no usage cap, updates for life. If it saves you time, support it with a donation.\n\n[Get started free](https://i18n-keyless.com/self-hosted)\n\nPrefer not to run a server? We run it for you.\n\nUp to 1,000 monthly active users\n\nFor indie apps and new products\n\nUp to 5,000 monthly active users\n\nFor apps finding their audience\n\nUp to 50,000 monthly active users\n\nFor apps with real traction\n\nUp to 500,000 monthly active users\n\nFor products at scale\n\nEvery plan includes:\n\nAll 48 languages. The whole world, from day one\n\nUnlimited translations, AI included. New strings translate themselves in production\n\nLive translation of UGC (user-generated content)\n\nUpgrade, downgrade or cancel anytime\n\nMore than 500,000 monthly active users? [Contact us](mailto:)\n\n### What the same app costs somewhere else\n\nMove the two sliders. The bill is for your app in all 48 languages.\n\n| Solution | Your monthly bill | You pay per | Translation | Languages | \n|---|---|---|---|---|\n| i18n-keylessus | €4/ month | Monthly active users Win win. | AI, unlimited, included | All 48, from day one | \n| Crowdin | €88/ month 1 | Hosted words: your words × 48 | Crowdin AI, inside a quota | You add each one | \n| Intlayer | €27/ month 2 | Seats and projects | AI generation, inside a quota | You add each one | \n| Lingo.dev | €91/ month 3 | A base fee, then AI tokens | The AI bill goes straight to you | You add each one | \n| Locize | €77/ month 4 | Words × 48, and CDN downloads | You bring your own AI key | 10 on the largest published plan | \n| Lokalise | €132/ month 5 | Seats, then keys | Translators billed apart | You add each one | \n| Phrase | €483/ month 6 | Seats, then managed words | From $0.06 a word, billed apart | You add each one | \n| Smartling | €552/ month 7 | Every word, every language | AI translation from $0.06 a word | You add each one | \n| Tolgee | €49/ month 8 | Keys and seats | Machine translation credits | You fill each one | \n| Weglot | €1,678/ month 9 | Words × languages, on a web page | Machine, inside a quota | 20 on the largest published plan | \n\nPublic list prices, read in August 2026. Vendors change them, so please check. Each bill is our reading of the published ladder, and we always take the cheapest paid plan that holds your app. When a vendor bills the first translation once, we spread it over twelve months.\n\n1 Crowdin publishes €44 a month for 60,000 hosted words on the Pro plan, billed annually. A hosted word is one word in one target language. We repeat that block price above 60,000.\n\n2 Intlayer is open source. The $29 a month buys the CMS and the AI generation quota. Above the quota you supply your own AI key, so we add the model bill at $10 for each million tokens, spread over twelve months.\n\n3 Lingo.dev publishes $99 a month plus $2 for each million tokens of infrastructure, and it passes the model bill to you. We count 1.4 tokens for each word and $10 for each million tokens of model cost. The base fee is most of this number.\n\n4 Locize publishes €7, €19 and €49 a month for 15,000, 30,000 and 60,000 words, with 1, 3 and 5 million CDN downloads. Above that it publishes $0.50 for each 1,000 extra words and $5 for each million extra downloads. We count thirty downloads for each user each month. No published plan holds 48 languages.\n\n5 Lokalise publishes $144, $375 and $999 a month, and no key limit. We assume the three plans hold 5,000, 20,000 and 100,000 keys, and twelve words for each key. Human translation is billed apart.\n\n6 Phrase publishes $525 a month for 1 million managed words on the software plan, and $1,245 for 3 million. We count one managed word for each word in each language, and we repeat the $1,245 block above 3 million.\n\n7 Smartling does not publish a platform price. We count only the AI translation, at the published $0.06 a word, spread over twelve months. Your real bill is higher.\n\n8 Tolgee bills keys, not words, so we count twelve words for each key. It publishes €49 for 2,000 keys, €179 for 5,000 and €499 for 20,000, billed annually. Above that we repeat the €499 block. Machine translation credits are counted apart.\n\n9 Weglot translates a web page, not an app. Its largest published plan is €699 a month for 20 languages, so we scale that price to 48 languages. Your words fit inside every one of these plans.\n\nEvery other line grows with your product. Ours is a flat price.\n\n## Frequently asked questions\n\n## Do I need to manage translation files?\n\nNo. There are no JSON files, no key extraction step, and no build-time plugin. You write your sentences in your source language, the SDK sends them to the API on the first request, the API translates them with AI, and every subsequent request is served from the cache. Your code is the single source of truth.\n\n## What happens when I change the source text?\n\nThe source text is the key. Change it and you get a new key with a fresh AI translation. The old key simply stops being requested, and the dashboard cleans it up after 30 days without use. A typo fix is the same: fix it in the code, deploy, and the new text is translated on the first request.\n\n## How much does it cost?\n\nSelf-hosted: fully free, unlimited projects, no subscription and no usage cap — install the Docker image, use your own AI key. Donations are optional and keep the project alive. Hosted: one flat price per project per month, by monthly active users — €4 up to 1,000, €9 up to 5,000, €29 up to 50,000, €99 up to 500,000 — billed monthly, cancel any time. There is no per-seat, per-word, or per-string pricing on either.\n\n## Can I export my translations?\n\nYes. The dashboard has an \"Export JSON\" button that downloads every translation in your project as a single JSON file. The export includes all rows, not just the ones used in the last 30 days, so it is a full backup. There is no lock-in: your data is always one click away.\n\n## One maintainer: what happens if the project stops?\n\nThe SDKs are MIT and stay on npm, PyPI, RubyGems and the other registries. The server is public under the Elastic License 2.0 and the protocol between them is documented, so anyone can run it, fork it, or write a server against it. Your translations leave in one JSON export at any time. If the hosted service stopped: installed apps keep serving their cached translations, a fresh client falls back to the source language, and pointing the SDK at your own instance with API_URL restores everything. What you would lose is the AI translation of new strings on i18n-keyless.com — not your data and not your app.\n\n[Read the full answer, with code](https://docs.i18n-keyless.com/docs/faq#one-maintainer-what-happens-if-the-project-stops)\n\n## Watch the Demo\n\nWatch this short video to see i18n-keyless in action\n\n## Get API Key for One App\n\nYour whole i18n implementation in 5 minutes. iykyk.", "url": "https://wpnews.pro/news/vibe-coding-did-not-kill-making-money-out-of-engineering-open-source-and-saas", "canonical_source": "https://i18n-keyless.com/", "published_at": "2026-09-19 04:05:14+00:00", "updated_at": "2026-09-19 04:24:35.469837+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "agent-protocols", "ai-tools"], "entities": ["i18n-keyless", "npm", "PyPI", "RubyGems", "pub.dev", "Docker", "SQLite", "Postgres"], "alternates": {"html": "https://wpnews.pro/news/vibe-coding-did-not-kill-making-money-out-of-engineering-open-source-and-saas", "markdown": "https://wpnews.pro/news/vibe-coding-did-not-kill-making-money-out-of-engineering-open-source-and-saas.md", "text": "https://wpnews.pro/news/vibe-coding-did-not-kill-making-money-out-of-engineering-open-source-and-saas.txt", "jsonld": "https://wpnews.pro/news/vibe-coding-did-not-kill-making-money-out-of-engineering-open-source-and-saas.jsonld"}}