🩺 Vitals
- 🟢 Last active: 2026-10-08
- 📦 Latest release: v3.226.3 (2026-10-07)
- 🐞 Open issues: 205
- 🌟 Stars: 4.1k
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent tagged, packaged version the maintainers published. Not every healthy project tags releases.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: tolgee.io
- Source: github.com/tolgee/tolgee-platform
- License: Apache 2.0 (open core; the enterprise
ee/modules are proprietary) - Deployment: Docker | Native Binary
- Data Model: PostgreSQL; exports JSON, XLIFF, PO, CSV and other formats
- Jurisdiction: Czech Republic 🇨🇿 / EU 🇪🇺 (Tolgee s.r.o.)
- Compliance (SaaS): ISO 27001 | GDPR
- Compliance (Self-Hosted): Self-Hosted (User Managed)
- Complexity: Low (2/5) - Application plus a single PostgreSQL database via Docker Compose
- Maintenance: Low (2/5) - Periodic image updates and database backups; no separate worker or cache tier to operate
- User Management: Low (2/5) - Free build offers basic multi-user access up to 10 seats; SSO, granular RBAC, and activity logs are paid Enterprise-Edition features
1. The Executive Summary
What is it? Tolgee is a developer-focused localization platform, best known for in-context translation editing, where translators edit strings directly over a running application, and for SDKs that integrate with common web, mobile, and desktop frameworks. It is developed by Tolgee s.r.o., an EU company in the Czech Republic, on an open-core model: the core platform is Apache-2.0, while enterprise features live in a proprietary ee/ directory. The official Docker image ships with that enterprise code included but inactive and free for up to 10 seats; unlocking the enterprise features or going beyond 10 seats requires a paid licence. A fully open-source deployment is possible by removing the ee/ modules and building from source, which lifts the seat cap at the cost of the enterprise features and some build-pipeline work. Translations export to standard formats (JSON, XLIFF, PO, CSV), so the data stays portable.
The Strategic Verdict:
- 🟢 For developer teams that fit the free tier and want in-context, SDK-driven localization: A strong fit. The in-context editor and framework SDKs are a productive workflow, the core is Apache-2.0, and the project is EU-governed.
- 🔴 For organizations needing SSO, granular RBAC, audit logs, or more than 10 seats: Caution. Those are paid Enterprise-Edition features, the official binaries carry proprietary code that is a licence breach to use beyond the free limits, and a fully open deployment means building and maintaining a custom community image from source. Budget for either the licence or that build pipeline.
2. The "Hidden" Costs (TCO Analysis)
| Cost Component | Crowdin (SaaS) | Tolgee (Self-Hosted) |
|---|---|---|
| Licensing | Per-seat subscription | $0 community build; official binary free to 10 seats |
| In-Context Editing | Paid feature tiers | Included in the open core |
| SSO & Granular RBAC | Paid tiers | Paid Enterprise Edition, even when self-hosted |
| Data Residency | Vendor cloud | Your infrastructure and database |
3. The "Day 2" Reality Check
🚀 Deployment & Operations
- Installation: A Docker Compose stack of the application and a single PostgreSQL database, or a Java binary. There is no separate cache or worker tier, so the standard deployment is light.
- The open-source build is a deliberate choice: The default official image contains the proprietary enterprise code, inactive unless licensed. Running a fully Apache-2.0 deployment means removing the
ee/modules and compiling from source, which removes the 10-seat cap but also the enterprise features, and adds a build step to your pipeline. - Data & Exit: Strings export to standard localization formats (JSON, XLIFF, PO, CSV) and the PostgreSQL database can be dumped directly, so translation data stays portable regardless of which build you run.
🛡️ Security & Governance (Risk Assessment)
- Jurisdiction & Governance (Czech Republic 🇨🇿 / EU 🇪🇺): Tolgee s.r.o. is an EU company, so the project sits under EU and GDPR jurisdiction and outside US CLOUD Act reach, and self-hosted deployments send no data to the vendor. The governance nuance is concentration: a single company controls the repository and the enterprise licensing, so continuity depends on that team. The Apache-2.0 core stays forkable, but the enterprise features do not.
- The Compliance Shift: Tolgee's managed cloud holds an ISO 27001 certification and operates under GDPR, but that certificate covers the vendor's SaaS, not a deployment you run yourself. Self-hosting inverts the responsibility, and there is a specific catch: the controls a compliant deployment leans on, single sign-on, granular access control, and activity logs, are paid Enterprise-Edition features. So a compliance-ready self-hosted Tolgee effectively requires the paid licence, not the free build.
- License Risk (the open-core trap): The core is Apache-2.0, but the notable risk is what ships around it. The official binaries and Docker images include proprietary enterprise code, free only up to 10 seats and only for non-enterprise use; exceeding those limits without a licence is a breach. Treating Tolgee as fully open source therefore is not the default path: it requires stripping the
ee/directory and building your own image, which is a real engineering commitment rather than a checkbox.
4. Market Landscape
🏢 Proprietary Incumbents
- Crowdin: A dominant localization SaaS with in-context editing and broad integrations, billed per seat. Teams weigh Tolgee to keep an in-context workflow on their own infrastructure, within the free tier or a custom build.
- Lokalise: A developer-focused localization SaaS with strong automation and SDKs. Evaluated against Tolgee when the goal is a self-hosted, SDK-driven workflow rather than a per-seat subscription.
🤝 Open Source Ecosystem
- Weblate: The larger, fully open-source (GPL) localization platform, Git-native and continuous, with no enterprise-gated features, in contrast to Tolgee's open-core model.
- Traduora: A lighter, fully open-source (AGPL), API-first alternative with no paid tier, though a smaller and single-vendor project.