Streaming & media
The True Cost of Cloud Egress Fees for Broadcasters and MAM
Build a storage budget around archive reads, proxy generation and recovery, and compare metered transfer with Gloman’s no-egress-fee storage.
Follow every copy of the video
A Media Asset Management (MAM) system does more than store master files. Editors retrieve footage, workers generate proxies, partners receive exports and backup jobs copy archives. The same asset can cross a billable boundary several times while its stored size remains unchanged.
Build the budget from a month of real activity. Separate uploads, archive reads, proxy reads, exports and recovery tests. Identify where each processing worker runs and where each transfer ends.
Separate storage, retrieval and transfer
Amazon S3 pricing separates stored capacity, requests and data transfer, with additional dimensions for some features and storage classes. Transfers to some AWS destinations are exempt from S3 transfer charges. Delivery through another service can still have its own bill.
Google Cloud Storage also distinguishes capacity, operations, retrieval and network transfer. Region, destination and storage class affect the result. Some colder classes introduce minimum storage durations and retrieval charges. Read the applicable regional tables before assigning a price.
A transparent cost model for archive activity
For illustration, suppose monthly activity includes 12 TB of editor downloads, 6 TB of off-platform proxy processing and a 2 TB recovery test. If all three cross the same billable boundary, that is 20 TB of outbound transfer. These are example workload volumes, not customer figures.
In decimal units, 20 TB is 20,000 GB. At a flat applicable rate P per GB, the transfer component is 20,000 × P. For a tiered tariff, apply each tier and allowance separately. Reconcile GB versus GiB, currency and tax before comparing quotes.
| Component | Metered storage provider | Gloman proposal |
|---|---|---|
| Stored capacity | Capacity × applicable storage-class rate | Quoted capacity and redundancy |
| Outbound transfer | Billable volume × applicable rates | No egress fees |
| Reads and retrieval | Requests and any class-specific retrieval fees | Confirm included operations and any other charges |
| Recovery and processing | Restore charges, compute and transfer where applicable | Confirm recovery capacity, compute and connectivity separately |
What no egress fees changes
Gloman Cloud Storage offers S3-compatible access with no egress fees. This removes the outbound-transfer line item from the storage comparison and can make frequent archive use easier to budget. It does not make storage, compute or every connected service free.
Ask for capacity, request handling, available throughput, access locations and support scope in writing. Zero egress pricing does not mean infinite bandwidth. Measure how long a large restore takes while the production system is also reading data.
For your MAM, verify the S3 operations it actually uses, including multipart uploads, presigned access and metadata handling. API compatibility should be tested against the application rather than treated as a guarantee that every provider feature is identical.
Choose by access pattern and recovery needs
An archive that is rarely read may justify a cold tier if its restore delay fits the business. An active production library benefits from predictable access costs and short retrieval times. Keep editing proxies close to the editors and avoid moving full-resolution masters when a smaller derivative is sufficient.
Compare retention, independent backups, security controls and staffing alongside the bill. Use encrypted connections and confirm encryption at rest and access permissions. Finally, include the cost and time to export the library if you change provider.