How it works
Requests hit the nearest edge PoP. On a cache miss the edge fetches from your origin, caches the response per your rules, and serves the next request locally.Core concepts
| Concept | What it is | Where to configure |
|---|---|---|
| Distribution | A configured CDN endpoint mapped to one or more origins. | Create distribution |
| Origin | The upstream your distribution pulls from (HTTP, S3, custom). | Origins |
| Cache rule | Per-path TTL, query-string handling, compression. | Cache rules |
| Access rule | Country / IP / referrer / token gate per path. | Access rules |
| Header rule | Add / remove request and response headers. | Headers |
| Purge | Invalidate cached content by path or pattern. | Purge |
Why Tenbyte CDN
- Smart routing — anycast plus health checks pick the nearest healthy edge.
- Global PoPs — many points of presence per region.
- Edge customization — cache, headers, and access policies as code via the API.
- Secure by default — TLS, WAF integration, and token-authenticated signed URLs.
- Real-time analytics — bandwidth, requests, cache-hit ratio, response classes.
- HTTP/2 and HTTP/3 — multiplexed, lower-handshake delivery.
- Instant purge — invalidate cached content via console or API.
- Pay-as-you-go — usage-based billing, no minimums.
What developers get
- REST API — manage distributions, rules, and purges. See the CDN API reference.
- OpenAPI spec — generate clients for your stack.
- Webhooks — react to purge, certificate, and traffic events.
- Signed URLs — protect content with time-limited tokens. Token authentication.
- Headers control — add
Cache-Control,CORS, and security headers at the edge.
Getting started
Create a distribution
Point a distribution at your origin. Create distribution →