Vercel

Vercel was founded in 2015 by Guillermo Rauch, a programmer who later also created Next.js, the most widely used framework for building modern websites. The company was originally called ZEIT, but renamed itself Vercel in 2020 and kept the triangular logo. Today millions of sites run through it, from small startup projects to products from global brands.

In practice it works like this. You write your site's code, push it to a repository like GitHub, and Vercel builds it on its own and puts it on stage, meaning it publishes it on the internet, spread across servers around the world so it opens fast both from Sofia and from Tokyo. With every change you get a separate rehearsal version with a unique link, before you hit the button for the real release in front of an audience. No one on the team touches a physical server, or watches over disks and power supplies.

The reason Vercel exists is simple: most people who build websites don't want to also be infrastructure technicians. It takes on all the heavy technical work backstage, while the developer stays focused only on what the viewer sees.

What's new for 2026 is Vercel Agent. It sits in the control panel of every project, watches what happens on the live site, and can propose or make a fix on its own while the site is running. The code it generates first goes through a separate, isolated rehearsal called Vercel Sandbox before reaching the real stage, and every one of its bigger actions gets a triple signature: the agent, the person who requested the change, and the person who approved it. For now the service is in a testing phase for paid team plans.

For the first time, a technician who isn't human steps onto the stage - while the show is already running in front of an audience.

Agents pile up storage, too. On October 9, 2026 Vercel announced that all teams on its paid Pro plan will start paying for the space their deployments and functions take up, at $0.10 per GB-month; each team learns by email when billing starts for it. A deployment is every uploaded version of the site, including those preview versions from above. Vercel states the reason plainly: coding agents have sped up the work, versions have multiplied and the stored history has grown. So the retention window becomes 30 days. Starting October 23, 2026, deployments older than 30 days get deleted, unless the team opts out of the change in its retention settings before that date, and a deleted deployment can't be used to roll back. If you roll your site back to versions older than a month, you decide by October 23.

The number behind that change came at Ship 2026, on October 15: by Vercel's data, deployments launched by agents are up 28 times over 12 months. The same recap announced Python as generally available, the Daemons background workers in public beta, and Drives, a disk that survives between agent runs, generally available for Sandbox.

On October 28, 2026 Vercel also released Vercel CI in beta, on all plans. CI is the automatic check of the code on every upload. Most such systems run the whole process on every push, while Vercel CI runs only what the change affects. There is no YAML file to maintain, the setup lives in turbo.json, and Remote Cache is on by default. By Vercel's figures, at their own sites the path from push to a green CI is 2 to 6 times faster. A price for after the beta has not been announced.

Here's where the craft shows

I come from the event business, so I look at Vercel as the crew backstage that no viewer sees, but without which nothing lights up and nothing makes a sound. Hosting has always been that invisible, boring job that has to be perfect precisely because no one is supposed to notice it.

That's why the news about the agent makes me stop and think twice. It's one thing to have a technician swap a cable backstage before the concert. It's a whole other thing to let someone, even someone very good, touch the soloist's microphone while the song is already playing live. The idea is sound, the Sandbox isolation and the triple signature are the right approach, but the line between a draft and a live site is exactly the line I personally wouldn't leave on autopilot without someone watching in real time.

The visual is generated code-art, no third-party images.