One-Click Deploy to GitHub Pages: Your FORGE Site Live in Seconds

We just shipped something you've been asking for.

You generate your site in FORGE. You review the code. And now—with a single click—your site is live on GitHub Pages, under your control, deployed to your terms.

No credit card. No waiting. No platform dependency. Just your code, your GitHub account, your infrastructure.

The Old Flow (Still Available)

When FORGE launched, the deploy flow looked like this:

1. Generate your site in FORGE
2. Review the code
3. Download the files (or push to GitHub manually via command line)
4. Set up a GitHub repo yourself
5. Connect to Vercel (or another host)
6. Configure deployment settings
7. Wait for your site to build

That worked. Thousands of sites shipped that way.

But it required steps. It required knowledge. For a founder who just wants their site live now, it was friction.

The New Flow

Today:

1. Generate your site in FORGE
2. Review the code
3. Click "Deploy to GitHub Pages"
4. Authorize FORGE once
5. Done. Your site is live.

That's it.

How It Works

Here's what happens behind the scenes (and why this matters):

One-Click Authorization — The first time you deploy, FORGE asks permission to push to your GitHub. You authenticate once, and we create a deploy token. That token stays in your control—you can revoke it anytime in GitHub settings.

Auto-Generated Repository — FORGE creates a new GitHub repo with a clean name (based on your site title), pushes your Next.js code, and configures GitHub Pages. You can browse the code immediately. It's yours.

Automatic Build and Deploy — GitHub Actions automatically builds your Next.js site and deploys it to GitHub Pages. Your domain is live at [your-username].github.io/[repo-name] (or your custom domain if you add one).

Your Code in Version Control — Every deployment creates a commit. You can see the full history of what changed. You can roll back, fork, or continue building locally. Total transparency.

Why This Matters

You're probably thinking: "Vercel does this too. Why is GitHub Pages deployment different?"

Three reasons.

It's Actually Free

GitHub Pages costs nothing. No usage limits. No surprise bills at the end of the month. You push code to GitHub, Pages serves it. That's the deal.

(Vercel is free too for most cases, but there's always a line where "free" ends and paid begins. GitHub Pages genuinely doesn't have that line.)

Your Code, Your Repo

When FORGE pushes to your GitHub, the repository is yours. Not FORGE's. You can clone it to your laptop, modify the code locally, push changes directly to GitHub. You can invite collaborators. You can fork it for a different project. It's a real GitHub repo with real version control.

One Less Platform

Every SaaS platform is another login. Another potential failure point. Another thing to monitor.

With GitHub Pages deployment, you have exactly two things:

• FORGE (generates your site)
• GitHub (hosts your code and deploys it)

Your site works without either one. Without FORGE? Your code still works; you just can't regenerate in the browser. Without GitHub? Your code is on your laptop. Without Pages? You push to another host.

That's freedom.

Who This Solves For

Founders who value ownership — You want code ownership. You want your site in version control. GitHub Pages with FORGE gives you both.

Developers building for clients — You can generate sites for clients and push them to the client's GitHub account. Client owns the code, Pages hosts it free, you iterate in FORGE. No friction.

Bootstrapped teams — Free hosting is non-negotiable. GitHub Pages is the obvious choice. FORGE now makes getting there a one-click operation.

Anyone who wants simplicity — Generate, review, deploy. That's the flow. No extra steps. No platform navigation.

How to Use It

1. Generate your site (or open an existing one in FORGE)
2. Click the "Deploy" button (top right)
3. Select "GitHub Pages"
4. Authorize FORGE to access your GitHub (first time only)
5. Confirm the repo name
6. Watch it deploy live

Your site is live in 30 seconds. GitHub shows you the commit. Pages starts building automatically.

Visit your repo's "Deployments" tab to see the live link. Add a custom domain in GitHub Pages settings if you want. That's optional.

One More Thing

We're not stopping here.

We're working on:

Continuous Regeneration — Update your site description in FORGE, click regenerate, one-click redeploy to GitHub. No manual code updates needed.

GitHub Collaboration — Invite other founders to your repo, they can push changes alongside your FORGE-generated code. Full GitHub workflow.

Multi-Platform Deployment — Vercel, Netlify, Railway—coming next.

Try It Today

Generate a new site and deploy it to GitHub Pages in under a minute. Or open an existing site and click deploy.

You'll own the code. You'll own the infrastructure. You'll own the deployment.

That's how websites should work.

→ Generate free → Deploy your first site