---
title: Deploy Kaeso on Render
description: "Run Kaeso on Render from the blueprint in the repository, with a public edge, a private gateway and console, Render Postgres and Key Value. Step by step, from the master key to your own domain."
url: https://kaeso.app/articles/deploy-kaeso-on-render
markdown: https://kaeso.app/articles/deploy-kaeso-on-render.md
language: en
alternates:
  de: https://kaeso.app/de/articles/deploy-kaeso-on-render.md
  zh-CN: https://kaeso.app/zh-CN/articles/deploy-kaeso-on-render.md
published: 2026-11-11
authors:
  - Kaeso Team
tags:
  - self-hosting
  - render
  - deployment
  - guide
image: https://kaeso.app/articles/deploy-kaeso-on-render/cover.jpg
index: https://kaeso.app/llms.txt
---

# Deploy Kaeso on Render

Run Kaeso on Render from the blueprint in the repository, with a public edge, a private gateway and console, Render Postgres and Key Value. Step by step, from the master key to your own domain.

> Every page, article and docs page of Kaeso is listed in https://kaeso.app/llms.txt.

- Published: 11 November 2026
- Reading time: 3 min
- Author: Kaeso Team

Render reads a blueprint, `render.yaml`, and creates every service in it. Kaeso's repository has one at its root, pinned to the latest release. It runs Kaeso on five Render resources, with only one of them public.

## What you get

| Service | Type | Image | Plan |
| --- | --- | --- | --- |
| `kaeso-edge` | Web service | The console image, running `kaeso-edge` | 0.5 CPU, 512 MB |
| `kaeso-gateway` | Private service | The gateway image | 2 CPU, 4 GB |
| `kaeso-console` | Private service | The console image | 0.5 CPU, 512 MB |
| `kaeso-valkey` | Key Value | Render's, with `noeviction` | 256 MB |
| `kaeso-postgres` | Postgres | Render's, version 18 | 1 CPU, 2 GB |

Only the edge is public. It sends the APIs, the MCP server and its sign-in to the gateway and every other path to the console, over Render's private network. Postgres and Key Value have an empty `ipAllowList`, so only the services reach them. Every service has `autoDeployTrigger: off`: Render never redeploys on a commit, and your install stays on the release you chose.

Change a plan or the region in the blueprint before you create it; Render keeps them from then on.

## Before you start

You need a Render account, an SMTP server for Kaeso's emails, and Docker on your computer to generate the master key:

```bash
docker run --rm ghcr.io/logicplanes/kaeso-gateway:0.6.0 master-key generate
```

Keep the key in a password manager. Kaeso encrypts provider keys with it, so a database backup can't be read without it.

For request logs, you also need a ClickHouse, such as ClickHouse Cloud. Without one, request logs are off, and usage, limits and budgets work the same.

## Deploy

1. Open [Deploy to Render](https://render.com/deploy?repo=https://github.com/logicplanes/kaeso/tree/prod). It creates a **Blueprint** from the repository `logicplanes/kaeso` on the branch `prod`, which holds the latest release.
2. Fill in the values the blueprint asks for:

   | Value | What to enter |
   | --- | --- |
   | `KAESO_PUBLIC_URL` | `https://` and the edge's address, such as `https://kaeso-edge.onrender.com` |
   | `KAESO_MASTER_KEYS` | The master key |
   | `KAESO_SETUP_EMAIL` | Your address; the gateway emails the setup link there |
   | `KAESO_SMTP_HOST`, `KAESO_SMTP_USER`, `KAESO_SMTP_PASSWORD`, `KAESO_SMTP_FROM` | Your SMTP server |
   | `KAESO_CLICKHOUSE_URL` | A ClickHouse HTTP URL with user and password, or empty |

3. Apply the blueprint, and wait until every service is live.
4. Open the one-time setup link the gateway emailed to `KAESO_SETUP_EMAIL`, and create the first user. The gateway sends a new link at every start until a user exists.

From there, add a provider key in the console, create a project key, and send a first request to `https://kaeso-edge.onrender.com/v1`.

## Your own domain

Add the domain to `kaeso-edge` under **Settings**, and point its DNS record where Render says. Then set `KAESO_PUBLIC_URL` on `kaeso-gateway` to `https://` and the domain, and redeploy the gateway.

## How client addresses stay honest

Kaeso's limits, logs and audit entries record the client's address, so it must not be something a caller can make up. Public traffic reaches Cloudflare before Render, and Render appends to the caller's `X-Forwarded-For` rather than replacing it. The edge therefore reads `CF-Connecting-IP`, which Cloudflare overwrites, and sends the gateway one address. The gateway trusts only the edge.

The gateway listens on port 8080 and keeps its metrics on its loopback address, because Render treats the one port a private service binds on every interface as its port.

## Update and roll back

A release changes the image tags in `render.yaml` on `prod`. On the blueprint's page, **Manual sync** redeploys the services on the new release, and the gateway migrates the database at start. To roll back, use **Rollback** on each service to its previous deploy. Migrations only move forward, so a rollback past a release whose migrations the earlier version can't run stays where it is, as on any install.

## What was tested

On 2026-11-07, during the release candidates, the blueprint was created from an empty Render project in Frankfurt. It created all five resources, the setup email arrived, the health and readiness checks passed, and a streamed completion reached the console's request log. The test also found that Render appends to `X-Forwarded-For`, which led to the `CF-Connecting-IP` change above; that change passes the local edge test and the configuration check, but hasn't been retested live.

## Next steps

- [Render in the docs](https://docs.kaeso.app/self-hosting/platforms/render), with every detail of the blueprint.
- [Backups and master keys](https://docs.kaeso.app/self-hosting/backups): back up Render Postgres and keep the master key outside Render.
- [Where to run Kaeso](https://kaeso.app/articles/where-to-run-kaeso): how Render compares with the other platforms.

By Kaeso Team

## More articles

- [Where to run Kaeso, from one server to a managed cloud](https://kaeso.app/articles/where-to-run-kaeso.md): Kaeso 0.6.0 runs on your own server with one command, and on ten platforms from templates in the repository. A guide to the four kinds of path, what each one keeps the same, and which to choose.
- [Deploy Kaeso on Railway](https://kaeso.app/articles/deploy-kaeso-on-railway.md): Run Kaeso on Railway with the Deploy on Railway button, which generates the master key for you, or from the infrastructure file with the Railway CLI. Five services, one public edge, Railway Postgres and Redis.

[See all articles](https://kaeso.app/articles.md)

## Own the gateway. Own the record

```bash
curl -fsSL https://kaeso.app/install.sh | sh
```

[Install Kaeso](https://docs.kaeso.app/self-hosting/installation) · [Open the live demo](https://demo.kaeso.app)
