Edge delivery for large static assets
CDN Core caches immutable files — build artefacts, 3D scene bundles, texture sets and application packages — close to the people who download them. Built for teams that push multi-gigabyte releases several times a day and don't want to pay hyperscaler egress.
What we serve
| Build artefacts | Content-addressed archives, container layers and installer packages. Content addressing
means a file never changes at a given path, so immutable caching is safe. |
| 3D and scene bundles | glTF and USD scene sets, texture atlases, lightmaps and baked geometry for rendering and visualisation pipelines — typically 200 MB to 4 GB per release. |
| Application packages | Desktop auto-update payloads and firmware images with byte-range support, so resumable downloads survive unstable links. |
| Dataset mirrors | Scheduled mirrors of public datasets and model weights: pulled from origin, verified by checksum, then served from cache. |
How it behaves
| Anycast and DNS steering | Requests go to the closest healthy node; health checks run every 30 seconds. |
| Range requests | Resumable and multi-part downloads are first-class: 206 with a correct
Content-Range for every object above 1 MB. |
| Origin shielding | Nodes fetch through a shield, so a cold object costs one origin request, not one per node. |
| Invalidation | Tag-based, propagated to all nodes in under 60 seconds. Content addressing makes it rarely necessary. |
Network
- Stockholm core
- Helsinki edge
- Tallinn edge
- Warsaw edge
- Frankfurt core
- Amsterdam edge
- Vienna edge
- Zurich edge
- London edge
Getting access
Access is by invitation while the public API is being finished. If you push large releases to a small audience and egress cost is the problem, write to ops@cdn-core.uk with rough monthly volume and region.