Skip to main content
ParadeDB home page
v0.18.11
Search...
⌘K
Documentation
Docs v2 (beta)
Deploy
Changelog
Deploy
Overview
ParadeDB Self-Hosted
ParadeDB BYOC
ParadeDB Enterprise
Upgrading ParadeDB
Installing Third Party Extensions
Continuous Integration
Community
Blog
paradedb/paradedb
ParadeDB home page
v0.18.11
Search...
⌘K
Community
Blog
paradedb/paradedb
paradedb/paradedb
Search...
Navigation
Deploy
Overview
On this page
Self-Hosted ParadeDB
ParadeDB BYOC
Deploy
Overview
There are two ways to deploy ParadeDB:
self-hosting ParadeDB
or using
ParadeDB BYOC
(Bring Your Own Cloud).
Self-Hosted ParadeDB
For hobby 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.
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.
Was this page helpful?
Yes
No
Kubernetes
⌘I
Assistant
Responses are generated using AI and may contain mistakes.