Migrate from Render to your own servers

Move your Render web services, background workers, cron jobs and Render Postgres database to Tenkai, step by step.

Last verified on 2 November 2026 against Render's documentation. Report a mistake.

Your Render services keep their repository, their start commands and their Postgres data when they move to a cluster of servers you own. Tenkai charges your team one price, whatever the number of services.

What each part becomes

On Render On Tenkai
Web service Web application
Background worker Worker
Cron job Scheduled job
Static site Static site
Pre-deploy command Pre-deploy commands
Environment variables Variables
Environment groups Environment variables
Render Postgres PostgreSQL
Render Key Value Redis® or Valkey
Persistent disk Kept directory
Service previews Pull request previews
Custom domains Custom domains

Before you start

You need a cluster with a project on it, as projects and clusters explains. Your CI builds the image of your app, so the cluster needs no Git builds.

Move your services

  1. Build the image in your CI. Add the Dockerfile of your framework's guide, such as Rails, Django, Node.js, Next.js or PHP, and put your Build Command in it as a RUN step. Then add the workflow that publishes an image to GHCR on each push.
  2. Create the web application. Add a web application, choose Container image and enter your image, such as ghcr.io/acme/app:main. Tenkai sets PORT, so an app that listens on PORT and 0.0.0.0 answers at once.
  3. Copy the environment variables. Copy them from the service's Environment page and its environment groups. Wrap each value in single quotes, then paste the lines in the project's Variables with Edit as .env…. Leave out PORT and the URLs of your Render databases, because Tenkai sets them.
  4. Stop the writes. Stop the web services and cron jobs. Let your workers empty the queue, then stop them too.
  5. Copy Render Postgres. Add a PostgreSQL and choose From database under Initial data. Paste the database's External Database URL, followed by ?sslmode=require.
  6. Bind the databases. Bind the PostgreSQL to the web application, so it receives DATABASE_URL. For Render Key Value, add a Redis® and bind it, so the app receives REDIS_URL. The new store starts empty, so sessions and other Redis data start over.
  7. Add the workers, the pre-deploy command and the cron jobs. Each background worker becomes a worker from the same image, with its start command as the entrypoint. The pre-deploy command becomes a pre-deploy command. Each cron job becomes a scheduled job with the same schedule, because both read cron in UTC. Bind the databases to each of them.
  8. Deploy and point your domain. Deploy the web application, then the workers and scheduled jobs, and check the default address. Add each deploy hook to your workflow, as deploy from GitHub Actions explains. Then add your domain and replace the record that points to Render with the one Tenkai shows.

A service with a persistent disk

That service becomes a web application that keeps a directory at the path where your app writes. Deploy it once, then bring the files over. Pack the mount path with tar in Render's Shell, put the archive at an HTTPS address, and download it into the directory from the application's terminal.

Sources

We read these pages on 2 November 2026.

Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd.

Something wrong in this guide?

Render and Tenkai both change, so a step can go out of date. If a command fails or a step does not match what you see, tell us at [email protected]. Once you have an account, you can also choose “Report a bug” in your user menu, as the account guide explains. We fix the guide and reply to you.

Bring your apps home

Enroll a server you already rent and deploy your first application. Free for one server, no credit card.

Start for free