Skip to main content
Here, we’ve compiled answers to some frequently asked questions about Ayakaleaf Pro.

Basic Question

No. Ayakaleaf Pro is completely free to use. It is not a trial and requires no license.
Yes. Ayakaleaf Pro includes all Overleaf Server Pro features, including Git-Bridge integration. It also includes selected features from the Overleaf SaaS platform. We continue to develop and improve Ayakaleaf Pro.
Overleaf Server Pro costs around $300 per user each year. It requires at least 10 licenses, so deployments start at roughly $3,000 annually. Smaller public U.S. contracts show annual costs of about $320–$370 per user. This makes Server Pro expensive, especially for smaller teams. See #information-and-price-about-overleaf-server-pro for documented purchases and pricing.
Overleaf Server Pro is commonly used by government organizations. They deploy it on private networks and strictly control access. To protect sensitive data, its included features avoid exchanging data with third-party services. If you need GitHub Sync, AI, or similar connected features, Overleaf recommends a subscription to its SaaS platform.
Ayakaleaf Pro is open source. We review the code with tools such as Codex Security to strengthen its security and reliability. If you do not enable third-party data synchronization, your data stays on your server. Ayakaleaf Pro contains no telemetry that sends your data elsewhere.
We will make every effort to maintain this project over the long term.
Ayakaleaf Pro is a community fork. Its code and integrated features come from community contributions. It is licensed under AGPL v3. Deployments can comply with this license when they meet its requirements.
The project was originally named Overleaf Pro in 2024. Development paused for a time, then restarted in late 2025. In the first quarter of 2026, Overleaf renamed its AI-enabled subscription plan to Pro. Community feedback also noted that the Overleaf Pro name could create trademark and impersonation risks. It could make users think the project was official.We renamed the project Ayakaleaf Pro to avoid that confusion. The name can be read as “Ayaka-notes Overleaf Pro.” The maintainer (you can call me ayaka!) has contributed to Overleaf community development since their student years, over five years ago. This experience supports our long-term maintenance commitment.
Since 2026, the open-source community has released many AI-built LaTeX editors, including OpenAI Prism. Ayakaleaf Pro keeps your data and services on your own server. This gives you direct control over your deployment and data.Many experimental community editors have no established long-term maintenance plan. Third-party LaTeX compilation platforms can also stop operating when their user base or revenue is insufficient. Ayakaleaf Pro delivers all source code and lets you self-host every service. Even if maintenance stopped, your existing self-hosted service could continue to run.
It was renamed to ayaka-notes/ayakaleaf-pro with the project rename (see Q08). It was not archived or replaced: it is the same repository, and GitHub redirects old ayaka-notes/overleaf-pro links and Git remotes to the new name. The Docker image keeps its name, ghcr.io/ayaka-notes/overleaf-pro, so you do not need to change config/overleaf.rc or config/version.

Features

Please check our documentation for the current feature list. If there’s a feature you’d like us to add, feel free to open a issue (for feature request) on GitHub. We’ll do our best to implement requested features, but development takes time, and we can’t guarantee that every feature will be delivered right away.
Contributions are welcome, but acceptance is not guaranteed. We evaluate each PR based on its impact on the underlying Overleaf codebase, its maintenance burden, and the value it brings to users. We’ll do our best to merge and maintain valuable contributions.However, we may reject PRs that introduce excessive changes, consist of unreviewed or poorly understood AI-generated code (“vibe coding”), or add features that would be difficult to maintain over time.
We generally update the documentation whenever we release a new feature. Please refer to the relevant documentation for detailed setup instructions and explanations of the available environment variables.
The Python Runner runs Python in the user’s browser with Pyodide 0.29.3, not on the server. It loads the packages that your code imports from the packages built into Pyodide, such as NumPy, pandas and Matplotlib. Packages installed with pip and other packages are not available. There is nothing to configure on the server.
No. The spell checker has no dictionary for Japanese or Chinese, so these languages are not in the spell-check language list. Users can turn off spell checking for a project in the editor settings.To stop a word from being marked as misspelled, right-click it and choose Add to dictionary. Added words are saved to your account and apply to all your projects. To review or remove them, open the editor settings, then Spelling and language → Dictionary → Edit. Adding words does not add a new spell-check language.
There is no plugin installer. Features are modules in services/web/modules of the source code, built into the Docker image and turned on with the settings in this documentation. To add your own, add a module to the source code and build your own image.

Deployment

