Deploying ParadeDB

<Note> Running ParadeDB Community in a production application that serves paying customers is discouraged.

This is because ParadeDB Community does not have write-ahead log (WAL) support. Without WALs, data can be lost or corrupted if the server crashes or restarts, which would necessitate a reindex and incur downtime for your application. For more details, see guarantees.

When you are ready to deploy in ParadeDB to production, contact us for access to ParadeDB Enterprise, which has WAL support.

</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

For hobby, development, or staging environments, ParadeDB Community can be deployed to cloud platforms with minimal setup. 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.