Docs/Unified Egress Gateway
Platform Architectureapi.nunc.cloud · Policy & Routing Mediation

Unified Governance Gateway

Every request entering Nunc — whether from Data Studio Web, Claude Desktop, ChatGPT, Slack, or a backend service — terminates at https://api.nunc.cloud. Centralizing ingress lets security and data teams define policies once and enforce strict principal isolation across every lane.

1. Specialized ingress lanes

Ingress PathAdmitted PrincipalsRuntime Pipeline
/api/* · /chat/completionsFirst-party SSO JWTs, type="chat" SDK apps, and nes_* embeds (completions only). Service keys denied (403).First-party CORS + CORP, Guardian 6-stage firewall, reversible ⟦PII:TYPE#N⟧ tokenization, memory scoping, and write approvals.
/mcp · /mcp/analytics · /mcp/memory · /mcp/sandbox · /mcp/delegateHuman OAuth 2.1 PKCE tokens (plus type="federated" apps on /mcp).Default-deny PBAC, Guardian prompt & secret scanning, outbound [REDACTED:TYPE] PII masking, and human write gates.
/serviceMachine Service Applications (type="service" only).Deterministic connector execution with Application-tier grants, rate limits, egress allowlists, and SHA-256 audit logging.

2. Gateway operational controls

  1. Policy-driven model routing: Administrators choose permitted model families in Console → Organization → Settings. The gateway routes analytical turns, deep reasoning plans, and code tasks across approved models with automatic failover and per-user token budgets.
  2. Fail-closed surface kill switches: Toggle service, mcp, external_surfaces, sidecar, or channels in Console → Trust → Security to halt calls on that surface within seconds without revoking SSO accounts.
  3. Unified SHA-256 execution ledger: Every ingress lane writes to the tenant's isolated audit ledger so compliance teams inspect one chronological timeline across Data Studio, Claude, Slack, @nunc/sdk, and /service.