🩺 Vitals
- 🟢 Last active: 2026-07-10
- 📦 Latest release: v0.1.3 (2015-02-26)
- 🐞 Open issues: 164
- 🌟 Stars: 18k
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: overleaf.com
- Source: github.com/overleaf/overleaf
- License: AGPL-3.0
- Deployment: Docker (Overleaf Toolkit)
- Data Model: MongoDB / Redis / S3
- Jurisdiction: United Kingdom 🇬🇧 (Digital Science, Holtzbrinck)
- Compliance (SaaS): GDPR
- Compliance (Self-Hosted): Self-Hosted (User Managed)
- Complexity: Medium (3/5) - Docker Toolkit + MongoDB / Redis
- Maintenance: Medium (3/5) - Stateful services, backups, upgrades
- Enterprise Ready: Medium (3/5) - SSO & user isolation require paid Server Pro
1. The Executive Summary
What is it? Overleaf is the de facto standard for collaborative LaTeX: a real-time, browser-based editor for academic, scientific, and technical writing where multiple authors edit the same typeset document at once. The same codebase ships as a free, self-hostable Community Edition (AGPLv3) and a commercial Server Pro tier. For a research institution or R&D team, the draw is keeping unpublished manuscripts, grant proposals, and IP on infrastructure they control while retaining raw .tex portability. It is operated by Digital Science, part of the Holtzbrinck publishing group.
The Strategic Verdict:
- 🔴 For Untrusted or Zero-Trust Multi-Tenancy: Caution. The free Community Edition has no per-user sandboxed compilation, so the project itself flags it as unsuitable where users must be isolated. That sandboxing, along with SSO, requires the paid Server Pro tier.
- 🟢 For Research Institutions & R&D Teams: Strong Buy. Self-host the standard tool for collaborative LaTeX, keep sensitive research on your own infrastructure, and avoid document lock-in entirely with native
.texand ZIP export.
2. The "Hidden" Costs (TCO Analysis)
| Cost Component | Google Workspace (SaaS) | Overleaf (Self-Hosted CE) |
|---|---|---|
| Seat Pricing | Per-user Workspace | $0 CE (unlimited users) |
| LaTeX / Math Typesetting | Not native | Native (full LaTeX engine) |
| Data Residency | Google cloud | Your own server |
| SSO, Sandboxing & Git Bridge | Workspace tiers | Overleaf Server Pro (paid) |
3. The "Day 2" Reality Check
🚀 Deployment & Operations
- Installation: Deployed with the Overleaf Toolkit (Docker), which orchestrates the application plus MongoDB and Redis; an S3 backend and the Git Bridge are optional. It is containerized but multi-service and stateful, so plan for backups of MongoDB and Redis from day one.
- Scalability: Server Pro scales to institutional user counts with isolation and SSO. The Community Edition runs a single shared compile environment without per-user sandboxing, which limits its safe use to trusted internal groups rather than open multi-tenant deployments.
🛡️ Security & Governance (Risk Assessment)
- Jurisdiction & Ownership (United Kingdom 🇬🇧): Overleaf is operated by Digital Science (Holtzbrinck group) under UK GDPR. Self-hosting removes cloud-jurisdiction exposure outright; for the managed cloud, AWS/GCP regional hosting can bring US CLOUD Act reach into scope for some tenants. Governance is moderate: strong corporate backing and AGPL protection against proprietary capture, but no independent foundation.
- The Compliance Shift: The managed cloud runs under Digital Science's corporate security program (the vendor reports group-level ISO 27001) and is GDPR-aligned, but none of that transfers to a self-hosted instance. Server Pro can underpin FedRAMP-style or air-gapped deployments, yet readiness depends entirely on your own SSO, user isolation, and infrastructure hardening. It is a capability you implement, not a certificate you inherit.
- License & The Open-Core Line (AGPL-3.0): AGPLv3 network copyleft applies: modify Overleaf and serve it to external users, and you must publish your changes; internal use is unrestricted. The commercial line is open-core: the Community Edition is a genuinely usable LaTeX platform, but the capabilities enterprises usually need (SSO/SAML/LDAP, per-user sandboxed compilation, tracked changes, and the Git Bridge) are Server Pro features, so budget for licences if you need them.
4. Market Landscape
🏢 Proprietary Incumbents
- Google Workspace: Google Docs for collaborative writing; research teams move to Overleaf when they need native LaTeX and math typesetting Docs cannot produce, and when manuscripts must stay off a US cloud.
- Microsoft 365: Word with co-authoring; Overleaf wins for reproducible scientific typesetting, equation-heavy documents, and self-hosted data residency.
🤝 Open Source Ecosystem
- Typst: A modern open-source typesetting system and lighter LaTeX alternative; today an engine and CLI with an emerging collaborative layer rather than a mature multi-user platform.
- Quarto: An open-source scientific and technical publishing system (Pandoc-based) for reproducible documents; a toolchain and CLI rather than a real-time multi-author web editor.