Runtime endpoints
Use the correct public origin for management, ingest, query, console, and generated Syslog traffic.
ReportPlane separates origins by purpose and TLS requirements.
Public origins
| Origin | Purpose | Cloudflare mode |
|---|---|---|
https://dash.reportplane.com | Browser console | Worker custom domain |
https://app.reportplane.com | Management/control-plane API | Proxied |
https://ingest.reportplane.com | HTTP/WebSocket ingest and runtime TLS | DNS-only |
https://query.reportplane.com | Analytics query runtime | DNS-only |
https://www.reportplane.com/docs | Public documentation | Worker route on the website hostname |
Syslog clients receive generated endpoint information from the console. The child zone ingestc.reportplane.com is used for generated endpoint identities in the production topology.
Why ingest and query are DNS-only
ReportPlane validates customer mTLS certificates in its own runtime. An HTTP proxy that terminates TLS would remove the original client certificate session. Future load balancing must preserve TLS with DNS steering or TCP/TLS passthrough.
CORS
The browser console calls the control-plane origin directly using the configured CORS policy. Runtime ingest/query callers are normally backend applications, agents, or devices rather than browser scripts.
Generated OpenAPI servers
Ingest OpenAPI documents use the ingest origin. Analytics OpenAPI documents use the query origin. This keeps generated examples aligned with production runtime responsibilities.