Media & Content
Media assets grow faster than anything else in your system, and the biggest cost is usually not storage but egress. Object storage with an integrated CDN keeps a file once and serves it from the point nearest the viewer, with no separate setup.
A Real Story
How this runs in production
Kabar Pagi publishes 200 articles a day and holds 40 TB of video. Its largest bill was never storage — it was egress, because every playback pulled from a single origin in Jakarta.
Assets moved to object storage with a CDN that is live the moment the bucket exists. Readers in Makassar stopped pulling files from Jakarta, and the transcoding queue moved to two instances that only run when there is work.
- lower egress cost
- 62%
- median load time
- 1,2 dtk
- of assets served
- 40 TB
We spent a year optimising images. What finally cut the bill was to stop serving everything from one city.
Reference Architecture
Exactly what they run
The plan names below are the same ones listed on the pricing page.
- Object Storage40 TB + CDNCDN on with no separate configuration.
- Virtual Machines4.large × 2Transcoding queue, up only when there is a job.
- Block Storage400 GB NVMeRender scratch disk, detached when done.
What You Get
Built for this workload
CDN with no setup
Global distribution is on the moment the bucket exists.
Presigned URLs
Share temporary access without opening the bucket.
Lifecycle policies
Move old archives to a cheaper tier on a schedule.
Built From