Vercel.
Hosting for web front ends, with a preview link for every change and server functions that scale on demand.
Talk to us about Vercel
Key features
What Vercel does well.
Preview deployments
Every pull request gets its own live URL, so changes are reviewed in a browser rather than in screenshots.
Functions that scale
Server code runs on Fluid compute, which scales with traffic and can reuse instances between requests.
CDN and firewall included
Pages are cached across a global network, with a web application firewall and DDoS mitigation on every plan.
Framework-aware builds
Next.js, Astro and other frameworks are detected and built with sensible defaults, with little configuration.
What we build with it
Every change gets a link before it goes live.
Vercel builds and deploys a web front end on every push. Each pull request gets its own preview URL to review, pages are served from a global CDN, and server code runs as functions that scale with traffic. This website runs on Vercel.
Marketing and content sites
Astro and Next.js sites where editors and stakeholders review each change on a preview link first.
Product front ends
Next.js applications whose server code runs as functions and talks to APIs and databases hosted elsewhere.
A review step for every change
Pull requests that come with a working preview, so design and product sign-off happens before merge.
When it’s the right choice
Vercel suits web front ends built with Next.js, Astro or React, when a team wants preview links for every change and little infrastructure to run.
When we’d pick something else
Long-running jobs, heavy background processing and most databases sit better with a cloud provider such as AWS, with Vercel hosting the front end. Costs grow with traffic, so we model them early.
Our Vercel services
How we can help.
Moving to Vercel
We move existing sites onto Vercel, set up domains, redirects and environment variables, and switch traffic without downtime.
Preview workflow
We set up previews for every pull request, with Neon database branches where data changes need testing.
Performance and caching
We check what is cached, rendered or run as a function, and tune it so pages stay fast and costs stay predictable.
Cost review
We look at function usage, bandwidth and build minutes, and agree which changes would lower the bill.
How we work
Starting a Vercel project.
Review what exists
Code, data, hosting and the people who maintain it, before any Vercel decision is made.
Agree the approach
A written scope: what changes, what stays, the risks and how we will know it worked.
Build in reviewable slices
Working increments your team can test, rather than one large delivery at the end.
Hand over or stay on
Documentation and access for your team, or a defined support scope if you want us to keep going.
Where AI fits
AI in cloud & infrastructure work.
Models inside your cloud account
Amazon Bedrock, Azure and Google’s Gemini Enterprise Agent Platform give model access under your own account’s access, logging and billing controls.
AI workflow automation ↗Region and residency checks
Model availability differs by region, so we check where prompts and documents will be processed before choosing a service.
Cloud architecture ↗
Where it stops: Turning on a model service does not make a use compliant. Data protection and sector rules still apply to every prompt and output.
What’s changing
Shifts to plan for.
Dates that affect Vercel projects, checked against the official sources.
July 2026
Vercel acquires Better Auth
Vercel announced it is acquiring Better Auth. The library stays free and MIT-licensed, with the same team leading it and a new focus on identity for AI agents.
Where it fits
Related expertise.
- Web application development Browser-based tools for customers and staff, built for the data, roles and permissions behind them.
- Cloud architecture Choose and structure cloud services around your product’s data, access and operating needs.
- CI/CD pipelines Automated builds, tests and deployments, so every release follows the same checked path.
Common questions
Vercel questions.
Can each pull request have its own database?
Yes. With Neon from the Vercel Marketplace, a preview deployment can use its own database branch, so data changes are tested before they reach production.
Where does the site actually run?
Pages are served from Vercel’s global CDN. Server functions run in a region you choose, including London, close to your data.
Further reading
- A database for every pull request: preview environments that work How to give each pull request its own database branch, with safe data, tested migrations and automatic clean-up.
- Awaab’s Law and the software landlords use for repairs What Awaab’s Law asks of the systems social landlords use to log, investigate and repair hazards, and the records they need to keep.
- Firebase, Supabase or a custom back end: how to choose How to choose between Firebase, Supabase and a custom back end by data shape, access rules, cost, exit paths and skills.
