Skip to content
Media & Content Delivery

Media Cloud, Storage & Processing

S3-compatible media storage, live and file transcoding, HLS/DASH packaging, multi-DRM and asset management on a media-optimised cloud that sits next to our CDN and contribution network.

Media Cloud, Storage & Processing - Dollu
  • 4K HDR

    Live and file transcoding

  • HLS + DASH

    CMAF packaging, multi-DRM

  • 1.4 Tbps

    Backbone to CDN and edge

Overview

What is Media Cloud, Storage & Processing?

Media workflows are bandwidth-heavy, latency-sensitive and bursty, and general-purpose cloud regions are often the wrong place for them: egress fees punish distribution, encoders sit far from the CDN and archives are priced for databases, not petabytes of mezzanine files. Dollu’s Media Cloud, Storage & Processing service is a purpose-built platform, deployed in our PoPs in London, Frankfurt, Amsterdam, Ashburn, Mumbai and Singapore, where storage, compute and the CDN edge share the same 1.4 Tbps backbone, so content moves from ingest to viewer without crossing an internet boundary or an egress invoice.

Storage is S3-compatible object storage with hot, warm and archive tiers, lifecycle policies and versioning, designed for large sequential media objects and parallel multipart uploads from contribution links, cameras and post-production systems. Files can be pushed over HTTPS, Aspera- and Signiant-compatible accelerated transfer, SFTP or directly from our video contribution and live event connectivity services. Data is replicated across availability zones within a region and optionally across regions, with immutable buckets for compliance archives and residency options for content that must stay in India, the EU or the US.

Processing runs next to the storage. File transcoding pipelines produce ABR ladders in H.264, HEVC and AV1 with loudness normalisation, subtitle and audio-track handling, thumbnails and QC reports; live transcoders take SRT, RIST, RTMP or SDI-over-IP contribution feeds and generate multi-bitrate outputs with sub-second processing latency. A just-in-time packager delivers HLS, DASH and CMAF with low-latency variants, server-side ad insertion markers and Widevine, PlayReady and FairPlay DRM, and pushes origin to our content delivery network or any third-party CDN. Edge processing nodes at CDN PoPs handle regional packaging, watermarking and manifest manipulation close to viewers.

The platform is operated through a media asset management layer and APIs. Metadata, rights windows, proxies and versions are searchable in the MAM; workflows such as ingest, transcode, QC, package, publish and archive are defined as templates and triggered by API, watch folder or event. Everything, from bucket creation to a transcode job to a DRM licence policy, is exposed over REST with webhooks for job status, so broadcasters, OTT platforms, sports leagues and enterprises can automate end to end. Pricing is per stored terabyte, per processed minute and per delivered gigabyte, with no charge for moving content between storage, processing and our CDN.

Why Dollu

Why choose Dollu for media cloud & storage.

The advantages of buying from a carrier that owns its network, interconnects and operations - rather than a reseller.

  • Cut distribution cost at the source

    Storage, processing and CDN origin share one backbone, so there are no egress charges between them and content leaves the platform only once, at the edge, to viewers.

  • Publish faster

    Ingest-to-live pipelines with parallel transcoding and just-in-time packaging turn a delivered master into a playable, DRM-protected ABR stream in minutes rather than hours.

  • Store petabytes without surprises

    Predictable per-terabyte pricing across tiers, lifecycle automation to archive and immutable buckets for retention give finance and compliance teams a clear model.

  • Protect premium content end to end

    Multi-DRM, token-secured playback, forensic watermarking at the edge and encrypted transfer and storage cover rights obligations from contribution to screen.

  • Automate rather than operate

    Workflow templates and APIs replace manual hand-offs between ingest, edit, QC and publish, and integrate with existing MAMs, playout and OTT back-ends.

Capabilities

Capabilities in detail.

Everything included with Media Cloud, Storage & Processing - the platform features, options and controls you get from day one.

  1. 01

    Media object storage

    S3 API-compatible buckets with multipart parallel upload, versioning, lifecycle rules, object lock, cross-region replication and per-bucket residency; hot, warm and archive tiers with defined retrieval times.

  2. 02

    Accelerated ingest

    HTTPS, SFTP, UDP-accelerated transfer compatible with Aspera and Signiant, S3 sync from third-party clouds and direct hand-off from Dollu contribution circuits and live event connectivity.

  3. 03

    File transcoding

    H.264, HEVC and AV1 ABR ladders, per-title encoding, HDR10 and HLG, Dolby and AAC audio, loudness normalisation, closed captions and subtitle conversion, thumbnails, sprites and automated QC reports.

  4. 04

    Live transcoding

    SRT, RIST, RTMP and SMPTE ST 2110 or 2022-6 inputs, redundant encoders, multi-bitrate outputs to 4K, SCTE-35 passthrough, slate insertion and failover to backup sources.

  5. 05

    ABR packaging and origin

    Just-in-time HLS, DASH and CMAF packaging, low-latency HLS and DASH, time-shift and catch-up windows, SSAI marker handling and a highly available origin fronting our CDN or any third-party CDN.

  6. 06

    Multi-DRM and content protection

    Widevine, PlayReady and FairPlay licence services with key rotation, offline licences, tokenised playback URLs, geo and concurrency rules and edge forensic watermarking.

  7. 07

    Media asset management

    Searchable metadata, proxies, rights windows, collections and version history; role-based access; connectors to broadcast MAM, playout and OTT CMS platforms.

  8. 08

    Edge processing

    Regional packaging, manifest manipulation, watermarking and image or thumbnail transformation at CDN PoPs, reducing origin load and viewer start-up time.

  9. 09

    Workflow APIs and automation

    REST APIs and SDKs for storage, jobs, packaging and DRM policy; watch-folder and event triggers; webhooks for job status; templates for ingest-to-publish and archive workflows.

