Deploy and Host Browser PDF Privacy Desk with BentoPDF on Railway

A protected browser PDF desk without a server-side document archive.

About Hosting Browser PDF Privacy Desk with BentoPDF

Teams preferring browser-side PDF tasks for small document workflows.

Enter the operator gateway, choose a PDF operation and open a local sample file. Download the result to your own document store. Use this separate desk when you do not need the server-side Stirling processing stack.

Included services and storage

Service	Persistent storage	Public access
App	None; container state is disposable	Private network only
Gateway	None; container state is disposable	HTTPS domain

First deployment

Review required inputs in the deploy form and supply your own administrator email where requested.
Deploy the services and wait for the application and any database migrations to finish.
Open the generated HTTPS domain and follow the workflow above.
For the first browser prompt use username operator and the generated Gateway.GATEWAY_PASSWORD from Railway variables. App-specific accounts, where present, remain separate. The App service has no public domain.

Why Deploy Browser PDF Privacy Desk with BentoPDF 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 a small PDF set in the browser.
Reorder pages before delivery.
Perform local PDF transformations.

Dependencies for Browser PDF Privacy Desk with BentoPDF

Upstream application and its documentation. The upstream authors own the application and its license. This recipe does not claim application authorship or official endorsement.
Caddy gateway using generated Basic authentication and WebSocket-capable reverse proxying.
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

This serves the upstream client application; no shared document storage, account system or server conversion API is added. Large PDFs depend on the client device memory. Review the upstream tool behavior and optional integrations before using sensitive material.

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

Review the required inputs and hosting resource costs before deploying.

Related deployment recipes

FastAPI REST Web Starter — Python REST API starter with HTTPS and a pinned upstream source snapshot.
Django PostgreSQL Web Starter — Django LTS starter with Postgres, generated secrets and DEBUG disabled.
Meilisearch with Persistent Indexes — Search API with persistent indexes, production auth and a generated key.

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.