Writing and content decision
Tolgee Cloud
A focused localization core (capture keys, auto-translate, edit, export) is realistic for a single developer in ~30 hours; the full Tolgee Cloud feature set (in-context editing, AI customization, content delivery, enterprise compliance and support) is larger and better left to the hosted product.
Visit website↗No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
Code Tolgee Cloud publishes itself
Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Collect strings from an app, auto-translate them via an MT provider, store/manage translations, and export translations for the app to consume.
What it still won’t have
- In-context editing (modify texts directly in your running app)
- AI translator & Brand context features
- Content Delivery (automated deploys to cloud storage/CDN)
- Enterprise features (SSO, dedicated support, ISO 27001 compliance)
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted lightweight localization service using Node.js (Express), PostgreSQL, and a React admin UI. Implement: 1) a JS SDK endpoint to POST new keys and metadata; 2) a worker that calls an external MT API (configurable DeepL/Google) to auto-translate new keys and stores translations in Postgres; 3) a React UI to list keys, edit translations, add languages, and trigger exports; 4) endpoints/CLI to export translation bundles (JSON and .po) to S3-compatible storage. Out of scope: in-context editing overlay in running apps, SSO, enterprise compliance, and paid support. Include error handling for API failures, retries for MT calls, input validation, unit tests for core modules, and basic Docker-based deployment manifests.
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score62
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productTolgee homepage
- official pricingTolgee pricing
- official docsLocalization process
Integrity checks
What held up, and what did not.
