FormaTeX

\compare{vs-self-hosting}

LaTeX API vs Self-Hosting TeX Live

apt install texlive-full pulls down a 4 GB image, requires ongoing patching, and adds an always-on server to your infrastructure. FormaTeX handles all of that so you do not have to.

Get started free Free compiler info

\section{Self-Hosting Reality}

What self-hosting TeX Live actually means

4 GB Docker image

texlive-full installs every LaTeX package, font, and documentation file. Your CI pipeline pulls gigabytes on every build.

Security patching

TeX Live packages have CVEs. Keeping them patched means tracking upstream releases, rebuilding images, and redeploying — continuously.

Always-on cost

A TeX server sits idle between requests but still consumes compute. You pay for it whether you compile one document or one thousand.

Concurrency management

Multiple simultaneous compilations can exhaust CPU and memory. You need a job queue, worker pools, and timeout handling — all custom.

\section{Feature Comparison}

FormaTeX vs self-hosting TeX Live

A practical breakdown of what changes when you stop maintaining a LaTeX server yourself.

DimensionFormaTeXSelf-hosted TeX Live
Docker image size~50 MB app image~4 GB with texlive-full
Time to first compilationMinutes (API key + one request)Hours (install, configure, test)
Security patchesYesManual — your team's responsibility
TeX Live updatesYesManual apt upgrade or rebuild
Uptime SLAYesNo
Concurrency / scalingHandled automaticallyManual queue + worker management
CI/CD integrationYesRequires custom tooling
Infrastructure costPay per compilationAlways-on VM or container
Full TeX Live controlNoYes
Custom packages / fontsStandard packages includedYes

\section{Total Cost of Ownership}

The hidden cost of self-hosting

The server cost is visible. The developer time is not.

Infrastructure cost

Pay per compilation — zero idle cost
Always-on VM: ~$20–80/month minimum

Developer time

Minutes to integrate — one HTTP call
Days to set up, hours per month to maintain

Operational burden

Zero — FormaTeX handles uptime and scaling
Monitoring, alerting, restarts, updates

Docker image size comparison

Your app + FormaTeX API call
~50 MB
alpine + texlive-base
~300 MB
ubuntu + texlive-full
~4 GB

\section{Decision Guide}

When self-hosting still makes sense

Choose FormaTeX when…

  • You want to ship PDF generation in minutes, not days
  • Your team has no LaTeX infrastructure experience
  • You are on serverless or edge runtimes with no persistent storage
  • You want pay-per-use pricing with no idle server cost
  • Security patching and uptime are not your team's job

Self-host TeX Live when…

  • You need proprietary or custom packages not in the standard distribution
  • Your documents require fonts only available on your internal systems
  • Compliance mandates that no document content leaves your network
  • You compile tens of thousands of documents per day and unit economics favor in-house
  • You have a dedicated DevOps team with LaTeX infrastructure experience
Overleaf alternativeFree compiler infoGitHub Actions integrationView pricing

\end{vs-self-hosting}

Skip the 4 GB Docker image

Sign up free — no credit card required. One API call, any language, TeX-quality output. No server to maintain.

Get started free Try with cURL

One quick thing

We track anonymous usage — page views, feature usage, compilation events — to understand what works and what doesn't. No ads, no personal data, no third-party sharing.

Cookie policy