Dyte offers a real-time video and voice solution for integrating high-quality video/voice calls into your web, mobile, and desktop applications and websites.

Call recording, live streaming, webinars, live transcription and translation, chatting, polling, quizzes, and many other features are available with Dyte.

Dyte includes:

Core SDKs: These SDKs enable you to create high-quality custom video and voice calls with real-time communication. Core SDKs are completely customizable and simple to integrate.

UI Kit: Using Dyte"s prebuilt design library of UI components, you can integrate video and voice calls into your app or website in minutes.

The following platforms are currently supported:

• Mobile: Flutter, Android (Java/Kotlin), iOS(Objective-C/Swift), React Native
• Web: Javascript Core SDK + UI Kit for React JS, Angular, Web Components for everything else
• Desktop: Electron

For more information, see Dyte docs

Dyte can add value to a wide range of industries, including telehealth, eLearning, gaming, remote working, education, event management, metaverse, adult entertainment, and others.

To get started with Dyte, you must first register in the developer portal.

The developer portal provides the following information:

• Dashboard: A view of your usage, billing, and organization details etc.
• API Keys: The API Keys are required to instantiate a meeting. The values for Organization ID, API Key, and Base URL are generated dynamically for your Organization. You require these settings when performing different actions, such as, create a meeting, delete a meeting, add a participant, etc. Learn more: Web SDKs, Mobile SDKs, APIs.
• Logs and Sample Apps: You can view logs and sample apps in developer portal.

You can also create a webhook, roles, presets, and so on using the developer portal.

A set of roles, UI elements, buttons, and configurations that determines how the meeting will appear for a specific participant. Presets can be created using Developer Portal as well as REST APIs. Learn more: DytePermissionsPreset.

The Dyte Core SDKs are designed to provide developers with an easy way to incorporate real-time communication (RTC) solutions into their apps and websites. With full customization and branding options, you can build your own UI from the ground up without dealing with complicated media layers.

The Core SDK acts as a data-only layer, offering high-level primitives and abstracting away complex media and networking optimizations. It only provides simple APIs that are user-friendly and easy to work with. See Dyte docs.

Dyte's React UI Kit is a prebuilt design library of UI components that makes it easy to integrate video and voice calls into any app or website within minutes. See Dyte docs.

You can use Dyte plugin SDKs to add third-party plugins to experience the most immersive, collaborative, and more human interaction right in your video and audio calls. Dyte provides multiple out-of-the-box plugins, for example, YouTube, Miro, WhiteBoard, and so on.

Log onto https://dev.dyte.io/apikeys with the credentials you used to sign up for Dyte.

On Dyte, you can have up to 2000 people on the same call with video and voice enabled. However, if you have any specific requirements that require more people joining the same call, please contact us.

We will support you with your requirements.

In order to provide the best possible experience, we recommend the number of attendees on live grid to be set in range of 4 to 9. However, we can tailor it to a maximum of 25 attendees.

5000 people. 100 users with the audio-video enabled and everyone else attending the call. However, if you have any specific requirements that require more people joining the same call, please contact us.

We will support you with your requirements.

In Dyte, organization allows you to group all of your company's members. This is a top-level entity to which all members of your group are added. Dyte also considers the organization to be a billing unit.

The Add Participant API call returns your authentication token.

See Add a participant.

Room name is generated when you create a meeting. You can get the room name from the developer portal or using REST APIs. For example,

It is to be noted that a V2 integration of our APIs doesn't have the concept of roomName therefore neither the APIs return roomName nor it is needed by SDK to initialize the meeting.

For more information, see Create a meeting.

Yes, you can.

Browser Requirements:

• Chrome (or Chromium based) 74+
• Firefox 78+
• Opera 64+
• Safari 12+
• Edge 79+
• iOS (Safari) 12.1+
• iOS (Non-Safari) 15+

Internet Requirements:

• Downlink (Minimum) 4 Mbps
• Downlink (Optimal) 8 Mbps
• Uplink (Minimum) 2 Mbps
• Uplink (Optimal) 4 Mbps

Every Dyte communication channel is referred to as a meeting. A meeting is basically a recurring instance of that communication channel, and an ongoing meeting is referred to as a session.

To match your branding, you can change the logo, colors, font, border, and spacing. Design tokens in UI Kit are used to customize these components.

Our Core SDKs can also be used to create fully customized video/voice calls for your applications.

Yes, you can record a meeting. See Start recording a meeting.

However, it's important to note that if there are no participants in the meeting for a duration of 1 minute after you've started the recording, the recording automatically stops and the recording is not saved.

The meeting recordings are saved in your cloud storage that you set up. The supported cloud providers are AWS S3 bucket, DigitalOcean Spaces, Azure Blob storage, and Google Cloud Storage (GCS) buckets.

For more information on how to configure storage configs for Dyte Recordings, see Set storage configuration.

If you haven't set up your storage configurations, Dyte will keep your recordings for 7 days, after which they will expire and become inaccessible.

Resiliency is important. Dyte uses multi-cloud and multi-region architecture to provide that seamless experience. Dyte is hosted in Mumbai, Virginia (US East), Singapore, Frankfurt & more. You can also read through this blog to understand how Dyte manages a multi-region setup.

No. Dyte is a Software as a Service (SaaS), fully managed and hosted by Dyte.

The following are the supported platforms:

