What is the RDK stack?

To simplify the packaging, distribution and building of firmware, RDK is organized into four high-level components:

Generic RDK

The generic RDK includes source code and links to acquire open source / 3rd party components. It also includes instructions for creating SoC specific RDK and basic validation tools.

MVPD Platform

This section contains MVPD applications and proprietary software as well as components that are device and SoC independent.


Contains SoC specific changes/optimization and SoC software in addition to items in generic RDK. It also includes instructions for OEM integration and tools for basic validation.

OEM Firmware

This layer features optimized components for SoC specific RDK provided by the OEM. This includes OEM software for boot-up, image updates, and APIs to handle custom drivers.

The RDK software stack can be visualized in terms of increasing levels of specificity. At the top are the generic layers – Generic RDK and MVPD Platform Components – which vary in level of proprietary components. As you move down to the SoC layer, this stack contains software such as the SDK and SoC-level patches for the generic RDK and MVPD components. Further down the stack, you find OEM-provided firmware that is device-specific. These could be specializations to the generic or SoC components or complementary software components provided by the OEM to create a fully functional set-top device.

What is included in the RDK Code Releases?

The RDK includes over thirty software components that allow for patches for open source and third-party extensions. This package consists of:

Source Code Packages

Includes source code for all generic RDK components. Restrictions exist for access to RDK components requiring a special license.

Component Manifest

List of all RDK components, software versions, and access instructions.
RDK Porting Guide

RDK Porting Guide

Provides licensees step-by-step procedures to install, build, and integrate RDK.

Access to the RDK Wiki

Provides the latest information on RDK, release timelines, architecture documentation, tutorials, white papers, etc.

Click here to request a login account for RDK

Click here for licensing information

How often is RDK updated?

The generic RDK trunk is accessible via RDK-M CMF Gerrit and reflects the most recent contributions from both Comcast development and the community. On a periodic basis, the trunk is tagged and those tags are made available. The code will be built and tested by RDK-M CMF ahead of tagging and made available for download along with appropriate documentation including a readme, component manifest, user guides and test results. Community members can fetch the tagged code from RDK-M CMF Gerrit and work with it.

Has RDK been deployed?

Yes. RDK based devices have been deployed on more than five million devices.

How do I join RDK?

If your organization wishes to license RDK, click here to begin the process.
If your organization already licenses RDK, click here to request access to RDK wiki.

How do I get technical support and information on RDK?

To get more information on RDK, please license RDK if you have not already done so. Once you have a license, click here to access the RDK support site.

How do I get access to the RDK Wiki once I am licensed?

Once you have been notified that the agreement has been executed by RDK Management, RDK Support will send you a short questionnaire. The questionnaire MUST be completed. Once submitted you will receive your RDK Wiki user account information within 48 hours. RDK Wiki access is limited to authorized staff of licensee companies only.

How do I submit a potential security issue with the RDK code?

If you uncover what you believe to be a security gap in the RDK code you can submit a secure message to RDK Management by using the following link: https://rdkcentral.com/security-submissions/

Is the process of submitting a potential security issue with the RDK code secure?

Yes. Our security point of contact is configured to accept PGP encrypted messages for submission of information regarding security vulnerabilities discovered in the RDK platform.

If I submit a security issue, how will I be notified that the issue has been received and is in review?

By attaching your Public Key, it will ensure that you receive a secure message confirming receipt of the submission.

If I submit a potential security issue, will I be notified of a resolution?

Yes, as long as you use your Public Key when submitting the issue.

For a full list of FAQs regarding RDK, please refer to the RDK Wiki by clicking here.