Skip to main content
ParadeDB Community supports single-node deployments. Use ParadeDB Enterprise when ParadeDB indexes need physical replication for high availability, failover, or read replicas that can serve ParadeDB queries. Contact us for access.
Pick the deployment path that matches where your data lives today.

Deploy on a cloud platform

Run ParadeDB Community on Railway, Render, Fly.io, DigitalOcean, or Dokku.

Install into existing Postgres

Add the pg_search extension to a Postgres instance you already control.

Deploy on Kubernetes

Run ParadeDB with CloudNativePG and plan for production operations.

Replicate from a managed primary

Keep RDS, Cloud SQL, or your primary where it is and stream changes into ParadeDB.
ParadeDB BYOC is available for managed private deployments. ParadeDB Cloud, our fully managed platform, is coming soon.

​
Cloud Platforms

ParadeDB Community is supported by several cloud platforms. These all use Docker containers, which package Postgres and pg_search together:
  • Railway — One-click deploy to Railway
  • Render — One-click deploy to Render
  • Fly.io — Deploy on Fly.io
  • DigitalOcean — Deploy on a DigitalOcean Droplet
  • Dokku — Deploy with Dokku

​
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. If a self-hosted production deployment needs failover or read replicas for ParadeDB queries, use ParadeDB Enterprise and configure 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.

​
ParadeDB Cloud

ParadeDB Cloud is fully managed ParadeDB: first-class search from Postgres, with a developer experience to match. It’s coming soon. Join the waitlist to get notified when it launches.