Vercel is the only infrastructure I haven't second-guessed
Hosting, analytics, speed monitoring, custom domain, security certificates. All of it just runs. Here's what I trust it for and what I don't.
Most of my technology opinions are skeptical by default. Vercel is the exception. The experience of going from 'code on my computer' to 'live on the internet with a custom domain and security certificate' is genuinely hard to beat. One command and it is live. The security certificate generates itself. The analytics dashboard appears without adding tracking scripts. The speed monitoring shows how fast real visitors experience the site, not just lab scores from my fast laptop.
Hosting for the site itself. Built-in analytics for visitor counts — the privacy-friendly kind that does not need a cookie consent banner. Speed monitoring that shows how fast real visitors experience the site, using actual data from real devices and connections. Custom domain on nirmitmeher.com, all handled through a simple DNS setup that took ten minutes.
I also use Vercel's preview deployments for every change. Before anything goes live, Vercel builds a preview version at a temporary URL. I can open it, check that the pages look right, test the chatbot, and verify the blog posts render correctly. Only after that check does the change go to the real site.
I strongly recommend creating a deploy script with safety checks instead of relying on auto-deploy. Mine checks four things before and after every deployment: Is the project linked to the correct Vercel project? Did the build pass without errors? Does the live URL return a successful response? Is the deployment URL from the expected project, not a different one on the same account?
That last check caught a real bug. I once accidentally deployed to a completely different project and did not realize it because the live site still showed the old version (which looked fine). My deploy script now refuses to proceed unless the project link matches exactly. I also added an auto-rollback safety net: if a deployment fails or serves errors, Vercel automatically rolls back to the previous working version.
The entire deploy process takes about 45 seconds. The safety checks add maybe five seconds. That five seconds has saved me from at least two deployment disasters.
Sign up, connect your project, and deploy. For a custom domain, add it in the Vercel dashboard, then update your domain registrar's DNS records to point at Vercel (they give you the exact values to enter). Security certificates are provisioned automatically. Analytics and speed monitoring are free on the basic tier and take about two minutes to enable.
One thing to watch out for: linking your local project to the right Vercel project is fragile when you have multiple projects on one account. Always verify the project link before deploying. A misrouted deploy to the wrong project is silent and invisible until someone notices the site did not update.
Never trust auto-confirm on a command with consequences you can't undo.
Building AI products in public.
Occasional notes on what I'm shipping, what's working, and what broke — straight to your inbox. No spam, unsubscribe anytime.
Product leader shipping across enterprise SaaS, AI in production, and 0→1. Writing about what actually ships — not what sounds good in a deck.