# Announcing: Realtime Media Streams developer preview

<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

    <div>
    <h3>Realtime Media Streams now available!</h3>
    <p>[Connect with our team](https://www.zoom.com/en/realtime-media-streams/#form) to use RTMS across your organization or to publish on our App Marketplace.</p>

</div>

We're excited to announce the upcoming release of **Realtime Media Streams (RTMS)**, a simplified method of accessing media across the Zoom Workplace platform for AI/ML workloads.

Realtime Media Streams will **provide per-participant media streams of audio, video, text transcripts, chat, and screen share over WebSockets** without the need for an automated client (participant "bot").

While we look for partners in an early developer beta to get the details right, there are a few highlights we're keen on sharing now.

## Simplifying implementation for AI/ML workloads

Today, accessing realtime media in Zoom Meetings is complex and expensive, with complicated business logic needed to understand when to join, who is speaking, or when the conversation is over.

**Realtime Media Streams remove the need for automated clients in Meetings**. Apps will receive per-participant structured data streams reflecting the context available to the user that authorized them.

We've spoken to many developers about the complexity and opportunity of building AI apps today. Needs vary widely across the market, but the complexity of managing automated clients to gain access is a shared pain point.

![Basic diagram showing the current media access for automated meeting clients. A Zoom user and a Meeting SDK client both connect to the Zoom Meeting. An application connects to the Meeting SDK client, accessing raw data. A container is required for each Meeting SDK client.](/img/blog/michaelharrington/rtms/currentmediaaccess-bloom.png)

Using RTMS, apps will receive per-participant media streams over a WebSocket connection or can be configured to existing infrastructure.

![Basic diagram showing the suggested diagram for realtime media streams, showing only a Zoom user connected to a Zoom Meeting and a WebSocket connected to the application. The WebSocket has structured data per participants: audio, video, transcript, screen share and chat.](/img/blog/michaelharrington/rtms/with-rtms-bloom.png)

## Apps will automatically join with your users

Realtime Media Streams simplify the complex business logic required to reconcile a user's external calendar with the meetings and calls they join.

**Apps will receive a new stream with a chosen media type when an authorized user joins any meeting, phone call, contact center engagement, or webinar** subject to role-based controls by hosts and account admins. This turns apps from automated listeners into passive, deep integrations to help developers focus on value for users, not infrastructure.

## Enhanced understanding and control of apps

**RTMS apps will not appear as participant tiles in a meeting.** With new affordance given to apps accessing content, specially designed consent flows will provide hosts and participants with control and help drive adoption.

In-meeting notices will help meeting participants understand when an app is active, what it is accessing, who brought it, and how they can start using it themselves.

Granular controls for admins will provide tools to manage which apps are allowed across an account and which format of data they can access.

Realtime Media Streams give app developers choice for deeper access and admins and users with controls for management and adoption.

## Context is everything

Zoom Workplace is where teams collaborate to make decisions, engage customers, and brainstorm ideas. This context is invaluable in turning AI apps into truly meaningful tools for work.

Our goal is to innovate toward the most compelling platform for developers to build and distribute AI applications in the context they'll matter most for users and customers.

Let's build that world together.