A project that only runs on your laptop isn't a real project. It's a draft. The moment it has a URL that anyone in the world can visit, something changes — for you and for anyone you show it to.
Vercel is the fastest way to get there. It's free, it takes about 10 minutes to set up, and once it's connected to GitHub, every time you push code, your site updates automatically. No manual uploads. No FTP. No deployment pipeline to maintain.
Here's the full setup, from zero to live URL.
If you don't have a GitHub repo for your project yet, that's step one. If you already do, skip ahead to step 3.
Go to github.com, click the + icon in the top right, and select New repository. Give it a name. Leave it public or set it to private — Vercel works with both. Don't add a README or .gitignore yet if you already have local files.
GitHub will show you a set of commands. Copy the ones under "push an existing repository." They look like this:
git remote add origin https://github.com/yourusername/your-repo.git git branch -M main git push -u origin main
Paste and run those in your terminal from inside your project folder.
Go to vercel.com and click Add New → Project. Vercel will ask to connect to GitHub — authorize it. Then you'll see a list of your GitHub repos. Find your project and click Import.
For most projects, Vercel detects the framework automatically and sets everything correctly. If you're deploying a plain HTML site, select Other as the framework and leave the build settings blank. If you're using Next.js, React, or Astro, Vercel already knows what to do.
The only setting you might need to change: Root Directory — if your project files aren't in the top-level folder, tell Vercel where to look.
Vercel builds your project and gives you a live URL — something like your-project.vercel.app. This usually takes under 60 seconds.
Open the URL. Your project is live.
From now on: every time you push to your GitHub main branch, Vercel automatically deploys the update. You don't have to do anything else. That's the loop — edit locally, push to GitHub, site updates in about 30 seconds.
In your Vercel project dashboard, go to Settings → Domains. Type in your domain name and click Add. Vercel will show you the DNS records you need to add — usually two: an A record pointing to Vercel's IP, and a CNAME for the www version.
Log into wherever you bought your domain (Namecheap, GoDaddy, Google Domains, etc.) and add those DNS records. DNS changes take anywhere from a few minutes to 48 hours to propagate — usually it's under an hour.
Once it propagates, Vercel automatically provisions an SSL certificate. Your site is live at your custom domain with HTTPS, for free.
If your deployment fails, Vercel shows you the build logs. The error is almost always one of three things: a missing dependency, a wrong build command, or a file that references something that doesn't exist in the repo.
Click on the failed deployment in your Vercel dashboard, scroll through the log, and find the first red line. That's usually where the problem is. Copy it and ask Claude — it'll tell you exactly what to fix.
In MakerSquare's program, students deploy their first project to a live URL on Day 2. By the end of week one, they've shipped three. The deploy loop becomes automatic fast.