guide

Deploy

Host your own Postbase instance — one-click deploys for Railway, DigitalOcean, Render, Fly.io, AWS, Google Cloud, Azure, Oracle Cloud, or plain Docker.

Published: September 6, 2026Updated: September 6, 2026

Postbase deploys the same way everywhere: a stateless Next.js app container (built from Dockerfile.railway) plus a managed Postgres database. Pick a provider below — each guide covers exactly what that provider’s one-click button provisions, the environment variables it sets, and how to redeploy after a code change.

  • Railway — two services (app + managed Postgres), one required secret. The fastest path to a working instance.

  • DigitalOcean — App Platform + managed database, provisioned from a single app spec.

  • Render — Blueprint (render.yaml) defines the web service + Postgres together, auto-deploys on push.

Unverified Templates

These follow the same pattern but haven’t been deployed against a live account yet on this provider — read the status note at the top of each page before relying on them in production.

  • Fly.io — the deploy button only runs fly launch; a follow-up script provisions Postgres and secrets.

  • AWS — CloudFormation: CodeBuild builds the image, deploys to App Runner + RDS.

  • Google Cloud — opens Cloud Shell; a setup script provisions Cloud SQL and deploys to Cloud Run.

  • Azure — ARM/Bicep: an ACR Task builds the image, deploys to Container Apps + Postgres Flexible Server.

  • Oracle Cloud — the least standardized path of the group; needs a GitHub token and a manual step after first deploy.

Self-Hosted

  • Docker — the base every option above builds on. Run it anywhere Docker runs, including your own server.