A CDN resource is the configuration that connects one or more domains to one or more origins and defines how delivery behaves: caching, access control, headers, TLS, logging, and security. Domains that need different settings need separate resources. Almost every delivery decision later in this documentation is a property of a resource.
This page explains the model behind the control plane described on the CDN platform page, and how to choose the right delivery mode for adult video, live, and website traffic.
The three delivery modes
| Mode | What you bring | What the edge does | Best for |
|---|---|---|---|
| Standard CDN | A website, API, or prepared assets | Caches and serves HTTP content, applies access and security policy | Portals, APIs, thumbnails, downloads |
| Video CDN | Prepared HLS, DASH, MP4, or FLV | Caches and distributes prepared video, honours byte ranges, protects origin | Tube and VOD libraries, live streams you already package |
| Managed streaming | A raw contribution feed | Ingests, transcodes, packages, and delivers, with recording and DVR | Live-cam and creator platforms that do not want to run a media pipeline |
Choose standard delivery when your media stack already produces playable output. Choose managed streaming when you want ingest and transcoding handled for you. The two are complementary: most adult platforms run website and API traffic on standard delivery and video on video delivery, then add managed streaming only for the live or adaptive-bitrate paths that need it.
Origins and origin groups
An origin is where the edge fetches content on a cache miss. You can point a resource at a single origin, or define an origin group with a primary and one or more backups so a failing origin does not become a viewer-facing outage. Common origin patterns for adult platforms:
- Object storage holding packaged media, originals, and derivatives.
- A private origin that only accepts requests from edge addresses, so it cannot be scraped or attacked directly.
- An origin group with a warm standby, used during deploys or storage migrations.
Keep origins private. If your origin is reachable from the public internet, caching and security at the edge can be bypassed entirely.
Domains and TLS
A resource serves a primary domain and optional aliases. Issue or attach a TLS certificate per domain, force HTTPS, and choose the minimum acceptable TLS version. HTTP/3 and HTTP/2 are negotiated automatically for supported clients. Prefer a dedicated certificate per brand so a shared certificate never leaks one property’s identity into another’s.
What to decide before you configure
- Traffic class. Website and API, prepared video, live, or a mix.
- Origin architecture. Single origin, origin group, or object storage, and how the origin is protected.
- Cache strategy. Which bytes are cacheable, for how long, and keyed on what. See Cache control and cache keys.
- Access model. Public, signed, token-gated, geo-restricted, or a combination.
- Failure behaviour. What the edge serves when the origin is unhealthy, and how misses are collapsed. See Origin shielding and failover.
- Observability. Which logs you export and which metrics you alert on.
Where AdultInfra fits
The platform exposes these controls directly and AdultInfra tunes them for adult workloads: range-heavy seeking, long-tail catalogues, volatile live concurrency, and origin-egress cost. If you are deciding whether a controlled test is worth it, start with Adult video CDN and bring one hostname and the metric you want to improve.