Overview of Dynamic Delivery

This topic provides an overview of Dynamic Delivery, Brightcove’s next-generation media delivery platform.

Delivering media to different devices — on desktop, mobile, and connected TVs — requires a mix of ever-changing technologies:

  • Audio and video codecs
  • Various types of packaging for streaming video
  • Various content protection schemes to protect content from being copied

Without the use of Dynamic Delivery, cross-platform streaming often requires storing the same content multiple times to support delivery to all your target platforms. Dynamic Delivery allows Brightcove customers to deliver media to a range of devices without the cost and operational overhead of re-packaging and storing content multiple times for every supported device and use-case. Dynamic Delivery creates the optimal content package just-in-time for delivery and streaming to all supported devices and use-cases. This also helps future-proof your delivery architecture as technology and your audience evolves.

With Dynamic Delivery, customers provide a single high-quality (mezzanine) video file. During the ingest process, we create several quality levels of this file suited to a range of different screen sizes and network conditions. When a viewer presses play, Beacon uses information about the requesting device to determine the type of streaming technology expected — for example, the type of stream packaging (HLS vs. DASH) (or MP4 if the device does not support any kind of HTTP streaming), the DRM required (e.g. Widevine, Fairplay, Playready), and ancillary content such as closed captions or alternate audio tracks. Dynamic Delivery then uses this information to deliver the appropriate content package (i.e. type of stream) for the requesting device in real-time.

Architecture overview

Dynamic Delivery Architecture
Dynamic Delivery Architecture
  1. When a source file is uploaded, the transcoding process will use the selected ingest profile to determine the set of renditions to create.
  2. Renditions are stored as a set of contiguous, fragmented MP4 files of various bit rates and resolutions that are agnostic of any specific delivery format.
  3. When a request is made for a video, the Dynamic Delivery process does Just-in-Time or JIT packaging, which means it will dynamically package content into the appropriate format based specified requirements. This packaging will take into consideration the specific delivery format needed, audio and caption tracks needed, as well as any encryption/DRM needed.
  4. When the playback device uses the manifest returned by the Playback API to request media to play, we perform just-in-time packaging on the fragmented MP4 files to provide the appropriate segment format, duration and encryption. These fragments are cached on a CDN so that video delivery is still highly performant.

The Dynamic Delivery process was designed to be a fully managed, cloud-based service. All the components run on cloud infrastructure in multiple regions to insure high availability, redundancy and scalability.

What video formats does Dynamic Delivery produce?

Dynamic Delivery produces the following sources as needed:

  • HLS (versions 3, 4, and 5)
  • Smooth
  • DASH
  • MP4 (if progressive renditions are specified in the ingest profile)

The following DRM-packagedrenditions are created (depending on what content protection your account is enabled for):

  • HLS + Fairplay
  • DASH + Widevine
  • DASH + Playready
  • Smooth + Playready

Migration process

As of Tuesday, October 17, 2017, all new Beacon accounts that are created are configured to use Dynamic Delivery by default. This includes trial accounts, accounts for new publishers, and new sub-accounts for existing publishers. With this change, all new publishers and trial customers will automatically benefit from all the features of Dynamic Delivery.

For existing customers, the migration is a two step process. First, new uploads are transitioned to utilize Dynamic Delivery (day forward migration) and second, existing content is migrated from the legacy delivery platform to Dynamic Delivery (back catalog migration.)

Day forward migration

The first step to moving to Dynamic Delivery is transitioning new uploads to utilize Dynamic Delivery. Enabling your account for Dynamic Delivery is a simple task that can be completed by Customer Support. There is no danger in enabling an existing Beacon account for Dynamic Delivery as it does not modify any existing content. Only content explicitly ingested to Dynamic Delivery will utilize the new system.

From a workflow perspective, a couple of things will appear differently inside Beacon Studio. First, when uploading videos using the Upload module, you will now see Dynamic Delivery ingestion profiles in your account.

Dynamic Delivey Profiles
Dynamic Delivery Profiles

The Media module will also display a green cloud icon (green cloud icon) next to video titles ingested using a Dynamic Delivery profile. Videos ingested using a legacy ingest profile will display a gray icon (gray cloud icon).

Media Module Video List
Media Module Video List

Additionally, the Video Sources panel in the media module will appear slightly different due to renditions being stored in a format agnostic state.

