Deploy and Host NocoDB with PostgreSQL, Redis & Files on Railway

No-code tables, forms and APIs with Postgres, Redis and durable files.

About Hosting NocoDB with PostgreSQL, Redis & Files

Deploying this template creates Postgres, Redis, NocoDB in your Railway project. The application receives an HTTPS domain automatically. Database and Redis services, when included, use private networking and generated credentials. Persistent data is stored on the included volumes or object storage, so application redeploys do not discard it.

Why Deploy NocoDB with PostgreSQL, Redis & Files on Railway

Official NocoDB app with a private PostgreSQL database.
Redis is authenticated and retains its data on a volume.
Attachments survive application redeploys on /usr/app/data.
Generated session signing key and automatic public URL.

Common Use Cases

Build an internal inventory, client list or operations tracker.
Collect structured submissions with forms.
Expose spreadsheet-style data through an API.

Dependencies for NocoDB with PostgreSQL, Redis & Files

A Railway account and a plan with capacity for 3 service(s).
Included services: Postgres, Redis, NocoDB.
3 persistent volume(s), provisioned by this template.
External integrations, mail delivery and your own business data are configured after installation as needed.

First launch

Deploy the three services and wait for NocoDB to become healthy.
Open its generated domain and create the first administrator through the signup screen.
Create a base, import a spreadsheet, or connect an external database.
Configure SMTP if you need invitation and password-reset emails.

Operations

Back up PostgreSQL and the NocoDB file volume together. Redis stores cache/queue state and should remain private. Keep NC_AUTH_JWT_SECRET. If you change domains, update NC_SITE_URL and NC_PUBLIC_URL. This template includes the upstream self-hosted edition; paid vendor features and external databases are configured separately.

Images are pinned to verified upstream image digests captured on 2026-10-17. Review upstream release notes, back up persistent data and update the image deliberately when upgrading. Railway charges the deployer for running services, storage and network usage.

Support and upstream

For Railway template wiring or deployment issues, use the discussion/support link on this template page. Include service names and redacted logs; omit passwords and tokens. Application documentation:

Environment variables · NocoDB source