AWS Elemental on Wednesday introduced Secure Packager and Encoder Key Exchange (SPEKE), a new open API spec geared toward standardizing encryption key exchanges between DRM platforms and encryptors.
Within SPEKE, encoders, transcoders and origin servers use a standardized method for obtaining encryption keys from DRM platforms before embedding security and sending content downstream. The company said this can save money and time, doing away with the need for custom APIs for each DRM solutions provider and each encryptor.
AWS Elemental said SPEKE-enabled key servers or encryptors can be used in on-premises, in the cloud or in hybrid infrastructures, and that SPEKE is designed for both live and on-demand media workflows.
SPEKE is built on the DASH Industry Forum’s Content Protection Information Exchange Format (CPIX) standard for key exchange. The API specification supports HLS, MSS and DASH packaging as well as standard DRM platforms including Apple FairPlay Streaming, Microsoft PlayReady, Google Widevine, AES-128, and proprietary DRMs.
AWS Elemental said that multiple APN partners are already using SPEKE, including AWS, Axinom, castLabs, EZDRM, INKA Entworks, Insys Video Technologies, Intertrust Technologies, Irdeto, Kaltura, NAGRA, NEXTSCAPE, Verimatrix, Viaccess-Orca, VUALTO and WebStream.
“SPEKE is an exciting development for our industry. Building on the CPIX API, it further improves operational efficiencies and reduces both the time and costs involved in launching OTT services,” said Will Law, founding board member and vice chairman of DASH Industry Forum.
“Prior to SPEKE, integration required a custom API tailored to each DRM solutions provider and each individual encoder, transcoder, and packager,” said Michael Callahan, head of media solutions marketing at AWS Elemental, in a statement. “This often resulted in delayed new service launches for customers. SPEKE simplifies DRM integration to a single secure API. Any SPEKE-enabled DRM key server works with any SPEKE-enabled encryptor out of the box without the need for proprietary integration.”