CacheVaultCDN

Edge caching & static asset delivery

Edge caching that does exactly what your headers say.

CacheVault is a small, independent CDN for static assets. We cache images, scripts, stylesheets, fonts and downloads close to your visitors, terminate TLS at the edge, and keep repeat traffic off your origin.

Talk to us How it works
  • HTTP/2 & HTTP/3-ready
  • TLS 1.3
  • Purge API
  • Origin shielding
response headersedge · cache hit
$ curl -sI https://static.example.com/app.9c1e.jsHTTP/2 200content-type: text/javascriptcache-control: public, max-age=31536000, immutableetag: "9c1e4f2a"age: 3187x-cache: HITalt-svc: h3=":443"; ma=86400$
Illustrative response. We cache what your origin marks as cacheable, for as long as it says.

01What we do

A fast cache between your origin and everyone else.

Most of what a website sends is the same for every visitor: images, bundles, stylesheets, fonts, downloads. There's no reason for each of those requests to travel back to your server.

We keep copies of those files at our edge locations and answer requests there. Your origin is asked only when a file is missing or has expired — and then only once.

That's the whole product. We don't run your code, rewrite your pages or sell you a suite of add-ons. We deliver static files, quickly and predictably.

Request pathGET /img/hero.avif
  1. VisitorRequests a file over HTTP/2 or HTTP/3.
  2. Edge HITIf the file is cached, it's served from the nearest edge node and the request ends here.
  3. Shield MISSEdge misses share one upstream cache, so duplicate fetches collapse into one.
  4. OriginFetched once, then cached for as long as your headers allow.

02How it works

Up and running in three steps.

No agents to install and no configuration language to learn. If you can edit a DNS record, you can use CacheVault.

  1. Point a hostname

    Create a CNAME — for example assets.yourdomain.com — to the edge hostname we give you. We issue the TLS certificate and renew it automatically.

  2. Keep your cache rules

    We follow Cache-Control, ETag and Last-Modified from your origin. Need something different for one path? We'll set an override with you.

  3. Deploy and purge

    Ship a release, then purge by URL, by path prefix or for a whole hostname through the API. Fingerprinted filenames don't need purging at all.

03Features

A short list, done properly.

We keep the feature set small on purpose, and make each part behave the way the HTTP specifications say it should.

  • Static asset caching

    Images, JavaScript, CSS, fonts, media segments and file downloads. We honour standard HTTP caching headers, including stale-while-revalidate and stale-if-error.

  • TLS at the edge, HTTP/2 and HTTP/3-ready

    Connections terminate close to the visitor with TLS 1.2 and 1.3 and automatically managed certificates. HTTP/2 by default, with HTTP/3 over QUIC ready for clients that support it.

  • Cache purge API

    A small HTTP API with scoped tokens. Purge a single URL, everything under a path prefix, or an entire hostname when you deploy.

  • Origin shielding

    Edge misses are funnelled through a shield tier and concurrent requests for the same object are collapsed, so your origin sees one fetch instead of many.Business and Custom plans

  • Sensible defaults

    Brotli and gzip for text assets, byte-range requests for large files, correct Vary handling, and no rewriting of your content.

  • Clear usage reports

    Requests, bytes delivered and cache hit ratio per hostname, summarised monthly. They're the same numbers we bill from.

04Network

A modest network, run carefully.

We don't sell a map with hundreds of pins. We run a focused set of edge locations and add capacity where our customers' visitors actually are.

Current status

Health-checked
Every edge node is checked continuously. A node that stops answering correctly is taken out of rotation and traffic moves to a healthy neighbour.
Honest reporting
We don't publish marketing uptime figures. When something breaks, it goes on the status page and affected customers hear from us by email.
Reachable people
Network issues go to ops@cachevault.net, read by the engineers who run the edge.
Capacity first
We would rather decline traffic we can't serve well than oversubscribe the nodes our customers rely on.

05Plans

Simple, usage-based pricing.

You pay for the traffic we deliver — no seat fees and no bundles. Tell us roughly what you serve and we'll reply with a plain quote.

  • Starter

    For personal projects, documentation and small sites.

    Usage-based · contact us

    • A few hostnames
    • Caching driven by your headers
    • Automatic TLS certificates
    • Cache purge API
    • Email support
    Contact us

  • Business

    For production sites and apps with steady traffic.

    Usage-based · contact us

    • Everything in Starter
    • More hostnames
    • Origin shielding
    • Per-path cache overrides
    • Priority support from the ops team
    Contact us

  • Custom

    For large files, unusual traffic patterns or specific regions.

    Quoted per project

    • Large-file and download delivery
    • Dedicated capacity
    • Custom terms and invoicing
    • A direct line to the engineers
    Contact us

If we're not the right fit for your workload, we'll say so.

Tell us what you serve.

Send us your origin, rough monthly traffic and what you'd like to improve. Someone who works on the network will reply.

hello@cachevault.net