Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions apps/docs/src/content/docs/try-the-demo.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/)):
Expand Down
1 change: 1 addition & 0 deletions apps/site/src/layouts/Base.astro
Original file line number Diff line number Diff line change
Expand Up @@ -867,6 +867,7 @@ const {
<h2>Product</h2>
<a href="/#demo">Live demo</a>
<a href="https://demo.fold.run/console/">Live console</a>
<a href="https://enterprise.fold.run/console/">Governed gateway</a>
<a href="https://docs.fold.run/use-cases/">Use cases</a>
<a href="https://docs.fold.run/benchmarks/">Benchmarks</a>
<a href="https://docs.fold.run/conformance/">Conformance</a>
Expand Down
45 changes: 45 additions & 0 deletions apps/site/src/pages/index.astro
Original file line number Diff line number Diff line change
Expand Up @@ -239,6 +239,29 @@ const jsonld = {
</p>
</article>
</div>

<!-- The same federation with the governance turned on. It is a separate
gateway because auth.mode is gateway-wide: demo stays anonymous and
copy-pasteable, and this one can require a token without taking that
away. Two deployments is the honest way to show both. -->
<div class="governed">
<h3>The same three upstreams, governed.</h3>
<p>
<a href="https://enterprise.fold.run/console/">enterprise.fold.run</a> 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.
</p>
<div class="route-rail">
<a class="chip chip-link" href="https://enterprise.fold.run/console/"
>enterprise.fold.run/console</a
>
<span class="chip">enterprise.fold.run/mcp</span>
<span class="muted" style="font-size: var(--body-sm)">sign-in required</span>
</div>
</div>
</div>
</section>

Expand Down Expand Up @@ -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);
Expand Down
Loading