How We Build/Vercel Hosting
3Live Hosting

What Vercel does as the host

Vercel is a cloud platform built for Next.js — the same company helps maintain the framework. It turns a Git push into a worldwide production deploy in seconds.

Global edgeHTTPS by defaultGit-connectedServerlessInstant rollback

How hosting works here

You do not rent a single server to log into and patch by hand. Vercel connects to the project's Git repository and watches it. When the developer pushes a change, Vercel automatically runs next build on its infrastructure, producing optimised static pages and serverless function bundles. Those outputs are then distributed across the global edge network.

The live site is a clean build from the repository — not a server that has drifted under manual edits over months. What the public sees is always traceable to a specific Git commit.

What Vercel provides

Git-connected deploys

Every push to the repository triggers a fresh build automatically. No FTP, no manual deploy step, no SSH session. The site advances in step with the code.

Global edge network

The built site is distributed across Vercel's data centres worldwide. Visitors are served from a location near them — one of the reasons pages load quickly regardless of where the visitor is.

HTTPS by default

Every deploy — production and preview — gets a valid SSL certificate automatically. No certificate management or Certbot cron jobs required.

Atomic deploys

The new version goes live all at once. Visitors never see a partially-updated site mid-deploy — the switchover is instant and complete.

Instant rollback

Any previous production deploy can be reinstated in one click from the Vercel dashboard. Every deploy maps to an exact Git commit — what went live and when is always traceable.

Serverless functions

When a page or API needs server-side code, Vercel runs it as a short-lived serverless function — not an always-on machine. The model is 'run this when asked', which scales automatically and costs nothing at rest.

Preview deployments

Every branch push — not just pushes to main — gets its own unique preview URL. This is how the client reviews work before it goes to production: a real browser link that matches exactly what will ship, not a developer's localhost that requires being on the same machine.

# Push a feature branch

$ git push origin feature/new-services-page

✓ Vercel preview deploy: https://arvintech-abc123.vercel.app

# Client reviews at that URL, then approves

$ git merge feature/new-services-page && git push origin main

✓ Production updated worldwide

How the three parts connect

1

Software stack

The packages and frameworks that make up the app.

2

Cursor IDE

Where the developer writes and edits the source code.

3

Vercel

Watches the repo, builds the output, and serves it worldwide.