How it works

How it works.

From first conversation to live traffic - a tracked, engineer-led onboarding with a named owner at every step.

  1. Step 01

    Design the pipeline

    We map your sources, formats, target players, DRM requirements, retention rules and regions, then define buckets, transcode profiles and packaging templates.

  2. Step 02

    Connect and migrate

    Ingest paths, contribution circuits and third-party cloud sync are set up; existing libraries are migrated with checksum verification and metadata mapping into the MAM.

  3. Step 03

    Test and publish

    Sample assets and live feeds run through the full pipeline; playback, DRM and CDN delivery are verified on target devices before you go live.

  4. Step 04

    Operate and scale

    Run workflows by API or template, monitor jobs and delivery in the portal, and let lifecycle rules move content between tiers while our 24×7 NOC watches the platform.

Use cases

Who uses this and why.

Typical deployments across carriers, enterprises, platforms and contact centres.

  • Broadcasters and news organisations

    Central archive with proxies and metadata, fast-turnaround transcoding for digital publishing and live channel packaging for OTT simulcast.

  • OTT and streaming platforms

    Full VOD and live pipeline with per-title encoding, multi-DRM and origin next to the CDN, cutting egress and start-up time.

  • Sports leagues and event producers

    Contribution feed ingest, live transcoding and packaging with SCTE-35 markers, plus instant clip creation and archive for highlights.

  • Enterprises and education

    Secure storage and streaming of training, town halls and lecture capture with SSO-protected playback and long-term retention.

  • Post-production and studios

    Accelerated transfer of mezzanine files, review proxies, immutable masters and multi-region replication for distributed teams.

Specifications

Technical & commercial specifications.

Key parameters at a glance. Ask us for the full service description and SLA document.

Storage APIS3-compatible; multipart, versioning, object lock, lifecycle, replication
Storage tiersHot, warm, archive; immutable compliance buckets
IngestHTTPS, SFTP, UDP-accelerated (Aspera/Signiant compatible), S3 sync
File codecsH.264, HEVC, AV1; HDR10, HLG; AAC, Dolby; captions and subtitles
Live inputsSRT, RIST, RTMP, SMPTE ST 2110 / 2022-6; SCTE-35 passthrough
PackagingHLS, DASH, CMAF; low-latency variants; time-shift; SSAI markers
DRMWidevine, PlayReady, FairPlay; token auth; forensic watermarking
RegionsLondon, Frankfurt, Amsterdam, Ashburn, Mumbai, Singapore
PricingPer TB stored, per minute processed, per GB delivered; no internal egress
Support24×7 NOC; P1 response ≤ 15 min; named account manager
Pricing model

How Media & CDN is priced.

CDN and media delivery are priced on delivered traffic - per GB or committed Mbps; contribution circuits and live events per event or per month; processing per output minute.

We publish the model, not a public rate card - actual rates depend on destination, route class, volume and regulatory cost. See how every Dollu service is priced.

Per GB or per Mbps · per event
  • CDN per GB delivered or committed Mbps at the 95th percentile
  • Contribution circuits per event or monthly
  • Media processing per output minute
  • Committed-traffic discounts
Billing
Monthly in arrears on delivered traffic; events invoiced per booking
Commitment
None on usage; committed traffic on 12–36 month terms for the best rates
Talk to salesActual rates within one business day.
FAQ

Media Cloud & Storage - your questions answered.

The questions customers and carriers ask us most often before they interconnect. If yours is not here, our team answers within one business day.

Still have a question?

Ask our solutions team

Yes. The object storage exposes the S3 API, so AWS CLI, SDKs, rclone, MAM connectors, NLE panels and backup tools work with a change of endpoint and credentials. Bucket policies, presigned URLs, multipart upload, versioning and object lock behave as you would expect, and we publish the list of supported API operations.

Let’s talk

Move your media pipeline next to the network.

Tell us your library size, monthly processing hours and target platforms and we will model storage, processing and delivery costs against your current setup.

Abstract globe with connected network lines