From 3f71b0e7882e5df3b011f6aa419314fd736087a6 Mon Sep 17 00:00:00 2001
From: Blake Bauman
Date: Tue, 25 Aug 2026 18:49:13 -0700
Subject: [PATCH] feat(site,docs): link the governed gateway next to the demo
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
enterprise.fold.run has been deployed and healthy since the redeploy in
#45, and nothing anywhere pointed at it — a finished gateway with tenants,
budgets, deny-by-default policy and audit configured, that no reader could
find. This links it beside the demo, where the argument lands: it is the
same binary over a byte-identical upstream set, with the governance on.
homepage a governed block closing the #demo section, with the console
and /mcp in a route rail marked "sign-in required"
footer "Governed gateway" in the Product column
docs a "same federation, governed" section in the walkthrough
Every claim is checked against the running config rather than written from
memory: both gateways federate the identical three upstreams (same ids,
urls and namespaces), auth.mode is required, policy is deny-by-default,
acme gets 5,000 calls/day at 120 req/min, globex 1,000 at 60 and no GitMCP
at all. Both curl examples in the docs were run verbatim and produce the
documented output — the 401 carries the RFC 9728 challenge, and the
metadata names oauth.work as the issuer.
It is a separate deployment because auth.mode is gateway-wide: governing
the demo would take away the copy-pasteable thing the demo exists to be.
The new copy says so rather than leaving two gateways unexplained.
Deliberately not referenced: /demo-token, which is 503 because deleting
the Worker in the teardown destroyed its four oauth.work
client-credentials secrets. Nothing shipped here depends on it, so this
points only at paths that answer today — the console (which reaches a
real login flow; the SPA client is registered) and the 401 discovery
path. Restoring those secrets is what would let the walkthrough add a
copy-paste token and go behind the wall.
Co-Authored-By: Claude Opus 5 (1M context)
---
apps/docs/src/content/docs/try-the-demo.md | 30 +++++++++++++++
apps/site/src/layouts/Base.astro | 1 +
apps/site/src/pages/index.astro | 45 ++++++++++++++++++++++
3 files changed, 76 insertions(+)
diff --git a/apps/docs/src/content/docs/try-the-demo.md b/apps/docs/src/content/docs/try-the-demo.md
index 4614431..6a52b0f 100644
--- a/apps/docs/src/content/docs/try-the-demo.md
+++ b/apps/docs/src/content/docs/try-the-demo.md
@@ -97,6 +97,36 @@ GitMCP speaks the 2025-era session handshake. fold — built on the official Go
Open **[demo.fold.run/console](https://demo.fold.run/console/)** — the read-only [fold console](/console/), enabled in the demo's config. The dashboard shows the three upstreams, their breaker state, and the deployment facts live, and **[the map view](https://demo.fold.run/console/#/upstreams?view=map)** draws the federation itself: one gateway node fanning out to cfdocs, git, and jobs, each route carrying that upstream's current breaker state. It's generated from `/api/federation`, so it's this demo's real topology, not a picture of one. The test console is a plain MCP client against the same `/mcp` endpoint you've been curling, governed and audited like any other caller.
+## The same federation, governed
+
+Everything above is unauthenticated on purpose. [`https://enterprise.fold.run`](https://enterprise.fold.run/console/) is the same binary over the same three upstreams with `auth.mode: required` — a separate deployment because `auth.mode` is gateway-wide, so making one governed would otherwise take the copy-pasteable one away.
+
+An anonymous `initialize` there answers `401` with an RFC 9728 challenge, which is the correct answer rather than a failure:
+
+```bash
+curl -si -X POST https://enterprise.fold.run/mcp \
+ -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
+ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2026-07-28","capabilities":{},"clientInfo":{"name":"me","version":"0"}}}' \
+ | grep -i www-authenticate
+# www-authenticate: Bearer resource_metadata="https://enterprise.fold.run/.well-known/oauth-protected-resource"
+```
+
+Follow that metadata and you get the issuer a client should sign in to — the discovery path an MCP client walks on its own:
+
+```bash
+curl -s https://enterprise.fold.run/.well-known/oauth-protected-resource
+# {"resource":"https://enterprise.fold.run","authorization_servers":["https://oauth.work"],...}
+```
+
+Two tenants sit on it, differing on every axis a tenant governs:
+
+| Tenant | Budget | Rate limit | Upstreams |
+|---|---|---|---|
+| `acme` | 5,000 upstream calls/day | 120 req/min | all three |
+| `globex` | 1,000 upstream calls/day | 60 req/min | `cf-docs`, `demo-tasks` — never reaches GitMCP |
+
+`globex`'s subset filters the fan-out *before* policy runs, so GitMCP is not asked, not billed, and not a partial failure when it is down. Policy is deny-by-default and splits each tenant by `actor_type`, so a signed-in person and that person's agent get different surfaces through the same gateway. The [console](https://enterprise.fold.run/console/) reads it all back live, behind sign-in.
+
## Run this yourself
The demo is assembled from one config — the same shape as any fold deployment ([configuration reference](/configuration/)):
diff --git a/apps/site/src/layouts/Base.astro b/apps/site/src/layouts/Base.astro
index ac40da2..a9da501 100644
--- a/apps/site/src/layouts/Base.astro
+++ b/apps/site/src/layouts/Base.astro
@@ -867,6 +867,7 @@ const {
Product
Live demo
Live console
+ Governed gateway
Use cases
Benchmarks
Conformance
diff --git a/apps/site/src/pages/index.astro b/apps/site/src/pages/index.astro
index 3105e65..6e4150d 100644
--- a/apps/site/src/pages/index.astro
+++ b/apps/site/src/pages/index.astro
@@ -239,6 +239,29 @@ const jsonld = {
+
+
+
+
The same three upstreams, governed.
+
+ enterprise.fold.run runs the same
+ binary over the same federation, with auth required and two tenants on it. acme spends
+ up to 5,000 upstream calls a day at 120 req/min; globex gets 1,000 at 60, and never
+ reaches GitMCP at all — the subset filters the fan-out before policy runs, so that
+ upstream is not asked, not billed, and not a partial failure when it is down. Policy is
+ deny-by-default and splits each tenant by whether the caller is a person or an agent.
+
+
+
@@ -1104,6 +1127,28 @@ const jsonld = {
border-color: var(--color-trace-hi);
text-decoration: none;
}
+ /* The governed gateway hangs off the end of the demo section rather than
+ getting a section of its own: it is the same federation, and the argument
+ only lands next to the ungoverned one. */
+ .governed {
+ margin-top: var(--spacing-lg);
+ padding-top: var(--spacing-lg);
+ border-top: 1px solid var(--color-trace);
+ }
+ .governed h3 {
+ font-size: 1.0625rem;
+ font-weight: var(--weight-heading);
+ line-height: var(--line-height-card);
+ margin-bottom: var(--spacing-sm);
+ color: var(--color-fg);
+ }
+ .governed p {
+ color: var(--color-static);
+ font-size: var(--body);
+ line-height: 1.6;
+ max-width: 78ch;
+ margin-bottom: var(--spacing-md);
+ }
.console-note {
color: var(--color-static);
font-size: var(--body-sm);