VoidZero, the company behind Vite , Vitest , Rolldown , Oxc , and Vite+ , is joining Cloudflare. As part of this change, all team members of VoidZero are joining Cloudflare, too. Before saying anything else, we want to make the most important thing clear: Vite, Vitest, Rolldown, Oxc, and Vite+ will stay open source, vendor-agnostic, and community-driven.
Nothing about that changes. Cloudflare's mission is to help build a better Internet. And a better Internet is an open Internet.
Developers need choice, frameworks need a neutral foundation, and applications need to be portable. It is not reasonable to expect the entire web ecosystem to build around a single vendor. The most important tools and frameworks are portable by design.
Vite is one of the few foundational tools that the whole JavaScript ecosystem agrees on. It earned that position by being fast, excellent, portable, and vendor-neutral. One of the best ways Cloudflare can help build a better Internet is by investing in that foundational open source toolchain.
A toolchain that makes the Internet better for everyone, not just people who use Cloudflare or choose to host with us. Over the last few years we've invested heavily in making Cloudflare the best place to build and run websites, applications, and agents on our developer platform . But ultimately that choice will always be yours.
Run your Vite application anywhere you want. What this means for Vite Today's news gives Vite more resources to keep growing, while the things that make Vite what it is remain the same: Vite remains MIT-licensed and open source. Vite remains vendor-agnostic.
Applications built with Vite run anywhere and will continue to do so. Vite's roadmap continues to be driven by the broader Vite team and community, and continues to be developed in the open. Evan and the rest of the VoidZero team continue to lead Vite, Vitest, Rolldown, Oxc, and Vite+.
Cloudflare is committing engineering and resources to those projects, not redirecting them. We made the same kind of commitment when Astro joined Cloudflare earlier this year. Astro is still open source, and still deploys anywhere.
The team is still shipping the roadmap they were already shipping. This commitment matters even more with Vite, because Vite is not one framework. Vite is the foundation underlying so many: Vue , SvelteKit , Nuxt , Astro , Solid , Qwik , Angular , React Router , TanStack Start .
Even Next. js now has a Vite-based implementation in vinext . Vite has become a shared substrate for the JavaScript ecosystem.
Our number one goal is to maintain the trust that has earned Vite so much adoption. Not with our words here, but by proving it every day in how we support and develop these projects. We also want to put our money where our mouth is when it comes to our support for open source and shared ecosystem foundations.
As part of this announcement, Cloudflare is committing $1 million to a Vite ecosystem fund to support maintainers and contributors, administered by the Vite core team. Vite is bigger than VoidZero or Cloudflare, and the people who have helped build it should be part of what comes next. Vite as the foundation The Vite and Cloudflare teams have been collaborating well before this announcement, starting in 2024 with the Vite Environment API .
The Environment API lets Vite run server code in something other than Node. js during development. We worked closely with the Vite team on its design, and then built the Cloudflare Vite plugin on top of it.
When you run vite dev with the Cloudflare plugin, your server code runs inside workerd , the same open-source runtime that powers Workers in production. Durable Objects, D1, KV, R2, Workflows, Workers AI, Agents, Service Bindings, Workers RPC – all of it runs locally inside the same runtime model as production. For a long time, the cost of developing on a non-Node runtime was that local dev felt like a worse version of production.
The Environment API removed that cost without forcing anyone to adopt a Cloudflare-specific dev server. Any runtime that wants to plug into Vite can do the same thing. That kind of design – a generic mechanism in Vite with provider-specific implementations – has proven to work well and is one we want to keep building on.
We knew we were on to something when we saw adoption of the Cloudflare Vite plugin take off: Vite's adoption curve is one of the more remarkable things to watch in the ecosystem right now. As of this writing, Vite is at roughly 129M weekly downloads . The Cloudflare Vite plugin ( @cloudflare/vite-plugin ) is at almost 14M weekly downloads .
If you had told us a year ago that a Cloudflare Vite plugin would reach downloads equivalent to more than 10% of Vite itself, we wouldn’t have believed you. What happened? AI happened.
More software is being created than ever before, and a lot of it starts with AI-generated code. Those applications need a default stack and a place to run. Agent-coded applications are choosing Vite, and increasingly they are choosing Vite running on Cloudflare.
AI is changing how we write software Developers used to be the only users of dev servers, bundlers, linters, formatters, and CLIs. That is no longer true: agents are using them too, constantly. They scaffold projects, run dev servers, read errors, write tests, lint and format code, deploy previews, and iterate.
A lot of AI-generated applications already start as Vite apps, because Vite is fast, well understood, and broadly compatible with what agents have seen in their training data. Fast feedback loops have always been important. They become even more critical when writing software with agents: Fast builds, because they iterate more than humans do.
Fast tests, because they re-run the suite constantly to verify their own work. Fast linting and formatting, because those tools become guardrails. Clear, structured errors, because the agent has to read and act on them.
Consistent CLIs, because small inconsistencies cause big detours.
Originally published at blog.cloudflare.com