Functionally, everything else remains the same. You can upload via all the standard mechanisms (Beacon Studio, Dynamic Ingest API, CMS Connectors, etc.) and playback remains unchanged on all your standard playback devices.

Once a video has been ingested using Dynamic Delivery, if the video is re-transcoded, a Dynamic Delivery profile must be selected. If you want to use a legacy ingest profile, the video must be re-uploaded.

Back catalog migration

Once you have new ingests utilizing Dynamic Delivery, we can then migrate your back catalog. This can be done in one of two ways:

Transmux migration tool

The transmux migration tool moves Beacon content from legacy delivery to Dynamic Delivery without re-transcoding. This allows for you to migrate your content much faster and easier than re-transcoding content. As such, it should be the preferred method of migration for most customers. The transmux tool will transform the existing renditions in your account to be compatible with Dynamic Delivery. To migrate your content via the transmux tool, please contact your Customer Success Manager.


There are a few criteria that make a title ineligible to migrate via the transmux tool and as such will require that titles be re-encoded to migrate them. Titles will need to be re-encoded if:

  • You wish to utilize Context Aware Encoding
  • You wish to do mid-roll Server-side Ad Insertion (SSAI)
  • Your title does not have HLS renditions
  • Your title currently has DRM (HLSe is acceptable)

If you need to re-transcode titles, you will either need to manage that process on your own (following our best practices) or engage with your account team for paid migration services. Note: It is possible to transmux some titles within an account and re-transcode others.

Frequently asked questions

What is Dynamic Delivery?

Dynamic Delivery is a set of technologies that make Brightcove's next-generation media delivery platform. Dynamic Delivery is designed to address publisher's current and future requirements and will become the foundation for how all Brightcove products deliver media.

What are the benefits of Dynamic Delivery?

  • Greater flexibility and agility for delivery - Content is dynamically packaged for delivery to a number of endpoints (web browsers, smartphones, tablets, connected TVs and streaming boxes). Dynamic Delivery is designed to be capable of using multiple CDNs to deliver content, increasing customer choice.
  • Future proofing - Since content is dynamically packaged, Brightcove can add new formats on the fly. As a new version of HLS, DASH, etc., or even a new format comes out, we simply add support at the platform level and publishers can start using it without re-transcoding existing content.
  • Reduced storage footprint - Content assets are stored once and renditions are created downstream for delivery when needed instead of storing the content multiple times.
  • Enhanced performance through geographic distribution - Dynamic Delivery is designed for a regionally distributed, highly available architecture. Publishers benefit from improved playback performance and increased resiliency.
  • Integrated support for Server Side Ad Insertion (SSAI) - Dynamic Delivery will enable ads or other content to be inserted from the server. This provides a seamless playback experience for viewers and gives publishers increased resiliency against ad blockers, all from within Beacon.

Are there any pricing considerations with Dynamic Delivery?

No, access to Dynamic Delivery is included in every base platform license. Certain features of Dynamic Delivery including Server Side Ad Insertion (SSAI) and Context-Aware Encoding (CAE) are add-ons with costs associated. Check with your Customer Success Manager for details on pricing.

Does Dynamic Delivery support BYO CDN publishers?

Dynamic Delivery allows publishers to take advantage of their own CDN relationships; however, all video assets must be managed by the Brightcove Origin. Please contact your Customer Success Manager for more information.

What regions does Dynamic Delivery support for ingest and origin?

Dynamic Delivery supports ingestion and origin in the following AWS Regions:

  • us-east-1 (Virginia) - default for all accounts
  • eu-west-1 (Dublin)
  • ap-northeast-1 (Tokyo)
  • ap-southeast-1 (Singapore)
  • ap-southeast-2 (Sydney)

Note that there are cost implications when moving ingestion and origin to another region. Please contact your Brightcove Customer Success Manager for further information.

Are all Brightcove accounts on Dynamic Delivery?

Yes, all new publishers will be configured with Dynamic Delivery. All existing accounts have been migrated to Dynamic Delivery and and the legacy ingest system has been turned off.

Some of my HLS renditions have a higher bitrate (according to the CMS API) than what is specified in the ingest profile - why is that?

What is specified in the ingest profile is the video bitrate. What is reported by the CMS API is the video bitrate + the audio bitrate + a 10% overhead for Dynamic Delivery processing. So the bitrate returned by the CMS API will always be higher than what is specified in the ingest profile, unless the source video bitrate was lower than that.