Skip to content
/ render-blueprint Public template

paradedb/render-blueprint

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 

Repository files navigation

ParadeDB

Postgres for Search and Analytics

WebsiteDocsCommunityBlogChangelog


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.

What You Get

  • 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

Deployment

One Click

Use the button below to deploy ParadeDB on Render.

Deploy to Render

This will:

  1. Create a private service named paradedb running the ParadeDB Docker image.
  2. Attach a 10 GB persistent disk for your database data.
  3. Set up POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB environment variables automatically.

Manual

  1. Click Use this template at the top of this repo to create your own copy (or fork it).
  2. Create a new Private Service on Render using the Existing Image runtime, pointing at docker.io/paradedb/paradedb:latest (or your preferred tag).
  3. Add a Disk mounted at /var/lib/postgresql with at least 10 GB.
  4. 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.

Connecting

From another Render service

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 paradedb

From your local machine

Private 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 paradedb

Replace srv-XXXXXXXXXXXXX with your service ID from the Render dashboard. Make sure you've added an SSH key to your Render account first.

Configuration

Render Plan

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 ultra

Disk Size

The 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

Environment Variables

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.

What is ParadeDB?

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.

License

This deployment blueprint is licensed under the MIT License.

About

Render Blueprint for ParadeDB. Deploy ParadeDB to Render with a single click!

Topics

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Sponsor this project

 

Contributors