For most users, we recommend deploying with the Toolkit. Kubernetes support is experimental: Using Kubernetes shows the manifests we tested with one or several replicas, but a cluster adds operational complexity and maintenance effort. Sandboxed Compiles create their compile containers through the Docker socket, so every node that runs Ayakaleaf Pro needs Docker Engine. We do not provide CRI-O, Podman or Quadlet configurations.
Please refer to our horizontal scaling guide. You can deploy multiple Overleaf instances and configure a load balancer to distribute traffic across them.
If you have an existing Overleaf Server Pro instance, we’d be happy to help you migrate to Ayakaleaf Pro. Please contact via email or issues.
No. Ayakaleaf Pro must be served from the root of a domain. Use a dedicated domain or subdomain, such as https://overleaf.example.com.
Yes. The Toolkit runs on Linux, macOS with Docker Desktop, and Windows with WSL 2 and Docker Desktop. We recommend Linux for shared and production servers. The macOS and Windows guides include sandboxed compile setup.We do not provide a standalone docker-compose.yml. To see the Compose configuration that the Toolkit uses, run bin/docker-compose config in the Toolkit directory.
There is no uninstall script. In the Toolkit directory:
  1. Stop and remove the containers with bin/docker-compose down.
  2. Delete the data. By default it is in the data/ directory of the Toolkit. If you changed OVERLEAF_DATA_PATH, MONGO_DATA_PATH, REDIS_DATA_PATH or GIT_BRIDGE_DATA_PATH in config/overleaf.rc, delete those directories too. This cannot be undone, so back up first if you may need the data.
  3. Delete the Toolkit directory.
  4. Remove the Docker images, which you can list with docker images: ghcr.io/ayaka-notes/overleaf-pro, the git-bridge image, mongo, redis and the TeX Live images.
Run these in the Toolkit directory:
  • bin/stop stops all containers, bin/start starts them again. The containers are kept, so users stay logged in.
  • bin/up -d creates the containers and starts them in the background. Run it after changing config/variables.env, config/overleaf.rc or config/version: it recreates the containers whose configuration changed, and only then do the changes take effect. bin/stop and bin/start do not apply them.
  • bin/docker-compose restart sharelatex restarts only the Overleaf container, without applying configuration changes.
If users are logged out every time bin/up recreates the container, set OVERLEAF_SESSION_SECRET, see the Q&A in Environment Variables.
In the application you create at the provider, not in Ayakaleaf Pro. There is no callback setting in config/variables.env for any of these integrations: Ayakaleaf Pro builds every callback URL from OVERLEAF_SITE_URL and sends it to the provider, which rejects it unless it matches the one registered for the application. So you only register it at the provider, and set OVERLEAF_SITE_URL to the address users open.If you change OVERLEAF_SITE_URL, for example to a new domain, update the URL at every provider too, or linking fails.
By default, everything stays on the server’s local disk, in the Toolkit’s data/ directory: data/overleaf (project files, history and compile output), data/mongo and data/redis. For instances with fewer than 1000 users, local disk with regular backups is what we recommend.The Ayakaleaf Pro image takes about 5 GB. The 40 GB minimum in the Introduction is for Sandboxed Compiles, whose texlive-full images take about 28 GB each. Without Sandboxed Compiles, compiles run inside the sharelatex container with the TeX Live basic scheme plus latexmk, texcount, synctex, etoolbox and xetex, so many projects fail with missing packages. The data/ directory then grows with your projects and their history; check it with du -sh data/*.
Yes, provided Windows stays awake and Docker Desktop stays running. Turn on Start Docker Desktop when you sign in to your computer, keep the Toolkit’s restart: always policies, and disable automatic sleep and hibernation while on AC power. The screen can turn off; laptop lid behavior is a separate setting. Closing the Ubuntu terminal after bin/up -d does not stop detached containers. Quitting Docker Desktop, pausing its engine or running wsl --shutdown interrupts the service.Docker Desktop’s Resource Saver is different from Windows sleep: it applies when no containers are running, so a running Ayakaleaf stack is not idle merely because nobody is editing. After a Windows reboot, the login startup setting still requires someone to sign in. Follow Keep the instance available for the checks and recovery steps. Linux remains our recommendation when availability must not depend on an interactive desktop login.
This guide uses the WSL 2 backend. It needs CPU virtualization enabled in BIOS/UEFI, Windows’ Virtual Machine Platform feature, and a working WSL 2 installation. The full Hyper-V feature is a separate Docker Desktop backend and is not a prerequisite for this WSL setup.Check Task Manager → Performance → CPU → Virtualization and wsl --list --verbose in PowerShell. Errors such as 0x80370102 can mean virtualization, the Windows feature or the boot hypervisor is disabled. See the Windows installation troubleshooting steps, with Microsoft’s and Docker’s repair links. Restart Windows after enabling the required features; reinstalling Ayakaleaf cannot fix a Docker engine that does not start.

LaTeX

When you enable Sandbox Compiles, each user’s compilation runs in a separate Docker container and is isolated from other users’ compilations. Shell Escape is enabled by default for Sandbox Compiles.
We have improved our TeX Live Full image for Sandbox Compiles over the past three years. In most cases, projects that compile on overleaf.com also compile correctly with Ayakaleaf Pro. If a required font is unavailable, upload that font to your project manually.
Please upload your project to the official Overleaf website, enable read-only link sharing, and include the link in a GitHub issue.We will investigate and fix any bugs that prevent a project from compiling in Ayakaleaf Pro when it compiles successfully on the official Overleaf website. Compilation problems outside this scope are not covered by our support.
Last modified on November 5, 2026