Pilots vs Vercel, Functions or a Server That Sleeps
Vercel turns an app into functions behind a global network. Pilots keeps it a server, and lets the server sleep.
Vercel set the standard for what deploying a frontend feels like. You push, get a preview URL, merge, and it is live everywhere. Pilots shares the ambition and makes a different bet about what is being deployed. Vercel runs an app as functions. Pilots runs it as a server.
Everything said about Vercel here was read from its own documentation in September 2026, and links to the page it came from.
What the two agree on
- No configuration to start. Both detect the framework in a directory and build it.
- The CLI deploys without a repository. `vercel deploy` and
pilot deployboth work from a directory. - You pay for what runs. Both stop charging for compute when there is no traffic.
- Agents are first-class. Both ship a CLI and an official MCP server.
- Rollback needs no rebuild. Both switch which release answers.
Two runtimes or one
Vercel runs an app and a sandbox on two different things. An app becomes functions, and several invocations can share one instance. A sandbox is a microVM, which is a separate product.
Pilots runs both as the same microVM, and those machines are what it orchestrates. A production service gets a kernel of its own, exactly as a sandbox does.
A function or a server
On Vercel your code runs as functions, and that includes a container image, in beta, which Vercel runs as a stateless function. A function has a maximum duration and a limit on the size of a request and a response. Its filesystem is read-only apart from temporary space, so state lives in a service beside it. Vercel Functions can serve WebSockets, in beta, and a connection closes when the function reaches its maximum duration.
On Pilots your code runs as a process in a machine, the way it does on your laptop. It has no maximum duration on a request or a connection, it writes to a disk, and it serves a large upload, because it is a server. It still costs nothing for compute while idle, because the machine is frozen with its memory when the traffic stops and thawed when it returns.
The sandbox
Vercel Sandbox runs agent code in microVMs, the same technology Pilots uses. Vercel is clear about its purpose. Sandboxes are not designed to run continuously and are not for permanent hosting. A session has a maximum duration. A sandbox persists across sessions by default, and what persists is the filesystem, with processes started again by a hook.
On Pilots the sandbox and the production service are the same kind of machine. A sandbox keeps its memory and its running processes across sleep and has no session ceiling. pilot promote turns a sandbox running your image into a production service, in one call and at the same URL.
Which frameworks are at home
Vercel maintains Next.js, and Next.js is the one framework that supports every feature in Vercel's own support table. Other frameworks run as Vercel Functions too, within the same limits.
Pilots runs the server the framework already ships. A Rails app, a Django app, a Go binary and a Next.js app all deploy the same way, as a process listening on a port. WebJs, its sibling framework, has no build step to wait for.
What a sandbox is for
A Pilots sandbox is a small computer with no ceiling on how long it runs. It has a kernel of its own and root access, so whatever you would install on a Linux server you install in it.
Hand one to an agent with its permission prompts switched off and unsafe code is no longer a risk to your laptop, only to a machine you can throw away. Start a fleet of them and each can drive a real browser through your product the way a person would, report what it found, and put the product under the load of every one of them at once.
What Pilots is built for
- You want a computer for the job and not a function, for as long as the job takes.
- Your app is a server, with requests and connections that have no maximum duration, large uploads and a disk.
- You want to run the database beside the app, on the same private network.
- You want a sandbox and a production service to be the same kind of machine.
- You want to move a framework you already run and keep its disk and its long requests.
Questions people ask
Does Vercel use microVMs?
Yes, for sandboxes. Vercel Sandbox runs each sandbox in a microVM, and an app deployed to Vercel runs as functions. Pilots runs both as microVMs.
Can I run a long-lived server on Vercel?
No. Vercel runs code as functions with a maximum duration, and documents its sandboxes as not for permanent hosting. Pilots runs an ordinary server process with no maximum duration.
Does Vercel Sandbox keep running processes between sessions?
No. It keeps the filesystem, and processes are started again by a hook. A Pilots sandbox is suspended with its memory, so its processes are still running when it wakes.
Can I deploy a Next.js app on Pilots?
Yes. Pilots detects Next.js and runs its own server, and an optional adapter builds it as a standalone server to keep the image small.
Every comparison, or install the CLI and hold Pilots against your own app.