Experience Cloud Flow Video Infrastructure

MK.IO OTT Integration — Add Apps, Subscriptions & Monetization on top of MK.IO

Processing and delivering video with MK.IO? Enveu adds the OTT business layer — branded apps, subscriptions, a no-code CMS, and monetization — plus automated MK.IO ingest and delivery via Flow.

In Experience Cloud In Flow

Experience Cloud

MK.IO for OTT platforms

Built for MK.IO customers who need a full OTT business

☁️

Teams migrating off Azure Media Services

Need an AMS-style processing/delivery backend (MK.IO) plus a full OTT front end.

📺

Broadcasters & VOD platforms

Need packaging and DRM at scale with branded apps and monetization.

⚽

Live & event streaming

MK.IO live processing plus Enveu fan apps, PPV, and Live-to-VOD.

🚀

OTT scale-ups

Want managed media services without building the platform layer.

About MK.IO

MK.IO (by MediaKind) is a cloud media platform for encoding, packaging, DRM, and streaming delivery — a modern, API-first successor to Azure Media Services. Enveu works on top: MK.IO handles media processing and delivery; Enveu adds the OTT experience and business layer — branded apps, CMS, subscriptions, monetization, and analytics.

EncodingPackaging (HLS/DASH)DRMStreaming deliveryAPI-firstAMS successor

How MK.IO + Enveu works

MK.IO processes and delivers; Enveu adds the OTT platform on top.

Process with MK.IO

Encode, package (HLS/DASH), and apply DRM to your content.

Ingest into Enveu

Enveu references the packaged outputs — no duplicate processing.

Manage & design

Metadata, access rules, and no-code apps in Experience Manager.

Deliver & play

Enveu apps stream the MK.IO-packaged content across devices.

Monetize & measure

Enveu enforces subscriptions and entitlements and adds business analytics.

What Enveu adds on top of MK.IO

No-code OTT UI builder (Experience Manager)
Multi-platform app management — 15+ devices
SVOD / TVOD / AVOD / PPV / Hybrid monetization
Subscriber lifecycle & entitlement management
Content CMS with metadata & scheduling
DRM, geo-rules & access control
Business analytics & subscriber insights

Android MobileiOS & iPadOSWeb BrowserAndroid TVApple TVSamsung Smart TVLG webOSAmazon Fire TVRoku

Why MK.IO customers add Enveu

Managed media processing (MK.IO) with a complete OTT platform (Enveu) around it.
Adaptive bitrate packaging (HLS & DASH) delivered inside fully branded apps.
DRM-protected delivery (MK.IO) with Enveu entitlements, geo-rules, and access control.
A clean path off Azure Media Services — MK.IO for processing, Enveu for the experience.
Live, VOD, and Live-to-VOD across web, mobile, and connected TV.
No-code operations — manage content, schedules, and layouts without engineering.

Frequently asked questions

What is MK.IO + Enveu?

Processing and delivering video with MK.IO? Enveu adds the OTT business layer — branded apps, subscriptions, a no-code CMS, and monetization — plus automated MK.IO ingest and delivery via Flow.

What does MK.IO do in the Enveu stack?

MK.IO handles encoding, packaging, and DRM; Enveu handles apps, CMS, subscriptions, monetization, and analytics.

Is MK.IO a replacement for Azure Media Services?

MK.IO (by MediaKind) is a modern, API-first successor to Azure Media Services for media processing and delivery.

What formats are supported?

HLS and MPEG-DASH adaptive bitrate streams, with DRM.

Does it support Live and Live-to-VOD?

Yes — MK.IO processes live, while Enveu manages playback, access, monetization, and Live-to-VOD publishing.

Which devices can I launch on?

Web, Android, iOS, and connected-TV platforms from a single Enveu codebase.

Flow

MK.IO as a Flow plugin

Best forConnecting MK.IO transcoding and packaging into automated ingest, processing, and delivery workflows for OTT platforms.

Manage media assets, trigger encoding jobs, and automate publishing workflows with MK.IO. Use in Live to VoD and Content Migration workflows for cloud-native media processing.

Inputs & outputs

Inputs

Source asset URLFile to submit for transcoding or packaging

Transform presetTranscoding profile or packaging configuration

Output storageDestination storage for transcoded outputs

Outputs

Output asset URLsURLs of transcoded renditions in configured formats

Job statusTranscoding job completion status and error details

Triggers & actions

Triggers

Job completedFires when a transcoding or packaging job finishes in MK.IO

Job failedFires when a processing job errors — triggers error handling or retry workflow

Actions

Create jobSubmit a transcoding or packaging job with a configured preset

Get job statusPoll the status of an in-progress transcoding job

List assetsEnumerate media assets in your MK.IO environment

Delete assetRemove a processed asset from MK.IO storage

Example workflow

Source asset uploadedStorage trigger

→

Submit transcode jobMK.IO action

→

Poll job statusMK.IO action

→

Upload outputAmazon S3

→

NotifySlack

Used in these workflows

Works well with

Frequently asked questions

How does Flow connect to MK.IO?

Flow connects to MK.IO using your Subscription Name, API Token, and Storage Account Name, stored securely in the Flow vault.

Can Flow create encoding jobs in MK.IO automatically?

Yes. Flow can submit encoding and packaging jobs to MK.IO as a workflow action. The job configuration - transform, output format, and storage destination - is defined in your workflow settings.

Can Flow generate MK.IO streaming locators as part of a workflow?

Yes. Flow can create streaming locators for MK.IO assets and return the playback URL for use in downstream steps such as CMS publishing or notification.

Does Flow support MK.IO asset triggers?

Yes. The MK.IO plugin supports asset created and job completed triggers, allowing workflows to fire automatically when new content arrives or processing finishes.

Launch with Enveu + MK.IO

See how Enveu works with MK.IO to power and automate OTT at scale.

Talk to an expert View all integrations