You push one small change and CI runs everything from scratch. Most systems work that way, Vercel writes.
Fact
The facts: on 28 October 2026, Vercel announced Vercel CI in beta, available on all plans. As Vercel describes it, the system runs only the tasks the change touches and spins up only the compute those checks need; tasks with unchanged inputs come from cache, and Remote Cache is on by default. Setup lives in turbo.json, with no workflow YAML to maintain. By Vercel's data, in their own repositories getting from push to green CI is 2-6x faster; Vercel CI has completed nearly 8 million tasks across those repositories and the private beta. Before general availability Vercel plans observability, a vc ci command for distributed execution before pushing, and more granular test selection. The announcement gives no price.
Vercel CI asks something else: what changed? It runs only the tasks the change touches. Whatever wasn't touched comes from cache. At a load-in you don't rig the whole stage over one broken lamp.
You win on what didn't change.
Setup lives in turbo.json, with no workflow YAML. That part you can check yourself today. The number is a different matter: 2-6x faster from push to green CI is Vercel's own measurement on its own repositories and doesn't say what it will be for you. What it costs after the beta isn't known.
If your repository uses Turborepo, run the beta there and compare the time to green with your current one.
Official primary sources
Vercel - Introducing Vercel CI, 28.10.2026The visual is generated code-art, no third-party images.