Postgres for Search and Analytics
This repo 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.
- Fork this repo.
- Create a new Private Service on Render.
- Connect your forked repo and use the
Dockerfileruntime. - Add a Disk mounted at
/var/lib/postgresqlwith at least 10 GB. - Set the following environment variables:
POSTGRES_USER— database user (e.g.postgres)POSTGRES_PASSWORD— a strong passwordPOSTGRES_DB— database name (e.g.paradedb)
Once deployed, connect from any other service in your Render private network:
psql -h paradedb -U postgres -d paradedbTo connect from your local machine, add an SSH key to Render, connect to the SSH endpoint, then run:
psql -U postgres paradedbThe 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 is an Elasticsearch alternative built on Postgres. It delivers Elastic-quality full-text, hybrid, and faceted search — all in pure SQL, with no separate search infrastructure to manage.
- 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.