---
title: Deploying ParadeDB
description: Explore the different ways to deploy ParadeDB into production
canonical: https://docs.paradedb.com/deploy/overview
---

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

There are three ways to deploy ParadeDB:

- **[Cloud Platforms](#cloud-platforms)** — deploy a ParadeDB container to Railway, Render, or DigitalOcean with minimal setup
- **[Self-Hosted](#self-hosted-paradedb)** — run ParadeDB inside Kubernetes or as an extension in your existing Postgres
- **[ParadeDB BYOC](#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](/deploy/cloud-platforms/railway) — One-click deploy to Railway
- [Render](/deploy/cloud-platforms/render) — One-click deploy to Render
- [DigitalOcean](/deploy/cloud-platforms/digitalocean) — Deploy on a DigitalOcean Droplet

## Self-Hosted ParadeDB

ParadeDB can be deployed as an [extension](/deploy/self-hosted/extension) inside an existing self-hosted Postgres or via our [Kubernetes Helm chart](/deploy/self-hosted/kubernetes), which is based on the [CloudNativePG](https://cloudnative-pg.io/) Helm chart. When self-hosting, we always recommend configuring [high availability](/deploy/self-hosted/high-availability).

## ParadeDB BYOC

[ParadeDB BYOC (Bring Your Own Cloud)](/deploy/byoc) is a managed deployment of ParadeDB Enterprise inside your AWS or GCP account. Please [contact sales](mailto:sales@paradedb.com) for access.
