Vite gets downloaded 100 million times a week and still couldn’t make rent This week it moved in with Cloudflare.

The tool half the front end quietly runs on just got an owner. Whether that’s a rescue or the first act of something worse is the whole question.

If you’ve built anything on the web in the last three years, you’ve used Vite, even if you’ve never typed its name. It’s the thing that starts your dev server in about the time it takes to blink.

It’s what npm create vite spits out. It's under your Vue app, your React app, your Svelte and Solid and Astro app, it's the default that quietly replaced the Webpack config nobody on the team could actually read.

Last I looked it gets pulled down something like a hundred million times a week. More, depending who's counting.

On Wednesday, the company behind it, VoidZero, got bought by Cloudflare.

My first reaction was relief, honestly. My second was a small cold feeling I’ve spent all week trying to name.

The part nobody says out loud

Here’s the fact that’s actually interesting, more than the acquisition itself. Evan You, the guy who built Vue and then built Vite and then started VoidZero around it back in 2023, more or less admitted in the announcement that the thing had a money problem. Not a usage problem. A hundred-million-downloads-a-week tool does not have a usage problem. A money problem.

Sit with that, because it’s the whole story. You can build the single most-used build tool on the planet, the thing basically every frontend developer alive reaches for daily, and still not have a business under it.

Downloads aren’t dollars. Nobody runs npm install vite and gets asked for a card. The tool everybody needs turns out to be the tool nobody pays for, and that gap doesn't close when you get popular.

It widens, because now the whole industry's expectations are sitting on a project funded by sponsorships and goodwill.

So when people ask why would Evan sell, I think the question’s pointed the wrong way. The actual surprise is that a tool this load-bearing stayed independent as long as it did.

Why Cloudflare specifically

This is the bit that makes it click, and also the bit that makes me uneasy. Cloudflare didn’t buy Vite because they’re fans of fast dev servers. They bought it because the build tool is the on-ramp.

It’s the first thing you touch when you start a project, and it’s the thing that decides how your app gets bundled and shipped, and Cloudflare is in the business of where your app gets shipped to. Own the on-ramp, and you get a quiet say in where the road goes.

We’ve all seen this movie. Next.js is owned by Vercel, and for years there’s been a low hum of suspicion every time Next ships something that works a little too smoothly on Vercel and a little less smoothly off it. Nobody’s saying anyone’s a villain.

It’s gravity. When the company that makes your framework also sells you the hosting, the framework starts, very slowly, leaning toward the hosting, and you can’t always point at the exact week it happened.

Vite’s whole superpower was that it didn’t lean. It was the neutral ground, the one thing every competing framework could agree on, Switzerland for the JavaScript build layer.

That neutrality is the real asset Cloudflare just bought. And neutrality is a strange thing to own, because the owning is the thing that puts it at risk.

Okay, but they did say the right things

I want to be fair, because the cynical read is the easy one and it might be wrong. Cloud flare and Evan said the words you’d want said. Vite, Vitest, Roll down, Oxc, all of it stays open source under MIT and stays vendor-agnostic.

The team keeps leading the projects. There’s a million-dollar fund set up specifically for ecosystem maintainers who work for neither company, which is a genuinely thoughtful move and not the kind of thing you bother with if you’re planning a heist.

And Cloudflare, credit where it’s due, has a better record here than most. They’ve open-sourced real things, they don’t have Google’s habit of walking products into the sea after eighteen months. If I had to pick a big infrastructure company to adopt the tool I use every day, they’re near the top of a short list.

This could honestly be the good ending, the one where Vite finally gets funded properly and maintained for a decade instead of running on one person’s heroic energy until he quietly burns out.

I just can’t fully shake the other thing. Vendor-agnostic, owned by a vendor is a sentence that has to be made true again every single quarter, against the steady pull of a roadmap that answers to shareholders now. A promise is a snapshot. Incentives are the weather.

What it actually means for you

Practically, today, nothing changes. Your vite.config.ts works the same on Monday as it did on Friday.

You don't need to do anything or switch anything or panic. If you're shipping a side project this weekend, Vite is still the right call, exactly like it was last week.

What changed is slower and more about the shape of the thing. The JavaScript build layer spent a decade as a wild fragmented mess, then finally, blessedly, converged on one good neutral tool, and now that one tool sits inside an infrastructure company that also wants your deployment money.

Maybe that’s fine. Maybe in three years we’re all just relieved Vite got funded and nothing weird happened. But the thought I keep landing on is smaller and a bit sad, that free, neutral, independent, and critical to everyone was apparently never a stable place for a tool to live. It was always going to resolve into being somebody’s asset. We just got to watch which somebody.

Anyway I scaffolded a new project last night, npm create vite, watched the dev server come up in about two hundred milliseconds like it always does, and felt weirdly sentimental, which is a deranged way to feel about a build tool. then I picked Vite anyway. what else am I going to do…