Deploy and Host self hosted Paperless-ngx Custom Fields (Open-Source Document Management with Custom Fields) on Railway

This template runs Paperless-ngx 3.3.0 with Postgres, Redis and a volume for your scans, so typed fields like Amount and Due Date stay filterable, workflow-aware and API-queryable. Built for invoice tracking.

About Hosting Paperless-ngx Custom Fields open-source software on Railway (self hosted Paperless-ngx custom fields template)

Your invoices, scans and the custom field values attached to them stay in your own Postgres database and on the template's volume at /usr/src/paperless/data. Railway handles TLS and the domain; you still click Save on the document page.

Why Deploy Paperless-ngx Custom Fields, the DocuWare alternative on Railway (Railway Free Trial)

DocuWare rents you index fields per seat and keeps your documents in its cloud. Here custom fields sit in your own Postgres, cost nothing per user, and come back out over the API. Railway's $5 trial covers the first look, and you can walk away with your data.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Paperless-ngx Custom Fields on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Railway vs Other Hosting Providers and VPS for Paperless-ngx Custom Fields self hosting

Railway runs the same upstream image with Postgres-backed fields, minus the server admin.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	Template deploy, managed domain, env wiring done	A Droplet you patch, secure and back up yourself
AWS	Small monthly spend for a personal archive, OCR runs as-is	EC2, RDS and S3 with IAM and alarms to set up
Hetzner	Dedicated vCPU feel for OCR bursts, no hardening	Cheap hardware, but you own Compose, TLS and snapshots

Keep the Hetzner box if you already run one; otherwise Railway gets you to a saved Due Date field faster.

Common Use Cases for hosted Paperless-ngx Custom Fields

Custom fields turn loose paperwork into rows you can filter, query and automate. These setups pay off first:

Invoice number plus amount: Give every scanned bill a Text field for the invoice number and a Monetary field for the total, so EUR12.30 stays a real number instead of living inside a tag name.
Contract end dates: A Date field feeds scheduled workflows that fire before renewal, using a day offset you set on the trigger.
Payment status: A Select field with options like unpaid, paid and disputed replaces a pile of overlapping status tags.
Receipt to invoice links: A Document Link field ties a receipt to its invoice and creates the reverse link automatically.
Bookkeeping exports: Pull Monetary values through the API into a spreadsheet at month end without retyping a single amount.

Dependencies for Paperless-ngx Custom Fields Docker hosted on Railway

Custom fields do not add a service. Persistent files sit on one volume mounted at /usr/src/paperless/data for the data, media and consume directories.

Deployment Dependencies for Managed Paperless-ngx Custom Fields Service (Document Management)

Set PAPERLESS_DBENGINE=postgresql plus PAPERLESS_DBHOST, PAPERLESS_DBPORT, PAPERLESS_DBNAME, PAPERLESS_DBUSER and PAPERLESS_DBPASS so the app reaches Postgres. Point PAPERLESS_REDIS at the Redis service.

Implementation Details for Paperless-ngx Custom Fields (Using Paperless-ngx official docker image)

The image runs migrations and starts the web and worker processes itself. Keep the volume attached; removing it drops your fields along with the documents.

How does Paperless-ngx Custom Fields compare against other document archives with structured metadata

Paperless-ngx vs DocuWare (DocuWare Alternative)

Where Paperless-ngx wins: custom fields ship in the free GPL-3.0 build, so Invoice Number and Amount cost nothing extra.
Where DocuWare wins: commercial support contracts and a long record in regulated offices.
The trade: DocuWare sells seats and modules; you own backups, the OCR queue and upgrades.

Paperless-ngx vs Papermerge (Papermerge Alternative)

Model: Papermerge is folder-first, like a desktop tree. Paperless-ngx is metadata-first, and custom fields carry the structure.
Typed values: Text, Boolean, Date, URL, Integer, Number, Monetary, Document Link and Select ship built in, Monetary with an ISO 4217 code.
Where Papermerge wins: the tree view is simpler for anyone who never wants to build a query.

Paperless-ngx vs Mayan EDMS (Mayan EDMS Alternative)

Weight: Mayan is a heavier enterprise EDMS. Paperless-ngx is the app, Postgres and Redis; custom fields add no service.
Setup: Mayan needs real configuration first. Paperless-ngx is Manage, Custom Fields, new field, done.
Where Mayan wins: deeper lifecycle and retention tooling, which Paperless-ngx does not attempt.

