Network
How revenexx delivers your API responses and your content — one origin in Germany, four points of presence in front of it, and the parts you configure.
revenexx runs on one origin in Germany with four points of presence in front of it. Which of the two answers a request depends only on the hostname:
api.revenexx.comis answered by the origin directly.- A domain you point at the edge with a CNAME — your storefront, your
/cdn/asset paths — is answered by the nearest point of presence, which terminates TLS, filters the request, caches the response, and reaches the origin only when it has to.
You do not choose a region and you do not provision anything. The only configuration in this section is a custom domain: one DNS record, and the edge is in front of it.
Topology and delivery
- Edge network The four points of presence, the single origin in Germany, and how a request is routed to one of them.
- Endpoints The public hostnames you call, and which of them the edge fronts.
- Content delivery Serving your assets and storefront from the edge, under your own domain.
- Caching The two caches you can actually observe — the gateway response cache and the edge cache — and the headers that report them.
- Compression Brotli and Gzip on text responses, and the image formats you can request.
Security
- Transport Layer Security (TLS) Every endpoint is HTTPS-only. Certificates are issued and renewed for you.
- DDoS mitigation What is filtered before it reaches the origin, and what that does not cover.
- Web Application Firewall (WAF) Request filtering, bot mitigation, and rate limiting at each point of presence.
Custom domains are configured in Cockpit, not over the API. The record to create and the verification flow are documented in Domains.