Getting Your Project Online (Deployment)

Deployment means your code ends up on a server or CDN that other people can actually open in a browser.

What deployment actually means

"It works on my machine" isn't enough. Deployment means your build output ends up on a server or CDN reachable by a URL — not just sitting on your own computer.

Static vs. server

A static site is finished HTML, CSS, and JavaScript — no server required at runtime. That's true for most vibe-coded frontends. A server app (with its own backend, database access at runtime) needs a runtime that keeps running. For getting started, a static site is almost always the simpler path.

The free-tier path for beginners

The usual flow: push your code to a GitHub repo, connect that repo to a static hosting provider (Cloudflare Pages, Vercel, Netlify, and GitHub Pages are all common choices), done. Every push to your main branch then triggers a new automatic deployment.

Env vars and secrets

API keys and passwords never belong directly in your code or your repo. Add them instead through your host's secret or environment-variable settings.

A custom domain is optional

Every provider gives you a free subdomain (like your-project.pages.dev). That's completely fine to start with. You can always add a custom domain later.

Let your agent do it — but review it

A coding agent can set up your deployment for you. Still review what it configures, especially anything touching billing or payment details.