Stirling PDF
Stirling PDF gives you a private toolbox for everyday document work: merge, split, compress, convert, OCR, sign, redact, and automate PDFs without uploading them to random websites.
Install it from Suite Manager → Apps — once running it lives atstirling-pdf.<your-domain> and on your Home dashboard.
What you can do
- Fix everyday PDF problems — Merge, split, compress, rotate, redact, sign, and convert documents from one private web app.
- Keep sensitive files local — Run document tools on your own server instead of sending private files to third-party upload sites.
- Automate repeat work — Use pipelines for repeatable document workflows when the same manual steps keep coming back.
A self-hosted Adobe Acrobat alternative
Stirling PDF does the job people use Adobe Acrobat, iLovePDF, Smallpdf, PDF24, Sejda, Soda PDF, Nitro PDF, and Foxit PDF for, on a server you own: the same everyday task, without a subscription and without an account at a company that also keeps your data. If you arrived comparing one of these, this is the app My Own Suite installs in its place — its privacy posture below says exactly what it does and does not send anywhere.
- Adobe Acrobat alternative
- iLovePDF alternative
- Smallpdf alternative
- PDF24 alternative
- Sejda alternative
- Soda PDF alternative
- Nitro PDF alternative
- Foxit PDF alternative
Good to know
Stirling PDF
External dependencyPrivacy grade C (A is best, D is worst)Something leaves your server in normal use and there is no in-app setting that stops it. MOS reviewed that and accepted it as the price of the feature. The full assessment says exactly what leaves, who receives it, and why.
Contacts one host outside your server in normal use, before you turn anything on.
api.iconify.designFrom your browser
- Resource needs: Medium resources — One service that sits quietly between jobs, but wants a spare gigabyte and a couple of cores while it reads a scan or converts an office document.
- Package-provided privacy notes (not independently verified by MOS): The server processes ordinary PDF tasks locally and contacts nothing. MOS keeps the PostHog analytics and Stripe payment library that Stirling PDF's pages start on its own server, so only icons are fetched from Iconify.
- Persistent app data is kept in package-owned volumes.
- User-invoked features such as trusted timestamping can contact an external service.
- Stirling PDF's own analytics setting does not reach PostHog or Stripe in its pages, so MOS patches the pages instead. Buying a Stirling PDF licence inside the app no longer works.
Just want to try Stirling PDF?
MOS is the way to grow a suite — apps installed, backed up, and updated together, all in one tailored dashboard. But if you'd rather see Stirling PDF on its own first, we've set up a one-click deploy on Railway so you can kick the tires with nothing to install.
Install in MOS
Recommended- Yours to control — runs on your own machine or any VPS you pick — and can move anytime
- One dashboard — every app you run, in one place at your own domain
- Backups built in — back up and restore your apps in a couple of clicks
- Fully private if you want — on your own hardware, apps can stay off the public internet entirely
- Updates handled — version-pinned, health-checked, applied for you
- HTTPS and domains — trusted certificates without touching DNS records
- Apps that connect — file, calendar, and office apps work together
Try it on Railway
Good for testing- Live in minutes — deploy from a template, fill in a few setup fields
- The real thing, not a demo — the same app MOS installs, running for you
- Free trial — limited free trial for new users
- Railway account required — a third-party cloud with its own sign-up and usage billing
- Tied to Railway — MOS runs anywhere and can migrate; this deploy lives on their platform
Privacy assessment
This is the assessment behind Stirling PDF's posture grade, exactly as it ships inside the package. It describes Stirling PDF 2.10.0 as MOS packages it and nothing else — install a different version and its own assessment travels with it. Reviewed 5 October 2026, due for reassessment by 16 January 2027.
What was reviewed
- Package — content digest
59204755a8b5…at commitef5027cc1528 - Stirling PDF — version 2.10.0 from
docker.io/stirlingtools/stirling-pdfpinned at4d9abedcd57a…
Deliberately outside this assessment:
- Stirling PDF desktop applications
- Stirling Cloud
- Third-party API clients
What it connects to
Every host Stirling PDF contacts in normal use as MOS ships it, before you turn anything on. The MOS test suite fails this package if it contacts a host this list does not name.
api.iconify.designFrom your browserFetches some of the interface's icons. It sees the browser's address and which icons were asked for.
Received by Iconify
Evidence
ObservedWatched on the wire, in a running instance of this package.
The MOS E2E network capture recorded this package on a MOS lab on 2026-10-05, through install, the package's own journey (signing in and replacing the default password, then merging two PDFs and downloading the result), a backup and a restore. It recorded every DNS lookup the package's containers made, read inside each container, every connection they opened to a public address, read on the Docker bridges, and every request the browser made to a host outside the suite. A control lookup and connection sent from inside each container showed up, so silence here is a measurement rather than a capture that failed. The server container made no lookup and no connection. The browser, on Stirling PDF's own pages, loaded https://js.stripe.com/basil/stripe.js, sent requests to r.stripe.com and m.stripe.com and loaded m.stripe.network/inner.html, which are Stripe's fraud-detection signals. It also loaded https://eu-assets.i.posthog.com/static/exception-autocapture.js and fetched https://api.iconify.design/material-symbols.json, all with SYSTEM_ENABLEANALYTICS=false applied. A browser capture on 2026-08-13, over a longer session, also saw eu.i.posthog.com. SYSTEM_ENABLEANALYTICS=false therefore does not stop the web client from loading PostHog or Stripe, and the package offers no other switch that does.
Source: MOS E2E `npm run e2e -- @app-cycle stirling-pdf`, run 20261005-112726-app-cycle-stirling-pdf (network/report.md), on the package version reviewed before this revision · checked 2026-10-05
The package now patches the web client at build time, pointing PostHog's host and Stripe's script host at paths on Stirling PDF's own server, where those requests fail. Two builds were compared on the MOS lab, each with SYSTEM_ENABLEANALYTICS=false and its sign-in page open in a browser for 25 seconds. The unpatched image loaded js.stripe.com, m.stripe.network, m.stripe.com and r.stripe.com, and a script from eu-assets.i.posthog.com, before anyone signed in. The patched image made no request outside the server. Stirling PDF's in-app licence purchase, which uses Stripe, no longer works. Icons the interface fetches from api.iconify.design are unchanged.
Source: apps/stirling-pdf/Dockerfile and patch-web-client.py, both builds opened in Chromium against the MOS Hyper-V lab · checked 2026-10-05
ConfiguredRead from the configuration MOS actually ships.
MOS sets SYSTEM_ENABLEANALYTICS=false for the packaged service.
Source: apps/stirling-pdf/manifest.json
DocumentedTaken from upstream documentation, policies or source.
Upstream documents SYSTEM_ENABLEANALYTICS=false as the system-wide control that disables PostHog and Scarf analytics.
Source: Stirling PDF Analytics and Telemetry documentation · checked 2026-07-16
The self-hosted server processes ordinary PDF operations locally without requiring an upstream account.
Source: Stirling PDF documentation · checked 2026-07-16
Some user-invoked features can contact external services; trusted timestamping sends a document hash to a time-stamp authority.
Source: Stirling PDF Security feature documentation · checked 2026-07-16
What this review does not settle
Published rather than smoothed over. Each of these is a limit of the method, not a finding against the app.
- Optional tools may contact services beyond the documented timestamp-authority example when explicitly invoked.
- The interface fetches some of its icons from api.iconify.design, which sees the browser's address and the icon names. Serving them from the package would need the icon data bundled, which was not attempted.
Policies read
- license — Stirling Tools · retrieved 2026-07-16
How this review was produced
- Method — AI-assisted review, not yet reviewed by a human
- Model — claude-opus-5-5 (Anthropic)
- Workflow —assess-app-privacy at
5146372c3c87 - Repository commit —
91dbeb466ec0
Technical reference
Maintained alongside the package at apps/stirling-pdf/README.md and rendered here as-is.
Stirling PDF MOS Package
Environment Variables
SERVER_HOST: Projected from the app public URL.SYSTEM_ENABLEANALYTICS=false: Disables Stirling PDF’s own analytics; the web client needs a patch as well (see Privacy Controls).
Volumes And Persistence
configs:/configs: Server configuration.custom-files:/customFiles: Custom assets.logs:/logs: Application logs.pipeline:/pipeline: Saved automation pipelines.training-data:/usr/share/tessdata: OCR language data.
Disable preserves these volumes so the app can be started again. Uninstall removes the app containers, routes, Suite Manager state, and these Docker volumes so the package returns to a clean installable state.
Setup
No user inputs are required; the package installs with an empty setup form.
Health Check
http://stirling-pdf:8080/api/v1/info/status
Privacy Controls
MOS sets SYSTEM_ENABLEANALYTICS=false, the upstream-supported system-wide control for disabling Stirling PDF analytics and suppressing its analytics consent prompt. It does not reach two things the web client starts on every page: PostHog, initialised at load with api_host: "https://eu.i.posthog.com", and Stripe’s @stripe/stripe-js, which injects https://js.stripe.com/basil/stripe.js on import.
patch-web-client.py runs at build time and rewrites those two hosts in static/assets/*.js inside /app/app.jar to /mos-blocked/posthog and /mos-blocked/stripe, so the requests go to Stirling PDF’s own server and fail there. The build stops unless each host occurs exactly once, so a new upstream version cannot bring them back unnoticed. Side effect: the in-app licence purchase, which uses Stripe, no longer works. Icons the interface fetches from api.iconify.design are left alone.
User-invoked features such as trusted timestamping can still contact an external service.