• Docs
  • Changelog
Sign in
Get started
    • Home
    • Your first deploy
    • Free instances
    • Platform features by plan
    • Use with coding agents
    • FAQ
    • Templates
      • Migrate from…
        • Heroku
        • Railway
    • Compute plans
    • SandboxesBeta
      • Service types
        • Which to use?
        • Static sites
        • Web services
        • Private services
        • Background workers
        • Cron jobs
        • Workflows
        • Multi-service architectures
      • Data storage
        • Render Postgres
        • Render Key Value (Redis®-compatible)
        • Persistent disks
    • How deploys work
    • Supported languages
    • Git providers (GitHub, etc.)
    • Build pipeline
    • Deploy hooks
    • Monorepo support
    • Troubleshooting deploys
      • Previewing changes
        • Single-service previews
        • Preview environments (multi-service)
      • Docker deploys
        • Overview
        • Deploy a registered image
        • Using secrets
      • Runtime
        • Native runtimes
        • Environment variables & secrets
        • Default environment variables
    • Intro to sandboxes
    • Limits & pricing
      • How to…
        • Create & configure sandboxes
        • Execute commands
        • Upload and download files
        • Manage snapshots
      • Use with…
        • Claude Managed Agents
        • Cursor Cloud Agents
        • OpenAI Agents API
      • SDK/CLI reference
        • TypeScript SDK
        • Python SDK
        • CLI commands
    • Intro to workflows
    • Tutorial
    • Limits & pricing
      • How to…
        • Define tasks
        • Define flowsNew
        • Trigger runs
        • Develop locally
      • SDK reference
        • TypeScript SDK
        • Python SDK
      • Example workflows
        • TypeScript examples
        • Python examples
    • Overview
    • Create & connect
    • Database credentials
    • Extensions
    • Version upgrades
    • Logical replication
    • Legacy instance types
      • Database recovery
        • Recovery & backups
        • High availability
      • Database performance
        • Read replicas
        • Connection pooling
        • Admin apps
        • Repacking tables
        • Troubleshooting performance
    • Regions
    • Inbound IP rules
    • Edge caching
    • WebSockets
    • TLS certificates
      • Custom domains
        • Overview
        • Cloudflare
        • Namecheap
        • Other DNS providers
      • Internal traffic
        • Private network
        • Private links
      • Outbound traffic
        • Default IP ranges
        • Dedicated IP addresses
        • Outbound bandwidth
        • Handling network changes
      • Static site config
        • Custom response headers
        • Redirects & rewrites
    • The Render Dashboard
    • SSH / Shell access
    • Projects & environments
      • Service actions
        • Scaling
        • Rollbacks
        • Maintenance mode
        • One-off jobs
      • Infrastructure as code
        • Blueprints overview
        • render.yaml reference
        • Terraform provider
    • In-dashboard metrics
    • Health checks
    • Uptime best practices
      • Logging
        • In-dashboard logs
        • Log streams (syslog/HTTPS)
      • OpenTelemetry (OTel) metrics
        • Provider setup
        • Metrics reference
      • Notifications
        • Webhooks
        • Email / Slack
    • API keys
    • MCP Server
      • Render CLI
        • Overview
        • Command reference
      • REST API
        • Overview
        • API reference
      • Third-party connections
        • OIDC support
        • Datadog
    • Workspaces, members, & roles
    • Login settings
    • Audit logs
      • Organizations
        • Overview
        • SAML SSO
    • DDoS protection
    • Platform maintenance
      • Compliance
        • Overview
        • HIPAA (US health data)
        • HIPAA best practices
        • Shared responsibility model
        • Pentest policy
    • Heroku vs Render
    • Vercel vs Render

Deploy ParadeDB on Render

Enable PostgreSQL-powered search for your other Render services.

ParadeDB is an open-source search engine built on PostgreSQL. It enables you to run full-text search and BM25 ranking directly in your database using standard SQL.

This tutorial walks through deploying ParadeDB on Render as a private service running PostgreSQL with an attached persistent disk. It requires paid resource types.

It is not currently possible to install ParadeDB directly into a Render Postgres database.

This tutorial instead deploys PostgreSQL as a private service, which doesn't support features like point-in-time recovery and high availability.

After you deploy your ParadeDB instance, you can pull your Render Postgres data into it via logical replication.

Deployment options

Quick deploy

To get up and running quickly, click the Deploy to Render button below. It uses a Blueprint to configure and deploy your ParadeDB private service with the following settings:

SettingValue

Docker image

paradedb/paradedb:latest-pg18

Region

Oregon

Starting compute plan

1c-2g

Starting disk size

10 GB

To customize any of the above (including to deploy to the same region as your existing services), instead perform a Dashboard deploy.

Deploy to Render

After your deploy completes, you can connect to your ParadeDB instance.

Dashboard deploy

To fully customize your ParadeDB deployment, do the following:

  1. In the Render Dashboard, click New > Private Service.

  2. Under Source Code, select Existing Image and provide the following Image URL:

  3. Click Connect. The rest of the service creation form appears.

  4. Select a Region and Compute Plan for your ParadeDB service.

    • Make sure to deploy to the same region as your services that will connect to ParadeDB.
    • We recommend using the 1c-2g compute plan or higher.
  5. Under Environment Variables, add the following:

    KeyValueDescription

    POSTGRES_USER

    parade_admin

    Your database superuser name.

    POSTGRES_PASSWORD

    [Set a secure password.]

    Your database superuser password.

    POSTGRES_DB

    paradedb

    The name of the default database.

  6. Expand the Advanced dropdown. Under the Disk section, click Add disk.

    • Set your disk's Mount Path to the following:

    • Set your disk's initial Size as needed for your dataset. You can increase this value later, but you can't decrease it.

  7. Click Deploy Private Service to start the initial deploy.

You're all set! Your ParadeDB instance will be up and running as soon as the deploy completes. Next, learn how to connect to your ParadeDB instance.

Connecting to your ParadeDB instance

SSH connections

Your ParadeDB instance supports shell connections from your terminal or the Render Dashboard. To get started, see SSH and Shell Access.

Starting a psql session

After connecting over SSH, start a psql session with the following command:

To test out functionality, you can create a table with mock data. Run the following commands from your psql session:

The output of your SELECT command should look like this:

Internal service connections

To connect to your ParadeDB instance from your other Render services in the same region, use a connection URL with the following format:

  • Replace {POSTGRES_PASSWORD} with the password you set for your ParadeDB instance.

  • Replace {PRIVATE_HOSTNAME} with your ParadeDB instance's hostname, available from its Connect dropdown in the Render Dashboard:

    The Connect dropdown for a ParadeDB instance in the Render Dashboard

    In the screenshot above, the hostname is paradedb18.

Set this URL as an environment variable (e.g., DATABASE_URL) in your other Render services. You can share this value across multiple services using an environment group.

Logical replication from Render Postgres

You can sync tables from a Render Postgres database to your ParadeDB instance via logical replication. Enabling logical replication requires contacting Render's support team.

  1. Follow the instructions described in Logical Replication with Render Postgres.
  2. After logical replication is enabled, follow the logical replication instructions in the ParadeDB documentation, starting with "3. Bootstrap the Schema on ParadeDB."
    • In the context of this tutorial, "publisher" refers to your managed Render Postgres database.
Deploy ParadeDB on Render
  • Deployment options
    • Quick deploy
    • Dashboard deploy
  • Connecting to your ParadeDB instance
    • SSH connections
    • Internal service connections
  • Logical replication from Render Postgres
All Systems Operational
© Render Inc. All rights reserved.