> ## 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.

# Render

> Deploy ParadeDB on Render with one click

<Note>
  Cloud platform deployments run ParadeDB Community, which do not support high
  availability or read replicas. If these matter to you, we recommend [ParadeDB
  Enterprise](/deploy/enterprise) deployed via
  [Kubernetes](/deploy/self-hosted/kubernetes) or [BYOC](/deploy/byoc).
</Note>

[Render](https://render.com) is a cloud platform that makes it easy to deploy and manage applications. The
[ParadeDB Render Blueprint](https://github.com/paradedb/render-blueprint) provides a one-click deployment
that runs ParadeDB Community as a [private service](https://render.com/docs/private-services) with persistent
SSD storage.

You can either follow [Render's official ParadeDB deployment guide](https://render.com/docs/deploy-paradedb)
or use the steps below.

## One-Click Deploy

The fastest way to get started is to click the button below, which deploys ParadeDB to your Render account.

[![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=https://github.com/paradedb/render-blueprint)

This will:

1. Create a private service named `paradedb` running the [official ParadeDB Docker image](https://hub.docker.com/r/paradedb/paradedb).
2. Attach a 10 GB persistent disk for your database data, mounted at `/var/lib/postgresql`.
3. Set up `POSTGRES_USER`, `POSTGRES_PASSWORD`, and `POSTGRES_DB` environment variables automatically.

## Manual Setup

If you prefer to configure the deployment yourself:

1. Click **Use this template** at the top of the [render-blueprint](https://github.com/paradedb/render-blueprint) repository to create your own copy (or fork it).
2. 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](https://hub.docker.com/r/paradedb/paradedb/tags)).
3. Attach a **Disk** of at least 10 GB mounted at `/var/lib/postgresql`.
4. 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:

```bash theme={null}
psql -h paradedb -U postgres -d paradedb
```

### From your local machine

Since the service isn't exposed publicly, [SSH into the service](https://render.com/docs/ssh) and run `psql` from inside the container:

```bash theme={null}
ssh srv-XXXXXXXXXXXXX@ssh.<region>.render.com
psql -U postgres -d paradedb
```

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