DNS
DNS records required before deploying Scrydon
The default and recommended routing mode is subpath: every Scrydon app lives behind a single hostname under a path prefix. You need one DNS A or CNAME record for that hostname, pointing at the load balancer in front of your Gateway API implementation. Set the same name as routing.host.
Subpath routing (default)
Replace app.yourdomain.com with your hostname. The Gateway matches the longest prefix first, so /agentic/realtime and /agentic/api reach their own services before /agentic.
Path prefixes on app.yourdomain.com | Served by |
|---|---|
/, /platform | platform (sign-in, settings, /platform/setup) |
/api/auth, /api/router, /api/mcp | api-platform |
/agentic | agentic |
/agentic/api, /horizon/api | api-agentic |
/agentic/realtime | agentic-realtime |
/horizon | horizon |
/analytics | analytics (notebooks open under this prefix too) |
/cortex | cortex |
/api/table | api-table |
/api/ontology | api-ontology |
Before you install, check that the name resolves to the load balancer's address:
dig +short app.yourdomain.comWhen cert-manager issues the certificate through an HTTP-01 challenge, the record must exist and port 80 must reach the Gateway before issuance can succeed. See TLS.
Subdomain routing
If you use subdomain routing instead (per-app hostnames), you need one record per app, or a wildcard. See Routing Modes for the mapping and trade-offs.