Deploy and Host Paperless-ngx with Railway

Run Paperless-ngx v3.0.5 with Railway-native PostgreSQL, authenticated Redis, a persistent /paperless volume, generated administrator credentials, and an immutable upstream image pin.

About Hosting Paperless-ngx

Paperless-ngx indexes scanned and digital documents for authenticated search, classification, metadata, workflows, and export. This template wires the three required services without exposing the database or Redis publicly. It prepares the app volume securely and runs the steady-state application as UID/GID 1000.

Common Use Cases

Maintain a private searchable household or team document archive.
Ingest scans through upload, API, or the persistent consumption directory.
Apply tags, correspondents, document types, custom fields, and workflows.
Export content as part of a coordinated off-platform recovery process.

Dependencies for Paperless-ngx Hosting

One public Paperless-ngx app on fixed port 8000.
One private Railway-native PostgreSQL service.
One private Railway-native authenticated Redis service.
One volume mounted at /paperless.
Generated PAPERLESS_SECRET_KEY and PAPERLESS_ADMIN_PASSWORD.
Login health path, one replica, Serverless off, and on-failure restart.

Why Deploy Paperless-ngx with Railway?

The package supplies immutable source provenance, generated secrets, native-service references, strict pre-bind URL validation, root-owned-volume recovery to UID/GID 1000, persistent storage, health configuration, and tested backup/update guidance. It removes manual database and Redis URL assembly while keeping credentials out of source.

Persistence and recovery

Back up PostgreSQL and the stopped complete /paperless tree together after quiescing ingestion and draining tasks. Restore both matching artifacts into an isolated environment with a clean Redis dependency and the same stable secret key. Verify login, status, OCR/search, metadata, documents, exports, and restart before relying on the recovery.

Update and rollback

Update immutable version, source, image, and manifest pins together only after testing a coordinated backup. The proven rollback method restores matching pre-update PostgreSQL and volume artifacts before starting v3.0.4; in-place downgrade of migrated v3.0.5 state is not claimed.

Support

Template support covers package pins, Railway topology and references, validation, health, volume ownership, and documentation. Application features belong upstream; Railway account, billing, domains, databases, Redis, and volume platform incidents belong to Railway. Never post passwords, secret keys, database or Redis URLs, tokens, cookies, documents, OCR text, exports, backups, private domains, or unredacted logs.