Content delivery (CDN)

revenexx runs its own content delivery edge. Your storefronts and your Storage assets are served from points of presence close to your users, with caching and TLS handled for you. The platform and your data are hosted in the EU; the edge then delivers cached content globally for speed.

You don't set any of this up. Point your domain at the edge and the nearest location fronts it automatically.

What you get

• Global edge, EU origin. The origin and your data live in the EU. Content is cached at edge locations on several continents, and each request is routed to the nearest healthy one — with automatic failover if a location is unavailable.
• Automatic caching and TLS. When your domain points at the edge (via a CNAME), the edge terminates TLS, issues the certificate, and caches static content for you. Everything else passes straight through to the platform.
• Asset and image delivery. Files in Storage are served from your own domain under /cdn/…, cached at the edge and transformed on the fly. See Storage for upload and image transforms.
• Resilient by default. Cached assets keep being served during a brief origin hiccup or while a cache entry refreshes in the background, so delivery stays up through transient issues.

Cache behaviour you can rely on

• Asset responses under /cdn/ are edge-cached for a short window (about an hour) and refreshed automatically in the background.
• Every edge response carries an X-Edge-Cache header reporting the cache result (HIT, MISS, …) — handy when you're debugging what's cached.
• Static assets are served compressed, close to the user, over TLS.

EU hosting

The platform and your tenant data are hosted in the EU. The edge caches and delivers your content globally so users everywhere get it fast; it doesn't move your tenant data out of the platform. If you have specific data-residency requirements, talk to us.