Introduction

These concepts apply to MK.IO as a whole. It is useful to have a general understanding of these when redeeming a direct sale with MK.IO or creating and managing projects on the platform.

Organisations

An organization in MK.IO is the highest level container. Users (via user accounts), payment methods and projects are all associated with the organization. You can think of it like a “tenant” in platforms such as Azure. While a user can belong to multiple organizations, each payment method and project belongs to only one organization.

Payment methods

A payment method defines how you pay MediaKind for the MK.IO services you use. There are two main types, marketplace and direct sale. An organization can have more than one payment method. For example, you might want to use a direct payment method to pay MediaKind up-front for MK.IO Beam contribution channels, but use a marketplace payment method to draw down your cloud-committed usage for your streaming workflows.

Projects

A project is a container that holds your media objects, assets, live events, devices, and more. Projects must be associated with a single payment method. You can also specify which cloud region any MK.IO cloud services you use will run. With our flexible RBAC (role-based access control) system, you can restrict user access to specific projects based on the teams you define.