Render.com Provider

Deploy preview environments to Render.com web services.

How it works

• Build: Previewops creates a synthetic image tag pointing at the source commit. Render pulls the code and builds from the Dockerfile in its own infrastructure.
• Deploy: creates a new Render web service (or re-deploys an existing one for the same PR). Polls until the service URL becomes healthy.
• Delete: deletes the Render web service.
• List: lists all web services in your Render account that match the prev-{owner}-{repo} name prefix.

Prerequisites

1. A Render.com account.
2. An API key and your owner ID (both available in the Render dashboard).

Step 1 — Get your Render API key

1. Go to Account Settings → API Keys → Create API Key.
2. Copy the key and store it as RENDER_API_KEY in the Previewops dashboard under Installations → your org → Credentials.

Step 2 — Get your owner ID

1. Go to Account Settings or Team Settings.
2. The owner ID is shown in the URL: https://dashboard.render.com/... or listed in the settings page. It begins with usr_ (personal) or tea_ (team).

Step 3 — Configure the repo

Add .previewops.yaml to your repository:

provider: render
providerConfig:
  ownerId: usr_xxxxxxxxxxxx  # required — from step 2
  region: oregon             # optional (default: oregon)
                             # options: oregon, ohio, virginia, frankfurt, singapore
  plan: starter              # optional (default: starter)
                             # options: starter, standard, pro, pro_plus

Step 4 — Verify

Comment /validate-previewops on any open PR. The bot will post whether the API key and owner ID are valid.

Troubleshooting