Jevons Paradox in Web Hosting: Why Cheaper Isn't Always Better

In this article, we’ll explore this 19th-century economic concept and how it sneaks into modern web development—especially through services like Vercel, Netlify, and AWS. Buckle up, it’s gonna be fun, ironic, and full of real-world implications.

Who Was Jevons?

The term “Jevons Paradox” comes from William Stanley Jevons, a British economist and logician. In 1865, he noticed something surprising about coal: as steam engines became more efficient at using coal, overall coal consumption didn’t go down—it went up.

Why? Because improved efficiency made coal-powered machinery more economical and widespread, leading to more usage, not less.

That insight became the foundation of what we now call the Jevons Paradox.

Jevons Paradox for Web Devs (the Ice Cream Analogy)

Let’s simplify it with a story: You invent a new ice cream machine that uses less electricity. Awesome! Now it’s cheaper to make ice cream. So you start making way more of it. Everyone loves it. But oops—now you’re using more electricity overall than with the old machine.

And here’s another catch: if you’re giving away all your ice cream—or only selling super cheap cones—your shop will only survive if enough people buy the big, expensive sundaes to make up for the cost. If not, even your awesome, efficient machine can’t save the business. This mirrors the model many hosting platforms use: offering generous free tiers, hoping that a portion of users will eventually pay for the premium plans to cover the costs of everyone else.

That’s the Jevons Paradox: making something more efficient or cheaper leads to using it more, which can increase total consumption.

Let’s see how this applies to web hosting, for example AWS, Netlify, and Vercel.

AWS and the Cost of Scale

Amazon Web Services (AWS) makes it incredibly cheap to start a server, spin up a Lambda function, or store gigabytes in S3. With pay-as-you-go pricing, it feels like you’re saving money.

But the Jevons Paradox kicks in when companies overuse services:

• Thousands of tiny Lambda functions instead of bundled logic.

• Endless backups “just in case” on S3.

• EC2 servers running 24/7 for low-traffic sites.

AWS gets richer. Your cloud bill grows. Efficiency created permission to overconsume.

Netlify: The Silent Enabler of Over-Previewing

Netlify offers a similarly generous free tier, especially for personal projects and JAMstack sites. Deploy previews, serverless functions, instant rollbacks—it’s a frontend developer’s dream.

But this comfort can encourage bad practices:

• Triggering CI builds for every content change.

• Deploying on save due to tight CMS integrations.

• Keeping unused preview branches around for months.

Netlify’s generous offering invites more frequent (and sometimes unnecessary) deployments. The cost of serving them accumulates over time.

Vercel: The Cost of Convenience

Vercel is beloved for its smooth DX and preview deployments on every push. That’s great for collaboration and testing, right?

But here’s the twist: when it’s free or cheap to create previews, teams might go wild. Every commit, every branch, every experiment—boom! A new preview with serverless functions, SSR, and edge caching.

Result? Total server usage spikes. More bandwidth, more server time, more logs. Even if each preview is cheaper to serve, the total cost rises.

And guess what? That cost is on Vercel’s side—unless they charge or limit you.

How Vercel Can Fight the Paradox

While devs can reduce waste, the real responsibility lies with Vercel to make the business sustainable. Their strategies might include:

• Tightening limits on free tiers (e.g., fewer preview deployments, lower build minutes).

• Encouraging upgrades with usage-based pricing.

• Introducing stricter quotas for bandwidth or serverless invocations.

• Improving infrastructure efficiency on their end.

Raising prices for Pro or Enterprise plans might seem risky, but it’s a lever to ensure high-usage customers contribute proportionally to the costs.

Conclusion

The Jevons Paradox is a helpful lens to examine how we use modern developer tools. Making something cheaper or faster doesn’t automatically mean it’s better in the long run—unless we keep usage in check.

Efficiency is power. Just don’t let it backfire.

Do you want to prototype your ideas faster?

Check out my latest Nextjs 15 template! Done with motion, shadcn, support for several languages, newsletter, etc!

See more