Cloud & deploy
When a team says "we're building on Next.js", the conversation often lands on Vercel. That makes sense: the same company stands behind the framework and much of the deploy experience. But Vercel is a hosting decision — not an architecture decision.
Here's what the platform actually does, what it's good at, and when we recommend something else.
TL;DR
Key takeaways
- Vercel is deploy, edge, preview environments, and observability — not the Next.js app itself.
- It fits teams that want a preview on every pull request and low friction from day one.
- It's not a requirement: Next.js runs fine on Cloudflare, containers, and classic Node hosting.
- Choose based on ops requirements, data residency, and who should own infra — not what's most hyped.
What Vercel actually delivers
Vercel takes your Git repo and builds the Next.js app on every push. Pull requests get their own preview URLs. Production typically deploys from main. The Edge Network caches static content and runs middleware close to the user. Serverless and edge functions handle dynamic parts without you managing a server pool.
For marketing sites, MVPs, and many SaaS products it's the model we most often start with: fast feedback, sensible defaults, and a platform the team can understand without becoming DevOps specialists in week one.
Vercel vs. your own infra — in practice
Vercel
Low friction, preview deploys, and edge without building the platform yourself.
- Preview URL on every pull request
- Tight integration with Next.js features (ISR, middleware, edge)
- No server pool to size at the start
- Vendor lock-in is moderate if you keep the app portable
- Pricing follows traffic and function invocations — budget for that early
Containers / own Node host
More control, more responsibility — good when compliance or existing cloud dictates the choice.
- Full control over runtime, network, and data placement
- Fits teams with existing Kubernetes or VM setup
- You build preview environments and CI pipeline yourself
- Typically more setup before first deploy
- Almost always right when strict data requirements or a specific cloud mandate apply
Preview deploys are what you actually buy with time
The biggest practical win on Vercel for most teams isn't edge cache — it's that every pull request gets a URL. Design, product and stakeholder review happen on the real page before merge. That shortens the feedback loop more than any dashboard feature.
For that to hold, preview environments need isolated data and their own secrets. A preview that writes to the production database is worse than no preview. Plan it from the start — cheaper than cleaning up after the first accident.
When you should look past Vercel
Long-running jobs, VPC access to private systems, or very specific compliance requirements are the classic signals. Then the answer is often hybrid: frontend and ordinary API routes on Vercel, heavy workers or private networking on AWS or similar — not necessarily a full migration.
Another signal is that you already have a strong Cloudflare setup (DNS, WAF, Workers) and Pages/Workers cover your Next.js needs. Then it's rarely worth adding another platform just for the brand name.
Before you commit to Vercel in production
- Preview environments have their own secrets and isolated data — not the production DB
- The app is portable enough to move (standard Next.js, few platform-specific APIs)
- Domain, environment variables and deploy protection live in your own account
- You have a plan for long-running jobs or background work if you expect it
- Observability (logs/errors) is wired from the first production deploy
Questions we get over and over
Is Vercel only for Next.js?
No. Vercel also hosts other frontend frameworks and static sites. But the tightest integration and most Next.js-specific features naturally live here, because the same company develops both.
Can we move away from Vercel later?
Yes, if the app is built portably: standard Next.js, no Vercel-specific APIs you can't live without, and infra in your own accounts. We structure projects with that in mind — exit should be possible, not taboo.
What about Cloudflare as an alternative?
Cloudflare Pages and Workers are a strong alternative — especially if you already have DNS, WAF, and R2 there. Friction is slightly higher on some Next.js features, but for many production apps it's an excellent match. We choose between them based on your setup, not dogma.
Do we need Vercel Pro from day one?
Not necessarily. Hobby/team plans often cover MVP and early production. Upgrade when you hit limits on team size, environments, or compliance — not because the sales brochure says so. We help assess when that makes sense.
Unsure about hosting choice?
Let's clarify Vercel vs. alternatives — before you commit.
We'll walk through your product, traffic expectations, and ops requirements and recommend the model that fits — even if the answer isn't Vercel.