All articles
Infra4 min read

I left Vercel. Here's why, and what I kept there

A one-million-request limit, a free plan that forbids projects that sell, and about forty projects on my list. How Cloudflare became my phone book, my shield and my free host.

by Vidhal Elame
#Cloudflare#Vercel#DNS

I love Vercel. I'm saying it upfront, because this post could read like a rant against it, and it isn't one. For months every project of mine lived there: I pushed my code and the site was live thirty seconds later. I've never had a better deployment experience.

And yet, in one week, I moved almost everything out. Here's why, and where it all went.

The day I looked at my usage

One morning, checking my account usage, I saw this: 946,000 requests used out of the free plan's million. The culprit: Logoforge, my brand-logo library for developers. Every logo is a small SVG file, every page loads dozens of them, and developers who use it in their own sites multiply the calls.

Three things made me stop:

  • the limit runs over a rolling 30 days, and going over pauses the site. No surprise bill: a site that's off;
  • the free plan forbids commercial use. Two of my apps already sell subscriptions;
  • the Pro plan costs $20 a month, plus tiers. With about forty projects planned, I could already see the bill climbing with each new one.
!The real problem wasn't the price

It was unpredictability. I want to launch a project one evening without wondering what it'll cost me the day it takes off.

Sorting projects by what they need

Instead of looking for "a cheaper Vercel", I split my projects into two families:

  • static sites: files that don't change from one visitor to the next. Logoforge is the perfect example: logos, pages, a search;
  • applications: a database, accounts, payments, e-mail. Certifstudio, CVMalin, Blockforge.

The first only need a good delivery network. The second need a real server. Two needs, two answers. The apps' answer is part 3. This post is about the first.

Cloudflare, three jobs in one

Cloudflare is a network of servers in hundreds of cities. For me, it does three jobs at once:

  1. DNS host: it keeps my domain's phone book, free and fast (we saw what that means in part 1).
  2. Shield: when the "orange cloud" is on for an address, visitors talk to Cloudflare, and Cloudflare talks to my server. The machine's address stays hidden, large attacks get absorbed, and pages are compressed and served from a city close to the visitor.
  3. Static host, with its Workers: files served from its global network with no request limit on those files, plus small programs for the dynamic bits.
BEFOREAFTERVisitorRegistrar's DNSplain phone bookVercelevery site, every limitVisitorCloudflareDNS · shield · cacheWorkerstatic sitesVPSthe SaaS appsVercelthe portfolio
Before, one platform did everything. After, Cloudflare answers first and sends each visitor to the place that suits the site best.

Moving the phone book without breaking the site

That was the scary step, and it went the smoothest. The method:

  1. Copy every DNS record from the old phone book to Cloudflare, exactly. I compared both lists line by line: zero differences.
  2. Switch the nameservers at my registrar. From then on, Cloudflare answers for the whole domain.
  3. Check that every site, every e-mail address and every verification answered as before.
✓Always keep the exit door open

Going back was a single change: put the old nameservers back. Knowing that before you start completely changes how you approach a migration.

Logoforge moves to Cloudflare

Logoforge needed some work, nothing dramatic. The site is now exported as static files: every page and every logo is generated once, at build time, then served by Cloudflare. The one truly dynamic part, an MCP server that lets AI assistants fetch logos, runs in a Worker.

And just like on Vercel, every git push rebuilds and republishes the site on its own. That was my non-negotiable.

What I kept on Vercel

My portfolio, the one you're reading. It's a showcase, it sells nothing, it uses little, and Vercel serves it perfectly. Picking the tool per project also means knowing when not to move.

Where this step left me

  • Logoforge: free, no request limit on its files, still deployed on every push.
  • The domain: still rented from the same place, but its phone book lives at Cloudflare, which is also the shield.
  • Cost: nothing extra.

That left the three apps, with their databases, accounts and payments. For them I needed a real server. That's next: my own Vercel on a €20-a-month server.