F-01
200+ edge locations
Requests are answered from the location nearest to the visitor, which cuts the distance every download has to travel.
$ cd ../services
Global delivery
Edge Cache Drop
Upload once. Land everywhere.
Edge Cache Drop keeps copies of your most requested files on servers close to the people downloading them. Upload to your bucket one time and let more than two hundred edge locations carry the traffic, so big downloads start fast on any continent.
$ cloudeee edge enable assets --ttl 1d
~/services/edge-cache-drop
$ cloudeee edge-cache-drop --features
What you get.
F-02
Cache warmup
Pre-load a new release to the edge before you announce it, so the first wave of downloads is already fast.
F-03
Rules by path
Set different lifetimes for different folders: long for static assets, short for files that change often.
F-04
Instant purge
Replace a file and clear it from every location by exact path or wildcard, usually within seconds.
F-05
Resumable downloads
Range requests let players seek and let interrupted downloads continue from where they stopped.
F-06
Delivery analytics
Track bandwidth, cache hit rate and top files per location to see what your audience actually downloads.
$ cloudeee edge-cache-drop --how
Four steps, zero fuss.
Step 01
Point at a source
Choose a Pixel Bucket or a workspace folder as the origin. Files stay stored exactly where they are.
Step 02
The edge pulls and caches
On the first request, the nearest location fetches the file from the origin and keeps a copy for the lifetime you set.
Step 03
Visitors download nearby
Everyone after that is served from a nearby cache over a modern, encrypted connection.
Step 04
Purge or refresh
Update a file, purge its path and the new version is picked up everywhere on the next request.
$ cat specs.txt
The specs.
~/services/edge-cache-drop/specs.txt
| Edge locations | 200+ |
|---|---|
| Purge | Exact path or wildcard, in seconds |
| Protocols | HTTP/2 and HTTP/3 |
| TLS | Automatic certificates |
| Cache control | TTL and stale-while-revalidate |
| Origin | Any Cloudeee bucket or workspace folder |
$ man edge-cache-drop
Quick answers.
Q01Does caching mean my files are stored in more places?
> Edge locations hold temporary cached copies for the lifetime you set. Your authoritative files stay in your Cloudeee storage, and cached copies disappear when they expire or are purged.
Q02Can I cache private files?
> Yes, with signed URLs. The edge checks the signature before serving, so only people holding a valid link can download.
Q03How fast does a purge take effect?
> Purges propagate across the network in seconds. After that, the next request fetches a fresh copy from your origin.
$ cloudeee signup --free
Start with Edge Cache Drop.
Create a free account, get 20 GB of encrypted storage and try it in minutes.