GitHub Pages, with stats, logs and a server.

Name: GenHTTP Pages
Author: GenHTTP

Your build and your pages stay as they are. Change one step of the workflow, and the site gets a dashboard with its traffic, every deployment and room for code. No secret, no account.

.github/workflows/pages.yml

    steps:
      - id: deployment
        uses: actions/deploy-pages@v5
        uses: Kaliumhexacyanoferrat/genhttp-pages@v1
        with:
          activation: gp-…

Activate your repository See what you get

Every site gets a dashboard

How the site is doing at a glance, and what changed last. This is the dashboard of this very page.

Activate your repository

Activate it
Activated in this browser
Repository
Address optional
https:// .genhttp.run

I accept the terms of GenHTTP Lambda.

Open your dashboard

The link is the only way into the dashboard. This browser keeps it at the top of this step; bookmark it to have it anywhere else. Your site will answer at .
Change the workflow

Replace the deploy step, as at the top of this page:
```
        uses: Kaliumhexacyanoferrat/genhttp-pages@v1
        with:
          activation: gp-…
```
Paste your workflow, get it back changed
Your workflow
My site is published from a branch

Branch

Folder

Save as .github/workflows/genhttp-pages.yml on the default branch. It builds with Jekyll unless there is a .nojekyll.
I have no Pages workflow yet
Folder to publish
Save as .github/workflows/genhttp-pages.yml:
Push

The first run binds the code to your repository and publishes the site. The job needs id-token: write, which Pages workflows already have. Everything else

Need a server? Ask for it.

Your site runs on a real web server, so it can have a server part. Ask the dashboard's agent for it in Change, or your own agent through MCP: it is built beside your pages, which call it with fetch('api/…'). Ask for the server, not for pages: the pages stay in your repository, and a push replaces them and keeps the server.