🩺 Vitals
- 🟢 Last active: 2026-10-09
- 📦 Latest release: weblate-2026.10.1 (2026-10-09)
- 🐞 Open issues: 456
- 🌟 Stars: 6.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: weblate.org
- Source: github.com/WeblateOrg/weblate
- License: GPL-3.0 (copyleft; not AGPL, so network use does not trigger it)
- Deployment: Docker
- Data Model: PostgreSQL with a Valkey cache and Celery workers; translations sync bidirectionally to Git
- Jurisdiction: Czech Republic 🇨🇿 / EU 🇪🇺 (Weblate s.r.o.)
- Compliance (SaaS): N/A
- Compliance (Self-Hosted): GDPR Ready
- Complexity: Moderate (3/5) - Docker Compose stack: Django app, PostgreSQL, a Valkey cache, and Celery workers
- Maintenance: Moderate (3/5) - Multi-service stack with database migrations on version upgrades and background-queue monitoring
- User Management: High (4/5) - Federated SSO (SAML, OIDC, LDAP), granular RBAC, and turnkey audit and change history, all in the self-hosted open build; SCIM provisioning is not turnkey
1. The Executive Summary
What is it? Weblate is a web-based continuous-localization platform. It manages the translation of software strings, documentation, and content, and syncs those translations bidirectionally with your Git repositories, so localization runs inside the same version-controlled workflow as your code. It is developed by Weblate s.r.o., an EU company in the Czech Republic, under GPL-3.0. Unusually for a commercially-backed tool, there is no open-core split: single sign-on, granular role-based access control, audit and change history, and every integration ship in the free self-hosted build. The company monetizes managed hosting and support rather than features. It self-hosts as a Docker Compose stack (a Django application, PostgreSQL, a Valkey cache, and Celery workers), and because the translations live in your own Git, the exit path is your repository.
The Strategic Verdict:
- 🟢 For organizations localizing software or content that want their translations in their own Git and infrastructure: Strong Buy. Continuous localization under a copyleft open-source licence, with SSO and RBAC included rather than sold as an enterprise add-on, and a Git-native exit that removes vendor lock-in.
- 🔴 For small teams without the capacity to run a multi-service stack: Caution. Weblate is a Django application with PostgreSQL, a cache, and background workers, so standing it up and keeping it patched is real operational work. Teams without that capacity often use the vendor's managed hosting instead.
2. The "Hidden" Costs (TCO Analysis)
| Cost Component | Crowdin (SaaS) | Weblate (Self-Hosted) |
|---|---|---|
| Licensing | Per-string or per-seat subscription | $0 (GPL-3.0, all features) |
| Enterprise Features | SSO and advanced workflows on higher tiers | Included in the open build |
| Data Residency | Vendor cloud | Your infrastructure and Git |
| Data Exit | Export or API | Bidirectional Git sync (your repos) |
3. The "Day 2" Reality Check
🚀 Deployment & Operations
- Installation: A Docker Compose stack that bundles the dependencies in one file: the Django application, PostgreSQL, a Valkey cache that doubles as the Celery broker, and Celery workers. Straightforward to bring up, but a multi-service system rather than a single container.
- Integration model: Bidirectional Git sync is the core of the tool. Weblate commits finished translations back to your repository and pulls source-string changes in, integrating with Forgejo, Gitea, GitLab, and GitHub. Localization runs continuously alongside your existing CI, which is what "continuous localization" means in practice.
- Scalability: Celery workers can be split across task queues to scale background processing, and PostgreSQL and the cache follow standard scaling patterns. The load is translation and version-control-sync throughput rather than heavy compute.
🛡️ Security & Governance (Risk Assessment)
- Jurisdiction & Governance (Czech Republic 🇨🇿 / EU 🇪🇺): Weblate s.r.o. is an EU company in the Czech Republic, so the project sits under EU and GDPR jurisdiction and outside US CLOUD Act reach, and for a self-hosted deployment no data reaches the vendor at all. The governance nuance is concentration: development sits with a single founder-led company rather than a foundation, so continuity rests on that entity. The GPL-3.0 licence is the hedge, keeping the code forkable and open regardless of corporate direction.
- The Compliance Shift: Self-hosting places infrastructure security, data-at-rest encryption, patching, and monitoring on you. Weblate ships the concrete controls a compliant pipeline needs: RBAC, SSO, and configurable audit logging with a retention setting, plus operable GDPR tooling where a user can export their account data as JSON and request an account removal that anonymizes the record. The vendor also publishes software bills of materials (SBOMs) as a Cyber Resilience Act readiness signal, which matters if you ship Weblate inside a product of your own. Meeting GDPR remains a property of your deployment and controls, not a certificate the software carries. CRA duties sit with whoever supplies a product on the EU market in the course of a commercial activity; running Weblate for your own use carries none.
- License Risk (GPL-3.0, not AGPL): GPL-3.0 is copyleft, so distributing a modified Weblate obliges you to publish those modifications. The distinction that matters for a hosted deployment is that, unlike AGPL, running Weblate over a network for your own or customers' users does not trigger the copyleft, so internal and customer-facing hosting carries no source-disclosure obligation. There is no open-core tier to buy around, which removes the usual enterprise-tax trap.
4. Market Landscape
🏢 Proprietary Incumbents
- Crowdin: The dominant SaaS localization platform, billed per string and seat. Teams weigh Weblate to move translations onto their own Git and infrastructure and off metered per-string pricing.
- Lokalise: A developer-focused localization SaaS with heavy automation. Evaluated against Weblate when the goal is to keep a continuous-localization workflow without a per-seat subscription or vendor-held data.
🤝 Open Source Ecosystem
- Tolgee: An open-source, self-hostable localization platform with an in-context editing focus; a lighter path for teams centred on web and app UI strings rather than Weblate's broad file-format and version-control coverage.
- Traduora: A lighter, API-first translation-management platform. Where Weblate is Git-native and continuous, Traduora manages translations over a REST API without a version-control workflow, a simpler option for teams that do not need Weblate's depth.