Self-hosted server
Run Stirling PDF on your own servers, on-premises or with your own cloud provider. Your team uses it in a browser or the desktop app.
Pick a build#
| Build | Login and admin settings | Use it when |
|---|---|---|
Docker latest |
Yes | You want the standard server. Start here. |
Docker latest-fat |
Yes | You also want the AI engine inside the same container. AI stays off until you turn it on. |
Docker latest-ultra-lite |
No | Hardware is limited and you only need the core tools. No OCR or Office conversions. |
Stirling-PDF-with-login.jar |
Yes | You can't use Docker and will install Java and the conversion tools yourself. |
Stirling-PDF.jar |
No | As above, for a single user who needs no login. |
Stirling-PDF-server.jar |
No | You only need the REST API. It has no web interface. |
Builds without login have no users, single sign-on or admin settings, so everything is set in files or environment variables.
Quick start#
Start the latest image with the compose file or docker run command in Install with Docker, then open http://localhost:8080.
First login#
Login is on by default. Sign in with:
Username: admin
Password: stirlingYou are then asked to set a new password of at least 8 characters. The first admin is also asked whether to send anonymous usage data: see Analytics and telemetry.
To create your own first admin instead, set SECURITY_INITIALLOGIN_USERNAME and SECURITY_INITIALLOGIN_PASSWORD before the first start. They are only used while the database has no users.
To run with no login at all, set SECURITY_ENABLELOGIN=false. Anyone who can reach the server can then use it.
The free plan covers up to 5 users. Team and Enterprise add seats and features: see Plans and licences.
Next steps#
Images, volumes and updates.
Helm chart and persistence.
Run the JAR without Docker.
HTTPS, users, backups and monitoring.
Settings, files and environment variables.
Login options, email and single sign-on.
Turn on the AI assistant and tools.
What changes when you move from V1.
Common admin questions and fixes.