Deploying ParadeDB

<Note> If your application requires high availability or read replicas, you should [contact us](mailto:[email protected]) for access to ParadeDB Enterprise. For all other cases, you may deploy ParadeDB Community. </Note>

There are three ways to deploy ParadeDB:

• Cloud Platforms — deploy a ParadeDB container to Railway, Render, or DigitalOcean with minimal setup
• Self-Hosted — run ParadeDB inside Kubernetes or as an extension in your existing Postgres
• ParadeDB BYOC — a managed deployment of ParadeDB Enterprise inside your own AWS or GCP account

Cloud Platforms

ParadeDB Community is supported by several cloud platforms. These all use Docker containers, which package PostgreSQL and pg_search together:

• Railway — One-click deploy to Railway
• Render — One-click deploy to Render
• DigitalOcean — Deploy on a DigitalOcean Droplet

Self-Hosted ParadeDB

ParadeDB can be deployed as an extension inside an existing self-hosted Postgres or via our Kubernetes Helm chart, which is based on the CloudNativePG Helm chart. When self-hosting, we always recommend configuring high availability.

ParadeDB BYOC

ParadeDB BYOC (Bring Your Own Cloud) is a managed deployment of ParadeDB Enterprise inside your AWS or GCP account. Please contact sales for access.