Vercel: I Didn't Choose It, Claude Did

Why I Tried This

Honestly? Claude told me to.

I was setting up this site — SG AI Nomad — and my default instinct was Cloudflare. I've poked around Cloudflare before, it's familiar enough territory, and I figured it would do the job. But I ran the decision past Claude first, and it pushed back. It recommended Vercel instead, specifically for a Next.js project.

So I followed the AI's advice. Which felt either very on-brand or slightly embarrassing, depending on how you look at it.

What I Actually Like

The GitHub integration is genuinely good. Not "good for a free tier" good — just good, full stop.

You import your project directly from GitHub, Vercel reads it, figures out what kind of project it is, and from that point on, every push to your repo triggers a new deployment automatically. I didn't have to configure a pipeline or write any deploy scripts. It just... worked.

For someone without a deep DevOps background, that matters. A lot of tools claim this kind of simplicity and then bury you in config files ten minutes later. Vercel didn't do that. The path from "I have a Next.js repo" to "it's live on the internet" was short and surprisingly free of friction.

The deployment previews are also worth mentioning. Every pull request gets its own preview URL, which is a genuinely useful feature if you're iterating on something and want to check how it looks before pushing to production. I've used it a few times already just to sanity-check layout changes.

The Rough Edges

The free tier cron job limit killed a feature I actually wanted.

I had this idea for scheduled posts — automating when content goes live, basically. Cron jobs are the obvious tool for that. But on Vercel's free tier, cron jobs are limited to once per day. That's not a scheduling tool, that's a daily alarm clock. It wasn't going to work for what I had in mind, so I had to shelve the idea entirely.

It's not a dealbreaker for the site as it stands right now, but it was a genuine disappointment. I went in thinking I could build a small automation layer on top of the hosting, and that door closed pretty quickly once I read the limits.

The other thing I'll flag — and this is minor — is that Vercel is clearly optimised for its own ecosystem. If you're running Next.js, everything fits neatly. If you're doing something outside that lane, I suspect the experience gets bumpier. I haven't tested that personally, but it's worth knowing going in.

Final Verdict

Vercel earns its reputation. For a Next.js project hosted on the free tier, it's a solid choice — the GitHub integration alone makes the setup feel effortless, and that counts for a lot when you're trying to focus on building rather than configuring infrastructure.

The cron job limitation is real and it did cost me a feature. If scheduled automation is central to what you're building, you'll want to check the pricing tiers before committing.

But for getting a Next.js site up and deployed quickly, with automatic deploys on push and preview URLs baked in? Yeah. Claude gave me good advice on this one.

4/5