Pilots vs Render, Always-On Instances or Machines That Sleep
Render keeps instances running and manages your Postgres. Pilots freezes what is idle and wakes it whole.
Render is what a lot of teams moved to when they wanted a platform that was predictable, with services, a managed database and a price per instance. Pilots starts from a different assumption, that most machines are idle most of the time, and builds everything else on that.
Everything said about Render here was read from its own pages in September 2026, and links to the page it came from.
What the two agree on
- A push deploys. Both build from a connected repository, and both run a prebuilt image when you have one.
- A deploy is gated. For a service without a disk, both bring the new version up beside the old one and switch over only when it is healthy.
- Agents are first-class. Both ship a CLI and an official MCP server.
- Rollback is one step. Both put a previous release back in front of the same address.
A container or a microVM
Render runs a service as a container. Render describes its services as containers, a reasonable fit for code your agents generate against your own tools and not designed for code submitted by untrusted users.
Pilots runs everything as a microVM, a small virtual machine with a kernel of its own, and those machines are what Pilots orchestrates. The isolation that is safe for untrusted code is the isolation your production service gets, because the two are the same kind of machine.
Whether a paid service sleeps
On Render, sleeping is a property of the free plan. A free web service spins down after fifteen minutes without traffic, takes about a minute to come back, shows a loading page while it does, and loses the changes to its local filesystem. A paid web service keeps at least one instance running, and autoscaling works between a minimum and a maximum you set.
On Pilots, sleeping is how every machine behaves. A replica with no traffic suspends, uses no compute while it sleeps, and the next request wakes it with its memory and its processes as they were. The request is held while that happens, so a visitor sees a slower first response and never a waiting page. You keep a replica resident only when something needs it to be, such as a queue consumer nothing will wake.
Sandboxes
Render offers sandboxes for running untrusted code, which its product page describes as isolated containers. They are in early access as of this writing. One of their two snapshot types captures memory and processor state as well as the filesystem, which is the same idea Pilots builds on.
On Pilots a sandbox is not a separate product. It is a machine, the same object a production replica is, with a permanent URL of its own. pilot promote turns a sandbox running your image into a service in one call, with nothing rebuilt and the URL unchanged.
Where a deploy starts
Render deploys from a repository or an image. Its CLI creates a service from one or the other.
pilot deploy takes the directory you are standing in, committed or not. That matters most to an agent, which has usually just written the code and has nowhere to push it yet.
What a sandbox is for
A Pilots sandbox is not only a place to run a snippet. It is a small computer running Linux with a kernel of its own and root access, so anything that runs on a server runs in it.
Point a fleet of them at your product and each one drives a real browser through it the way a person would, files what it found, and adds to the load the product is being measured under. Hand one to an agent with its permission prompts off, and code that would be unsafe on your laptop is safe to run, because the machine is disposable.
What Pilots is built for
- You want to run code you do not trust, or an agent you have not supervised, somewhere it can do no harm.
- Most of what you run is idle most of the time, such as internal tools, staging copies, side projects and per-customer instances.
- You want scale to zero on a production service, and a wake that resumes memory instead of booting.
- You need disposable computers, for agents or for anything else, and want the same platform to host what gets built.
- You want one command between the sandbox and production.
- You want to deploy a directory, not a repository.
Both platforms limit a service with a disk to one instance. On Render, adding a disk also turns off zero-downtime deploys. Pilots holds requests during the swap rather than dropping them.
Questions people ask
Does Render use containers or virtual machines?
Containers. Render describes its services as containers and its sandboxes as isolated containers. Pilots runs sandboxes and services alike as microVMs.
Does Render scale to zero?
Yes, on the free plan only. A free web service takes about a minute to come back, and a paid one keeps an instance running. Pilots suspends every idle machine and wakes it with its memory intact.
Does Render have sandboxes for AI agents?
Yes, in early access as of September 2026, for selected workspaces. On Pilots a sandbox is the same machine a production service runs on.
Can I run a production database on Pilots?
Yes. pilot add postgres writes the configuration, the volume, a daily snapshot schedule and write-ahead log archiving into your project. You operate the database.
Every comparison, or install the CLI and hold Pilots against your own app.