Paperless-ngx vs Google Drive (Google Drive Alternative)

Typed fields: Drive stores files. Paperless-ngx attaches typed fields, and field values are included in search.
Access control: custom fields have their own add, edit, delete and view permissions, so a bookkeeper sees amounts without the archive.
Where Drive wins: sharing and sync are frictionless, and your accountant likely has a folder there already.

How to use Paperless-ngx Custom Fields (the OSS document management system)?

Open your Railway Paperless-ngx domain and log in with the generated admin password from Railway variables.
Go to Manage then Custom Fields and create Invoice Number (Text), Amount (Monetary), Due Date (Date). Types are permanent.
Open a document, pick the fields from the Custom Fields menu, fill them, and click Save.
Filter the document list by Due Date to confirm the values stick.
Grab an API token, URL-encode the query, then:

curl -H "Authorization: Token $TOKEN" "https://your-domain/api/documents/?custom_field_query=%5B%22Due%20Date%22%2C%20%22range%22%2C%20%5B%222026-11-01%22%2C%222026-11-30%22%5D%5D"

The response lists matching documents.

How to self host Paperless-ngx Custom Fields on other VPS Services (Paperless-ngx self hosting guide)

Clone the Repository

Pull the official repo and check out the release with the custom field types you need.

git clone https://github.com/paperless-ngx/paperless-ngx.git
git checkout v3.3.0

Install Dependencies

Install Docker with the Compose plugin. Postgres and Redis come from the compose stack, and Tesseract ships in the image.

Configure Environment Variables

Copy the env example and set the secret key, admin login, public URL, database and Redis. PAPERLESS_URL must match your domain or logins fail CSRF.

PAPERLESS_SECRET_KEY=your-generated-key
PAPERLESS_ADMIN_USER=admin
PAPERLESS_URL=https://your-domain
PAPERLESS_REDIS=redis://broker:6379

Start the Paperless-ngx Custom Fields Application

Bring it up, confirm /accounts/login/ returns 200, then create fields under Manage. Values sit in Postgres, so nothing else needs deploying.

docker compose up -d

Railway runs that whole stack for you, with Postgres, Redis, TLS and the public domain already wired.

Official Pricing of Paperless-ngx Custom Fields (Paperless-ngx pricing)

Paperless-ngx is free software under GPL-3.0, and custom fields are part of the core app, not a paid add-on. The project sells no official cloud tier, so your only cost is infrastructure. Third-party hosts exist and set their own prices.

Paperless-ngx Custom Fields cloud vs self hosted comparison (Pricing, features, costs, and more)

There's no official Paperless-ngx cloud, so the real choice is a managed third-party host or your own box. Custom fields behave the same either way: they're Postgres rows, not a paid add-on.

Monthly cost of self hosting Paperless-ngx Custom Fields on Railway

Railway bills usage, not seats. A small personal archive running this template lands around $5-15/mo, and volume storage grows as documents pile up. The $5 trial covers the first stretch, and the software itself is GPL-3.0, so there are no license or per-field fees.

System Requirements for Hosting Paperless-ngx Custom Fields on a VPS

Plan on 2 GB RAM minimum for comfort, more if you OCR big batches. It runs on a Raspberry Pi, but OCR drags on weak CPUs. Postgres and Redis ship with this template, so custom fields need no extra service.

Frequently Asked Questions (FAQs)

Can I change a field type later?

No. The type is fixed once set, so delete the field, create a new one with the right type, and re-enter values, clicking Save on each document.

What format does Monetary use?

An ISO 4217 code plus a number with exactly two decimals, no space: EUR12.30. There's no conversion, so keep one currency per field.

Can workflows fill fields automatically?

Yes. A workflow action can assign a custom field, optionally with a value, and a scheduled trigger can run off a Date field with a day offset.

Can I set fields on upload via API?

Yes. post_document accepts custom_fields as an array of field ids or an object of id to value, and returns a task UUID right away.

Are custom fields searchable?

Yes. Field values and notes are in the search index, the document list filters on them, and custom_field_query handles scripted lookups such as ["Due Date", "range", ["2026-11-01", "2026-11-30"]].

Do custom fields need an extra service?

No. They live in Postgres next to your documents, so the template's Postgres and Redis cover them. CustomField objects have their own view and edit permissions.