Skip to main content


Dyte provides the easiest way to add real-time communications using video and audio to your apps and platforms.

Working with Dyte will require an integration with your application server as well as the participant-facing client (mobile or web) app where you want to deliver the video.

Jump to quickstart

Keep reading to know more about how Dyte works, or click here to jump to our quickstart guides that get you started.

How Dyte works#

Diagram explaining how Dyte works

Dyte is based largely on the WebRTC protocol, and the features and optimizations we build on top of it. Although the protocol is supposed to be peer-to-peer, anyone who has tried implementing it by themselves would know that the implementions get real messy, real fast. To have a real working solution, servers with SFU, STUN, TURN, etc capabilities are required to optimize for user bandwidth and performance, route the data packets correctly and maintain state of certain client side configurations and preferences.

On top of managing this basic communication using media streams, Dyte offers additional features on top such as chat, polls, plugins, recording and streaming, and many others.

Dyte's mission is to make this technology available to developers for easy use, and towards that we provide several implementations of Dyte's real-time communications services, which enable developers to integrate a meeting within a few lines of code without having any previous knowledge about media, streaming, or RTC, but also allow them to go deeper if they so wish. The features offered on top of the basic communication service are also in a developer's control - which ones do they want to pick and to what level do they want to customize it. Pick from one of the below available options to suit your platform.

Meeting initialization, customizations, and most other features remain the same across all clients. You can select a client platform from the quickstart section below and use the switcher at the top left to access the guides specific to other frameworks you might want to build your client app on.

The reference for the server APIs can be found here.


  • Meeting - every communication channel created on Dyte is termed as a meeting
  • Participant - anyone who joins the meeting, whether as an actual user or programatically / robo user
  • Permission - a specific action allowed or not for a participant
  • Role - a set of permissions saved together form a role. An existing role can be assigned to any participant to describe their level of control and limit their actions within the meeting.
  • Preset - a combination of role, the UI elements, buttons and configurations that define the look and feel of your meeting for a particular participant.
  • Recording - you can record the meeting, and get a video / audio file.
  • Livestreaming - you can livestream the meeting to other streaming platforms that support RTMP, like YouTube, Twitch, etc.
  • Analytics - get analytics data around your meetings, like number of minutes, number of recorded minutes, number of participants, etc.

For a guided tutorial on how to start from scratch, pick from one of the below available options or pick one of the SDK guides to read in detail.


Mobile app using Client SDK with React Native
Web app using Client SDK with React
Mobile app using Client SDK with Kotlin
Mobile app using Client SDK with Swift

Pick a platform or framework#



Read about our server APIs#

How to use these docs#