• Web: React JS, Angular, Javascript
• Mobile: Flutter, Kotlin, Swift, React Native
• Desktop: Electron

We have no restrictions on our end. Our APIs are HTTP REST APIs and thus can be called from services written in any language or framework. To find your language-specific backend code, refer to our API reference

Webhook service enables you to subscribe to server events. These events allow to trigger specific server actions in response to Dyte meeting events and state changes.

To access the current list of events that can be used with webhooks, see Webhook Events List.

You can pass an optional object storageConfig in the start recording request, and we will publish the recording directly to your cloud provider once it stops. For more information, see Publishing a recording to your cloud provider.

There are two possible reasons:

1. Dyte's recording feature will automatically stop recording if no participants are present in the meeting for 1 minute or longer. Please verify whether there were any participants present during the time the recording was initiated.

2. In case you haven't set up an external storage configuration and have also disabled uploads to Dyte's bucket, the recording will not be saved in any location and will be considered invalid. For more information, see Publishing a recording to your cloud provider.

To create a meeting in your preferred region, pass preferredRegion in the body of the createMeeting endpoint. For more information, see Create a meeting.

No, it is not possible to selectively record specific streams or users. Instead, our recording feature captures the entire screen and not individual streams or users.

Yes, you can share media files via chat during a live session. You can send files, pdfs, images, and more. You can also use plugins such as Doc sync to view the shared file as a group and annotate the points that you would want to clarify.

You can programmatically retrieve all chat messages of a Dyte session using Chat Replay API. For more information, see How to Fetch Chat History of a Dyte Session blog.

Dyte stores chat records for a period of 7 days, only if you've enabled Chat Replay API for your organization. You can download the chat using the chat_download_url in CSV format from AWS S3. However, it is important to note that this download link is only valid for 24 hours. In case the link has expired, you can request for a new chat_download_url by sending an HTTP GET request to the Chat Replay API.

You can use the Session API to fetch the metadata for a given session.

Dyte provides multiple out-of-the-box plugins, for example, YouTube, Miro, WhiteBoard, and so on. You can use WhiteBoard for the collaboration.

No, after creating a meeting, use the Add Participants API to add participants to the meeting.

Yes, codec and storage information can be passed through the recording API. Per recording, you can pass the parameters storageConfig and videoConfig. You can also send an email to dev@dyte.io to set the orgs default configuration.

Yes, you can. By default, Dyte uploads all recordings to Dyte's S3 bucket in the AWS ap-south-1 region. However, Dyte provides users with the flexibility to choose whether or not to upload their recordings to Dyte's S3 bucket.

If you wish to disable uploads to Dyte's bucket, you can set the dyte_bucket_config parameter to false in the Start Recording endpoint. For more information, see Manage Dyte's Default Recording Upload Settings.

Based on historical data, here are estimations for recording sizes with different components:

• Format: H264 video codec
• Resolution: 720p
• Duration: 1 hour
• Estimated size: On average, around 230MB
• Range: Typically falls between 200-250MB, with potential outliers for static or rapidly changing content.

Please note that these estimations are based on historical data and apply to recordings with a resolution of 720p. Actual sizes may vary depending on factors such as content, codec settings, and resolution.

For timeouts and 5xx errors, we retry three times with a one-second delay between each retry.

We send startedAt and endedAt timestamps in a meeting.ended webhook that can be used to compute the session's running time.

Typically, there is a 3-5 second lag in all livestreams. If the delay exceeds 10 seconds, users can "Skip to Live," which involves dropping frames in order to synchronize the user's video with the live stream. Once the videos are synced, we stop dropping frames until the time exceeds 10 seconds again.

Dyte's Interactive Livestreaming (ILS) can currently accommodate 25,000 viewers and 100 hosts on a single livestream.

Currently, our platform can support up to 25,000 viewers in a single livestream, and the quality of the stream is not affected by the number of viewers. However, an increase in the number of users may impact other features such as chats and polls.

You can manage the permissions for a viewer using presets. For livestreaming, you must create two presets. One preset is for the livestreaming host, while the other is for the livestreaming viewer. For details, see Create Presets.

Yes, you can. However, ensure that you've the required preset permissions. For details, see Create Presets.

The host requires certain host controls such as the ability to Kick Participants, Mute Audio, Mute Video, and Pin Participant, as well as media permissions like Start Livestream and Admit or remove participants from the livestream. For details, see Create Presets.

Dyte provides live streams with a low latency of only 3 to 6 seconds.

No, stream keys can be reused multiple times. However, it's important to keep the stream key private as it grants access to the live stream. Therefore, users should be informed to keep their stream key secure.

For more information, see Live Stream Custom Video Input via RTMP.

The issue could be due to the security features implemented by the browser. Most of the standard browsers with best security practices restrict many features to HTTPS instead of HTTP. You can read about the details of the features that are restricted in Chrome here.

To troubleshoot, we recommend trying the steps mentioned in this document. If this does not resolve the issue, you can try using ngrok as an alternative solution.

To use ngrok, download the software and run it with the local port specified. This generates an HTTPS URL that you can use for testing the microphone and camera.

1. Download ngrok.

2. Run the command 'ngrok http PUT_LOCAL_PORT_HERE'.

3. Use the HTTPS URL to test your microphone and camera.

Once Dyte has generated an invoice, you can pay using a link, a saved card, or do a direct bank transfer.