How to Self-Host Stirling-PDF
Stirling-PDF is a local PDF platform for merge, split, convert, compress, OCR, sign, and redact without sending documents to a third party. The notes below were checked against the project site and source repository.
When Stirling-PDF is a good fit
Choose Stirling-PDF when people need everyday PDF tools and the files should be processed on a machine you administer. It also ships a desktop app. The server is the right shape when several people share one install or you want the API. You own the host, the temporary files, and the upgrades.
Deployment notes
The documented container quick start publishes port 8080 from docker.stirlingpdf.com/stirlingtools/stirling-pdf. The same project documents a desktop client and other install paths, including Kubernetes. Pin a release instead of an unqualified latest tag once you depend on the result. If you enable accounts, persist the configuration directory the current docs name for that mode so users survive a new container.
Put a shared server behind HTTPS. Turn on login before the URL is public. PDFs uploaded for conversion sit on that server for the duration of the job.
Data and recovery
Decide which directories hold configuration and any saved files, and back those up. Most operations are stateless conversions. The part you cannot regenerate is the account database and any custom settings, plus the original documents people still have only on their side.
Write down the restore sequence, required secrets, and exposed ports. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
A public Stirling-PDF with open access will process whatever strangers upload, on your CPU, with your disk. That is a document-handling service, not an anonymous demo.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
