Skip to main content
Productivity

Self-host Stirling PDF on a VPS

A self-hosted PDF toolbox.

Merge, split, compress, convert, OCR and sign PDFs locally without uploading them anywhere.

Why self-host Stirling PDF?

Stirling PDF handles sensitive documents entirely on your own server — nothing leaves your machine.

How to install Stirling PDF

  1. 1

    Provision a VPS

    Choose a plan with room for your data as well as the app.

  2. 2

    Install the stack

    Install Java/Spring + Docker.

  3. 3

    Deploy the application

    Follow the project’s official install guide for your distribution.

  4. 4

    Enable HTTPS

    Serve it on your own domain behind a reverse proxy with a certificate.

  5. 5

    Back it up

    Schedule a database dump plus a copy of any uploaded files to an off-box location.

Practical tips

  • Give Stirling PDF its own database user with rights only on its own schema.
  • Reverse-proxy Stirling PDF and terminate TLS at the proxy so certificates are managed in one place.
  • Take a VPS snapshot before major upgrades so you can roll back cleanly.
  • Keep Stirling PDF patched — most self-hosting incidents are unpatched software.

Frequently asked questions

How much RAM does Stirling PDF need?
Plan on 1–2 GB for typical use; add headroom if you expect many concurrent users.
What stack does Stirling PDF run on?
Java/Spring + Docker.
Can I run other things on the same VPS?
Yes — size the plan so Stirling PDF plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include PDFsam, Docuseal, Adobe (hosted) — browse all app guides.