---
title: "Deploy Operations PDF Station with Stirling"
description: "An authenticated PDF processing station with persistent app state."
category: "Other"
url: https://railway.com/deploy/operations-pdf-station-with-stirling
---

# Deploy Operations PDF Station with Stirling

An authenticated PDF processing station with persistent app state.

**[Deploy Operations PDF Station with Stirling on Railway](https://railway.com/template/operations-pdf-station-with-stirling)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/operations-pdf-station-with-stirling/manifest.json

- **Creator:** dankeewithtwoes's Projects
- **Category:** Other

## Template content

### App

- **Image:** stirlingtools/stirling-pdf@sha256:10164ffe04961b02ebc9fa4da12064eeacb8d3bc3e09ceb059f78ce7aaa83207
- **Start command:** `/bin/sh -c 'set -eu; for d in configs storage; do mkdir -p "/data/$d"; if [ ! -L "/$d" ]; then if [ -d "/$d" ]; then cp -an "/$d/." "/data/$d/"; mv "/$d" "/$d.image"; fi; ln -s "/data/$d" "/$d"; fi; done; exec tini -- /scripts/init.sh'`
- **Public domain:** Yes

## Documentation

# Deploy and Host Operations PDF Station with Stirling on Railway

An authenticated PDF processing station with persistent app state.

## About Hosting Operations PDF Station with Stirling

Operations teams processing routine document bundles on their own server.

Allocate at least 4 GB RAM before deploying. Sign in as operator with SECURITY_INITIALLOGIN_PASSWORD from Railway variables, process a sample PDF, then download and inspect the result. Enable your own integrations separately.

### Included services and storage

| Service | Persistent storage | Public access |
| --- | --- | --- |
| App | /data | HTTPS domain |

### First deployment

1. Review required inputs in the deploy form and supply your own administrator email where requested.
2. Deploy the services and wait for the application and any database migrations to finish.
3. Open the generated HTTPS domain and follow the workflow above.

## Why Deploy Operations PDF Station with Stirling on Railway

The definition supplies an HTTPS endpoint, generated credentials where supported and explicit storage paths. PostgreSQL, when present, stays private. Public upstream image manifests are locked to immutable digests so an upstream tag change does not silently replace a running version.

## Common Use Cases

- Merge incoming document bundles.
- Split and rotate PDF pages.
- Run supported OCR and conversion tasks.

## Dependencies for Operations PDF Station with Stirling

- [Upstream application and its documentation](https://github.com/Stirling-Tools/Stirling-PDF). The upstream authors own the application and its license. This recipe does not claim application authorship or official endorsement.
- A Railway plan with resources sufficient for these services. Hosting, storage and outbound traffic are billed by Railway; no software subscription, bank connection, SMTP account or provider credit is included.

### Operational limits and backups

The template persists /configs and /storage below one Railway /data volume. Upload limit is 50 MB. OCR and conversion can require substantial CPU and memory; some features or user counts require an upstream paid plan. PDF editing does not establish legally reliable redaction. No upstream subscription is included.

Run one replica for volume-backed applications. Schedule volume backups and export important application data; a persistent volume is not a backup. Keep generated secrets with the backups and review upstream migration notes before changing the pinned image. Credentials cannot all be rotated by changing first-run environment variables after accounts already exist.

### Validation status

Prepared on 2026-10-18 from upstream installation documentation and public image manifests. Railway schema, variable references and publication metadata are checked before publication. Application runtime boot checks were not performed. This is an independently authored deployment recipe for existing software, not a claim of novel software, audited security or Railway partner verification.


## Deploy this recipe

[![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/new/template/operations-pdf-station-with-stirling?utm_source=railway-marketplace&amp;utm_medium=listing&amp;utm_campaign=toolkit-discovery&amp;utm_content=operations-pdf-station)

Review the required inputs and hosting resource costs before deploying.

### Related deployment recipes

- [Twenty CRM with Worker &amp; Shared S3](https://railway.com/template/twenty-crm-with-worker-and-shared-s3) — CRM with Postgres, Redis, background worker and shared S3 file storage.
- [Ubuntu Browser Terminal Starter](https://railway.com/template/ubuntu-browser-terminal-starter) — Password-protected Ubuntu web terminal with a persistent workspace volume.
- [Ubuntu SSH and AI CLI Starter](https://railway.com/template/ubuntu-ssh-and-ai-cli-starter) — SSH development container with generated credentials and durable workspace.

These are separate deployments; no preconfigured integration between the applications is implied.

Disclosure: this template is maintained independently. Its maintainer may earn Railway usage kickbacks when other people deploy it. Railway bills hosting separately; no paid software subscription or provider credits are included.



## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/operations-pdf-station-with-stirling
