Search without a second system.
One Postgres for your application data, full-text search, vector retrieval, and aggregations.
Note
This blueprint is maintained by the ParadeDB team. For the official version maintained by Render, see the Render documentation and GitHub repository.
This repository deploys ParadeDB on Render with one click using a Render Blueprint.
- The official ParadeDB Docker image
- A private service that isn't exposed to the public Internet — only accessible within your Render private network
- 10 GB of persistent SSD storage via Render Disks, mounted at
/var/lib/postgresql - Auto-generated secure database password
- Auto-deploy on push — your service redeploys whenever you push changes to your fork
Use the button below to deploy ParadeDB on Render.
This will:
- Create a private service named
paradedbrunning the ParadeDB Docker image. - Attach a 10 GB persistent disk for your database data.
- Set up
POSTGRES_USER,POSTGRES_PASSWORD, andPOSTGRES_DBenvironment variables automatically.
- Click Use this template at the top of this repo to create your own copy (or fork it).
- Create a new Private Service on Render using the Existing Image runtime, pointing at
docker.io/paradedb/paradedb:latest(or your preferred tag). - Add a Disk mounted at
/var/lib/postgresqlwith at least 10 GB. - Set the following environment variables:
POSTGRES_DB— database name (e.g.paradedb)POSTGRES_USER— database user (e.g.postgres)POSTGRES_PASSWORD— let Render generate a value, or set your own strong password.
Once deployed, connect from any other service in your Render private network using the service name as the host:
psql -h paradedb -U postgres -d paradedbPrivate services aren't exposed to the public internet, so the recommended path is to SSH into the service and run psql from inside the container:
ssh srv-XXXXXXXXXXXXX@ssh.<region>.render.com
psql -U postgres -d paradedbReplace srv-XXXXXXXXXXXXX with your service ID from the Render dashboard. Make sure you've added an SSH key to your Render account first.
The default render.yaml uses the standard plan. To change it, edit the plan field in render.yaml:
plan: standard # Options: starter, standard, pro, pro plus, pro max, pro ultraThe default disk size is 10 GB. To increase it, edit the sizeGB field in render.yaml:
disk:
name: data
mountPath: /var/lib/postgresql
sizeGB: 50| Variable | Description | Default |
|---|---|---|
POSTGRES_DB |
Default database name | paradedb |
POSTGRES_USER |
Database superuser name | postgres |
POSTGRES_PASSWORD |
Database password | Auto-generated |
You can add additional Postgres environment variables (e.g. POSTGRES_INITDB_ARGS, PGDATA) in the envVars section of render.yaml or through the Render dashboard.
ParadeDB adds Elastic-quality full-text search, vector retrieval, and aggregations to Postgres with the pg_search extension. Your application data and your search engine live in one database, with no second system to deploy and nothing to sync.
- BM25 full-text search with 12+ tokenizers across 20+ languages
- Hybrid search combining BM25 and vector similarity
- Faceted search and boolean queries for filtering and complex search logic
- Zero ETL — use as your primary Postgres directly or replicate from managed databases (RDS, Supabase, Neon, etc.)
Learn more at paradedb.com.
This deployment blueprint is licensed under the MIT License.