Tool
Stirling PDF
A locally hosted PDF toolkit — merge, split, OCR, convert, sign, redact, and dozens more ops — so documents stay on your instance instead of another SaaS upload box.
What it is
Stirling PDF (docs at docs.stirlingpdf.com) lives in Stirling-Tools/Stirling-PDF. It is a self-hosted PDF toolkit with 55+ operations: merge/split, OCR, convert, sign, redact, compress, and more. You can run it via Docker, desktop builds, or bare metal. Processing happens on the instance you control — files are not shipped to a third-party PDF SaaS by default. OCR and some conversion paths pull in extra dependencies (Tesseract, LibreOffice, and similar) depending on how you install.
What it replaces
It replaces cloud PDF suites like Adobe Acrobat online workflows, ILovePDF, and Smallpdf for self-hosters who want merge/split/OCR/sign/redact without uploading sensitive docs to a vendor. It does not replace a full document management system like Paperless-ngx, enterprise Acrobat Pro feature parity, or a lawyer-reviewed redaction process for regulated disclosure.
License
The core project is largely under the MIT License, but that is not the whole story. Paths under proprietary / saas / engine and listed proprietary editor directories carry separate licenses — they are not “MIT free-for-all.” Paid Server / Enterprise (SSO and related commercial features) is a commercial product path. Re-check the repo LICENSE and proprietary notices before redistributing or assuming every UI feature is MIT.
Where it falls over
- Public UI without auth — hang it naked on the internet and strangers get a PDF workshop on your box.
- OCR / LibreOffice / related deps — missing packages mean broken convert/OCR paths until you install them.
- Proprietary / paid paths ≠ MIT — do not treat Server/Enterprise or proprietary editor dirs as open-core freebies.
- You own backups, disk, and who can reach the UI — self-hosting the toolkit does not automate trust.
- Redaction quality depends on how you use the tools; “looks blank” is not always “gone from the PDF.”
Who it's for
Homelab and small-team operators who already run Docker (or a desktop install), want PDF ops without SaaS uploads, and will put auth / Tailscale / reverse-proxy in front of the UI. Wrong tool if you needed Acrobat Pro enterprise workflows with a vendor SLA, or assumed every Stirling feature was MIT-redistributable.
Related in this cluster
- Paperless-ngx — document DMS with OCR for archives
- Nextcloud — files/sync suite where PDFs often live
- Docker — common packaging path
- Nginx Proxy Manager — TLS / reverse proxy in front of the UI
- Tailscale — keep the admin UI off the public internet
Verdict
Use Stirling PDF when a self-hosted PDF toolkit beats uploading sensitive docs to another SaaS, and you will secure the UI and read the MIT + proprietary split honestly. Skip the “everything is free MIT” cosplay if you need SSO/Enterprise features or redistribute proprietary paths without checking their licenses.
← Tools · Home · stirlingpdf.com · GitHub