Skip to content

Gateway

Responsibility

External entrypoint and policy enforcement boundary for inbound traffic.

Inbound Authentication

  • JWT/API key verification
  • route-level required scopes

Outbound Authentication

  • Forwards validated identity context to backend services.

Flow policies (YAML)

Declarative policies loaded from POLICY_DIR (default /app/flows/policies): required headers, OAuth introspection, product rate limits, transform specs. Applied on edge routes (/v1/api, /v1/webhooks). Full reference: Gateway flow policies.

Key Config

  • Gateway route/policy configuration
  • upstream service targets (ORCHESTRATOR_URL, TRANSFORMERS_URL for /v1/transform)
  • CAPABILITY_REGISTRY_URL — /v1/status probes registered providers under their registry service_name (http.service, ftp.service, …), not egress_* aliases or EGRESS_* env. Internal platform services (gateway, orchestrator, identity, dashboard, storage, scheduler, transformers) are not double-probed; orchestrator and transformers stay on ORCHESTRATOR_URL / TRANSFORMERS_URL.

Health

  • GET /healthz
  • GET /readyz