Render

Render builds and deploys web services, background workers, cron jobs and managed Postgres and Key Value stores from your Git repo, all described in one render.yaml file if you like.

What it is: Platform as a service (PaaS)
Type: Commercial product
Made by: Render Services, Inc.
License: Proprietary
Facts checked: 12 October 2026

What it is

You link a Git branch, and every push triggers a build and a deploy; you can also deploy a prebuilt Docker image. Each piece of your app is a service of a given type: a web service gets an onrender.com subdomain and must listen on 0.0.0.0 (port 10000 by default), a private service is reachable only on your private network, a background worker takes no incoming traffic and usually polls a queue, a cron job runs a command on a UTC cron schedule and is billed for how long it runs, and static sites are served from a CDN. Render also runs managed Render Postgres databases and Render Key Value instances, which run Valkey 8 when newly created and work with Redis clients.

A Blueprint is a render.yaml file in your repo that declares all of these together, with environment variables that point at each other: a web service can take DATABASE_URL from a database’s connection string. Deploys replace instances with zero downtime unless the service has a persistent disk, and if a build or pre-deploy command fails, the previous deploy keeps serving. Preview environments can spin up a copy of the stack for a pull request.

Billing combines a workspace plan (Hobby is $0, Pro $25 a month) with compute per instance, from $7 a month for 512 MB up to 12 CPUs and 96 GB. Web services, Postgres and Key Value also have Free instances for trying things out, with tight limits.

Why teams pick it

Push to deploy with zero-downtime rollouts, rollbacks and per-pull-request preview environments
One render.yaml describes services, workers, cron jobs, databases and shared environment groups, and wires their connection strings together
Managed Postgres with backups, read replicas and high availability, plus a Valkey-based Key Value store for caches and job queues
A free starting point: 750 Free instance hours per workspace each month for web services

Watch out for

Free web services spin down after 15 minutes without traffic and take about a minute to come back; Free Postgres is capped at 1 GB and expires after 30 days
Filesystems are ephemeral; adding a persistent disk turns off zero-downtime deploys for that service, and cron jobs can’t use disks at all
Autoscaling on CPU or memory needs a Pro workspace or higher, and a service tops out at 100 instances (5 on the largest plans)
Free web services can’t scale past one instance, offer SSH access or receive private network traffic

Alternatives

What all platform as a service (paas) have in common →

AWS Elastic BeanstalkAWSUpload your code and Elastic Beanstalk builds the AWS setup to run it (EC2 instances, a load balancer, an Auto Scaling group) in your own account, where you can still see and change every piece.

Azure App ServiceAzureAzure’s platform for web apps and APIs: you rent a pool of VMs called an App Service plan, and every app you put in it runs on those VMs without you managing them.

Cloud FoundryOpen sourceAn open-source PaaS you run yourself: `cf push` uploads your code, a buildpack stages it into a droplet, and Diego keeps the requested number of instances running behind the Gorouter.

DokkuOpen sourceA Heroku-like PaaS on one server of your own: `git push` to it, and Dokku builds the app with buildpacks or a Dockerfile and runs it in Docker containers behind nginx.

Fly.ioCommercialFly.io turns your Docker image into fast-booting Firecracker microVMs on its own servers in regions around the world, and routes each user to the nearest one.

Google App EngineGoogle CloudGoogle’s original platform as a service: describe your app in an `app.yaml`, run one deploy command, and Google runs and scales the instances.

HerokuCommercialThe platform that defined PaaS: `git push` your code, and Heroku builds it with a buildpack and runs it on managed containers called dynos behind its own HTTP router.

How it fits with other technologies

What Render uses

render.yaml: a web service, a worker, a nightly job, Postgres and Key Value · yaml

services:
  - type: web
    name: shop-api
    runtime: python
    plan: 0.5c-512mb
    buildCommand: pip install -r requirements.txt
    startCommand: gunicorn app:app
    healthCheckPath: /healthz
    envVars:
      - key: DATABASE_URL
        fromDatabase:
          name: shop-db
          property: connectionString
      - key: QUEUE_URL
        fromService:
          type: keyvalue
          name: shop-queue
          property: connectionString
  - type: worker
    name: shop-jobs
    runtime: python
    buildCommand: pip install -r requirements.txt
    startCommand: celery -A tasks worker
  - type: cron
    name: nightly-report
    runtime: python
    schedule: '0 3 * * *'
    buildCommand: pip install -r requirements.txt
    startCommand: python report.py
  - type: keyvalue
    name: shop-queue
    ipAllowList: []  # private network only
databases:
  - name: shop-db

See it in a real stack

No architecture uses Render yet. Drop it into the playground and wire it up yourself.Open playground →

Where it came from2019–2025

Small teams that moved to AWS often found that the cloud came with a second job. Anurag Goel, Render’s founder and CEO, told TechCrunch in 2019 that startups had to hire expensive DevOps engineers or consultants to build their infrastructure, then keep patching it and managing security and access. Render launched in April 2019 as a managed cloud that “abstracts all of that away, and automates all of it”, while aiming to be “the easiest and most flexible provider for teams to run any application in the cloud.”

In October 2019 Render won the Startup Battlefield at TechCrunch Disrupt SF; TechCrunch described its automated deployments and app management as reminiscent of Heroku. By 2021 Goel said many customers were moving over from Heroku and AWS for features such as infrastructure as code, private networking and persistent storage, and the company announced plans for a free plan for web services and databases.

In June 2023 Render raised a $50 million Series B led by Bessemer Venture Partners. In February 2025 it switched newly created Render Key Value instances from Redis to Valkey, an open-source fork of Redis 7.2.4, while existing Redis instances kept running without further version updates.

Why it’s built this way

A managed platform, not a thin layer over AWS: Goel pitched Render as an alternative to AWS, Azure and Google Cloud for teams without DevOps staff, arguing that the big clouds “were built for the 2000s, when managing infrastructure was the norm at every company.”
The whole stack as code in the repo: Blueprints put services, databases and environment groups in one render.yaml, which Goel listed among the modern features drawing customers from Heroku and AWS.
Preview environments that match production: Launched in 2020, they spin up disposable copies of the stack so developers, QA and product teams can test a change in an environment that looks like production.

Timeline

2019
Launches in April; wins the TechCrunch Disrupt SF Startup Battlefield in October
2020
Preview environments, alongside a $4.5 million funding round
2021
$20 million Series A; a free plan for web services and databases announced
2023
$50 million Series B led by Bessemer Venture Partners
2025
New Key Value instances run Valkey instead of Redis

Sources10 · facts checked 12 October 2026

Improve this page on GitHub