Skip to main content
There are two ways to deploy ParadeDB: self-hosting ParadeDB or using ParadeDB BYOC (Bring Your Own Cloud).

Self-Hosted ParadeDB

For hobby, development, or staging environments, ParadeDB Community can be deployed as a Docker image, inside Kubernetes, or as an extension inside an existing self-hosted Postgres. For production environments, we recommend deploying the ParadeDB Enterprise binary inside Kubernetes. This unlocks support for logical replication and high availability, which must be configured separately.
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.

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.