FEATURES / CDN
/// CDN
Your Spaces, served from the edge — on your own domain.
Enable the DigitalOcean Spaces edge CDN per bucket, set cache TTL, and attach a custom domain with auto-provisioned managed TLS. Purge objects or prefixes on demand — all from Storafleet, no DigitalOcean console juggling.
Start for free/// How it works
Enable the CDN on a bucket
Pick a Spaces bucket and turn on the DigitalOcean Spaces edge CDN from Storafleet. Set the cache TTL that suits your content — short for frequently changing assets, long for immutable files.
Attach your custom domain
Point a CNAME at the CDN edge host and attach your domain in Storafleet. DigitalOcean auto-provisions a DNS-validated managed TLS certificate, so your assets serve over HTTPS on your own domain.
Serve, then purge on change
Object URLs now resolve through the CDN edge host and cache at the edge. When you publish new content, purge specific objects or prefixes so users get the update without waiting for the TTL.
Per-bucket CDN toggle
Enable or disable the DigitalOcean Spaces edge CDN for any bucket from Storafleet. No jumping into the DigitalOcean console — flip it on and your objects start serving through the CDN edge host.
Edge caching that you tune
Set the cache TTL per bucket so the Spaces CDN holds your objects at the edge for as long as you want. Faster delivery for large files, with stale-cache control in your hands.
Custom domain via CNAME
Attach your own branded domain to the Spaces CDN by pointing a CNAME at the CDN edge. Serve assets from cdn.yourdomain.com instead of a generic DigitalOcean Spaces hostname.
Managed TLS, auto-provisioned
DigitalOcean auto-provisions a DNS-validated HTTPS certificate for your custom domain. You get HTTPS on your own domain without generating, uploading, or rotating certificates by hand.
Targeted cache purge
Purge the CDN cache for specific objects or whole prefixes when you ship new content. No waiting out the full TTL — invalidate exactly what changed and let the rest stay cached.
Built for distributed audiences
Edge caching shortens the path between your files and geographically distributed users. International visitors pull large media and downloads from a nearer edge instead of the origin region.
/// Without Storafleet
Configuring the Spaces CDN means hopping into the DigitalOcean console: toggle the endpoint, wire up the CNAME, wait on certificates, and there's no convenient way to purge what you just changed.
- Enabling the Spaces CDN means digging through the DigitalOcean console per bucket
- Setting cache TTL is buried in endpoint settings, not where you manage objects
- Wiring a custom domain means a CNAME plus certificate setup you track manually
- Purging stale objects after a content update is awkward and easy to forget
- Object URLs default to a generic Spaces hostname, not your own brand
/// With Storafleet
Per-bucket CDN controls in one place. Enable the edge CDN, set TTL, attach a custom domain with managed TLS, and purge specific objects or prefixes — without leaving Storafleet.
- Enable or disable the DigitalOcean Spaces edge CDN per bucket with one toggle
- Set cache TTL right alongside the bucket you're already managing
- Attach a custom domain via CNAME; DigitalOcean auto-provisions DNS-validated TLS
- Purge specific objects or whole prefixes the moment you publish new content
- Serve object URLs through the CDN edge host on your own branded domain
/// When you'll use this
Serving site assets from a branded domain
Your static site loads images and downloads from a Spaces bucket, but the URLs are a generic DigitalOcean hostname and there's no edge caching. In Storafleet you enable the Spaces CDN, point cdn.yoursite.com at the edge via CNAME, and let DigitalOcean provision the TLS cert. Assets now serve over HTTPS on your own domain, cached at the edge.
Key featureCustom domain + auto-provisioned managed TLS
Speeding up large downloads for international users
Users in three continents pull multi-hundred-megabyte media files straight from your origin region and the wait times are brutal. You enable the Spaces edge CDN on the media bucket and set a long cache TTL. The first request warms the edge; everyone after that downloads from a nearer cache. Delivery times drop for your distributed audience.
Key featureEdge caching with tunable cache TTL
Shipping a content update without a full cache wait
You replaced a batch of images under the /assets/ prefix, but the CDN is still serving the old ones to the TTL's end. Instead of touching the DigitalOcean console, you open Storafleet, purge the /assets/ prefix, and the edge refetches from origin on the next request. New content goes live immediately while everything else stays cached.
Key featureTargeted cache purge by object or prefix
Your storage estate deserves a control plane.
Join the DevOps teams and founders who run every cloud's buckets from one control plane.
Free plan · No credit card · 50+ cloud providers · Cancel any time