Custom Domain Edge Routing
Custom Domain Edge Routing allows developers to map their own branded domain (e.g., api.yourdomain.com) to edge infrastructure via CNAME and automated TLS issuance. This creates white-labeled API endpoints, prevents third-party ad-blocker filtering, and enhances brand authority.
Technical Architecture & Deep-Dive
When frontends query third-party gateway URLs like `https://realcomposer.com/v1/workspace/endpoint`, internal architecture is visible in DevTools and certain privacy extensions or corporate firewalls may block third-party domains.
Custom Domain routing leverages Cloudflare for SaaS (Custom Hostnames) to issue and automatically renew free DV SSL certificates for customer hostnames. Edge Workers intercept incoming `Host` headers to identify the workspace and execute pipelines with zero URL prefix bloat.
Key Architectural Benefits
Implement Custom Domain Edge Routing at the Edge
Deploy lightweight API aggregation, edge caching, and secret injection in minutes without Docker containers or complex servers.
Frequently Asked Questions
Q:Do custom domains require moving DNS to Cloudflare?
No. Customers can keep their existing DNS provider (Route 53, Namecheap, GoDaddy) and simply point a CNAME record to the designated fallback origin.
Related Architecture Concepts
A Reverse Proxy is an intermediate server that intercepts requests from client applications and forwards them to one or more backend origin servers. The reverse proxy terminates TLS, applies security filtering, caches responses, and returns the result to the client as if it originated from the proxy itself.
Backend for Frontend (BFF) is an architectural pattern where a dedicated gateway layer is created for a specific frontend client (e.g., iOS, Android, React). Instead of clients calling multiple generic backend APIs, the edge BFF aggregates upstream calls, injects credentials, and strips unneeded payload fields before transmission.
A Client Token is a scoped, revocable authentication credential designed for frontend web and mobile applications. It grants permission to invoke specific edge API pipelines while enforcing allowed-origin domains and rate limits, safely abstracting sensitive upstream API secrets.