Repository navigation
feat(site,docs): link the governed gateway next to the demo - #47
Merged
Merged
Conversation
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) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
enterprise.fold.runhas been deployed and healthy since #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, which is where the argument lands: the same binary over a byte-identical upstream set, with the governance switched on.What was added
#demosection — console and/mcpin a route rail marked "sign-in required"Every claim verified against the running system
Written from the config and the live gateway, not from memory:
auth.mode: required,policy.defaultDecision: deny✓acme— 5,000 upstream calls/day, 120 req/min, all three upstreams ✓globex— 1,000/day, 60 req/min,cf-docs+demo-tasksonly ✓www-authenticate: Bearer resource_metadata="…", and the metadata namesoauth.workas the issuer.Why two gateways, said out loud
auth.modeis gateway-wide, so governing the demo would take away the copy-pasteable thing the demo exists to be. The new copy explains this rather than leaving a reader to wonder why there are two.What is deliberately not referenced
/demo-tokenis 503 — deleting the Worker in the teardown destroyed its four oauth.work client-credentials secrets. Nothing shipped here depends on it. Everything linked answers today:enterprise.fold.run/console/spa_fold_enterpriseclient is registered at oauth.work (verified:/authorizereturns a login flow, notinvalid_client).well-known/oauth-protected-resourceSo the section demonstrates governance working — the 401 and the discovery path a client walks on its own — rather than promising anonymous access it cannot deliver. Restoring the four secrets is what would let the walkthrough add a copy-paste token and take a reader behind the wall; that is a follow-up, not a blocker.
Site and docs are deployed.
🤖 Generated with Claude Code