Documentation Index
Fetch the complete documentation index at: https://docs.paradedb.com/llms.txt
Use this file to discover all available pages before exploring further.
Cloud platform deployments run ParadeDB Community, which does not include WAL
support. This makes them suitable for hobby, development, and staging
environments. For production, we recommend ParadeDB
Enterprise deployed via
Kubernetes or BYOC.
One-Click Deploy
The fastest way to get started is to click the button below, which deploys ParadeDB to your Render account.- Create a private service named
paradedbrunning the official ParadeDB Docker image. - Attach a 10 GB persistent disk for your database data, mounted at
/var/lib/postgresql. - Set up
POSTGRES_USER,POSTGRES_PASSWORD, andPOSTGRES_DBenvironment variables automatically.
Manual Setup
If you prefer to configure the deployment yourself:- Click Use this template at the top of the render-blueprint repository to create your own copy (or fork it).
- In the Render dashboard, create a new Private Service using the Existing Image runtime, pointing at
docker.io/paradedb/paradedb:latest(or your preferred tag). - Attach a Disk of at least 10 GB mounted at
/var/lib/postgresql. - Set the following environment variables:
| Variable | Description | Default |
|---|---|---|
POSTGRES_USER | Database user | postgres |
POSTGRES_PASSWORD | Database password | Auto-generated |
POSTGRES_DB | Database name | paradedb |
Connecting to ParadeDB
ParadeDB runs as a private service on Render, which means it is not exposed to the public internet.From another Render service
Connect from any other service in your Render private network using the service name as the host:From your local machine
Since the service isn’t exposed publicly, SSH into the service and runpsql from inside the container:
srv-XXXXXXXXXXXXX with your service ID from the Render dashboard, and make sure you’ve added an SSH key to your Render account first.