📄️ Accounts, organizations and users
Your user identity, account membership and organization membership are separate resources. Choose the context you intend to manage before making a request.
📄️ HTTP load balancers, groups and routes
An HTTP load balancer contains application groups, domains and ordered routes. Groups provide settings that routes can override.
📄️ Upstream groups and origins
An upstream group contains the origins that can serve your application. An HTTP or L4 group selects an upstream group and backend port.
📄️ L4 load balancers
Use an L4 load balancer for TCP or UDP traffic. Its listener selects an upstream group without HTTP route matching.
📄️ Policies and evaluation order
Policies decide whether and how a selected HTTP request continues. A source allow policy and a WAF allow policy have different scopes.
📄️ Caching
Cache policies control whether HTTP responses are eligible for caching and how cached responses are used. A cache hit can serve a response without contacting your origin.
📄️ TLS and certificates
You can upload certificates or request issuance through ACME. Certificate issuance and certificate activation are separate stages.
📄️ How changes reach the edge
A saved change represents your desired configuration. It does not establish that every serving location uses that configuration.
📄️ Versions and concurrency
Use a version precondition when you update a resource that supports concurrency checks. This prevents an update based on stale state from overwriting a newer change.