You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/realtime/index.mdx
+6-19Lines changed: 6 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,30 +26,17 @@ Cloudflare Realtime is a comprehensive suite of products designed to help you bu
26
26
27
27
### RealtimeKit
28
28
29
-
Cloudflare [RealtimeKit](/realtime/introduction) allows you to integrate programmable and easily customizable live video and voice into your web, mobile, and desktop applications. With just a few lines of code, you can enable live video communication, voice calls, and interactive live streaming.
29
+
Cloudflare [RealtimeKit](/realtime/realtimekit/) allows you to integrate programmable and easily customizable live video and voice into your web, mobile, and desktop applications. With just a few lines of code, you can enable live video communication, voice calls, and interactive live streaming.
30
30
31
-
At its core, RealtimeKit is powered by the [Realtime SFU](/realtime/sfu), which efficiently routes video and audio streams between participants. RealtimeKit provides a set of user-friendly SDKs and APIs that act as a layer on top of the SFU, so you don't have to handle the complexities of media track management, peer management, and other intricate WebRTC-related tasks.
31
+
At its core, RealtimeKit is powered by the [Realtime SFU](/realtime/sfu/), which efficiently routes video and audio streams between participants. RealtimeKit provides a set of user-friendly SDKs and APIs that act as a layer on top of the SFU, so you don't have to handle the complexities of media track management, peer management, and other intricate WebRTC-related tasks.
32
32
33
33
### Realtime SFU
34
34
35
-
The [Realtime SFU (Selective Forwarding Unit)](/realtime/sfu) is a powerful media server that efficiently routes video and audio streams between participants, and underpins the RealtimeKit. The Realtime SFU runs on [Cloudflare's global cloud network](https://www.cloudflare.com/network/) in hundreds of cities worldwide. For developers with WebRTC expertise, the SFU can be used independently to build highly custom applications that require full control over media streams. This is recommended only for those who want to leverage Cloudflare's network with their own WebRTC logic.
35
+
The [Realtime SFU (Selective Forwarding Unit)](/realtime/sfu/) is a powerful media server that efficiently routes video and audio streams between participants, and underpins the RealtimeKit. The Realtime SFU runs on [Cloudflare's global cloud network](https://www.cloudflare.com/network/) in hundreds of cities worldwide. For developers with WebRTC expertise, the SFU can be used independently to build highly custom applications that require full control over media streams. This is recommended only for those who want to leverage Cloudflare's network with their own WebRTC logic.
36
36
37
37
### TURN Service
38
38
39
-
The [TURN service](/realtime/turn) is a managed service that acts as a relay for WebRTC traffic. It ensures connectivity for users behind restrictive firewalls or NATs by providing a public relay point for media streams.
The [TURN service](/realtime/turn/) is a managed service that acts as a relay for WebRTC traffic. It ensures connectivity for users behind restrictive firewalls or NATs by providing a public relay point for media streams.
53
40
54
41
## Related products
55
42
@@ -80,7 +67,7 @@ Cloudflare Stream lets you or your end users upload, store, encode, and deliver
Copy file name to clipboardExpand all lines: src/content/docs/realtime/realtimekit/concepts.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This page explains the core concepts and terminology used in RealtimeKit.
9
9
10
10
### Meeting
11
11
12
-
A **Meeting** is the fundamental communication channel in RealtimeKit. You can think of it like an event on your calendar - it's a persistent, long-lived container or "room" that serves as a blueprint for its [sessions](/realtime/concepts#session). Every session created for this meeting inherits the same base configuration, such as the title of the meeting and whether to automatically record the session when it starts. You add participants to the meeting, which grants them access to join a session of that meeting.
12
+
A **Meeting** is the fundamental communication channel in RealtimeKit. You can think of it like an event on your calendar - it's a persistent, long-lived container or "room" that serves as a blueprint for its [sessions](/realtime/realtimekit/concepts/#session). Every session created for this meeting inherits the same base configuration, such as the title of the meeting and whether to automatically record the session when it starts. You add participants to the meeting, which grants them access to join a session of that meeting.
13
13
14
14
### Session
15
15
@@ -33,7 +33,7 @@ A **Participant** is the server-side representation of a user within a session.
33
33
34
34
### Peer
35
35
36
-
A **Peer** is the client-side representation of a [participant](/realtime/concepts#participant) in a session. While the terms are sometimes used interchangeably, a peer represents a specific instance of a participant joining the meeting. For example, if a single user joins the same meeting from two different browser tabs, they will have the same participant ID (also referred to as a user ID) but two unique peer IDs.
36
+
A **Peer** is the client-side representation of a [participant](/realtime/realtimekit/concepts/#participant) in a session. While the terms are sometimes used interchangeably, a peer represents a specific instance of a participant joining the meeting. For example, if a single user joins the same meeting from two different browser tabs, they will have the same participant ID (also referred to as a user ID) but two unique peer IDs.
Integrate programmable, and easily customizable live video and voice into your web, mobile, and desktop applications with just a few lines of code.
16
+
17
+
</Description>
18
+
19
+
The RealtimeKit is a set of user-friendly SDKs and APIs that provides the fastest and simplest way to integrate a complete video and voice call interface into any application, allowing you to get started with just a few lines of code while still offering flexibility for customization.
20
+
21
+
Powerful yet simple to use, RealtimeKit is built on top of WebRTC and provides a set of user-friendly SDKs and APIs that act as a layer on top of the [Realtime SFU](/realtime/sfu/), so you don't have to handle the complexities of media track management, peer management, and other intricate WebRTC-related tasks.
22
+
23
+
Learn more about the [concepts](/realtime/realtimekit/concepts/) behind RealtimeKit, [how it works](/realtime/realtimekit/introduction/#how-realtimekit-works), and [use cases](/realtime/realtimekit/introduction/#use-cases).
Copy file name to clipboardExpand all lines: src/content/docs/realtime/realtimekit/introduction.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Build collaborative experiences for team meetings, online classrooms, or social
31
31
32
32
### Webinars
33
33
34
-
Webinars are one-to-many events designed for a presenter to share information with a large, interactive audience. Unlike group calls where all participants collaborate freely, webinars have distinct roles for presenters and viewers, managed through [presets](/realtime/concepts#presets). This structure, powered by WebRTC, is ideal for product demos, company all-hands, and live workshops, with features like chat, Q&A, and polls to engage the audience.
34
+
Webinars are one-to-many events designed for a presenter to share information with a large, interactive audience. Unlike group calls where all participants collaborate freely, webinars have distinct roles for presenters and viewers, managed through [presets](/realtime/realtimekit/concepts/#presets). This structure, powered by WebRTC, is ideal for product demos, company all-hands, and live workshops, with features like chat, Q&A, and polls to engage the audience.
35
35
36
36
-**Product Demos:** Showcase your product to a large audience with live video and Q&A sessions.
37
37
-**Company All-Hands:** Broadcast company-wide meetings to all your employees, no matter where they are.
Copy file name to clipboardExpand all lines: src/content/docs/realtime/turn/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: TURN Service
3
3
pcx_content_type: navigation
4
4
sidebar:
5
-
order: 10
5
+
order: 3
6
6
---
7
7
8
8
Separately from the SFU, Realtime offers a managed TURN service. TURN acts as a relay point for traffic between WebRTC clients like the browser and SFUs, particularly in scenarios where direct communication is obstructed by NATs or firewalls. TURN maintains an allocation of public IP addresses and ports for each session, ensuring connectivity even in restrictive network environments.
@@ -64,4 +64,4 @@ Each limit is for a single TURN allocation (single TURN user) and not account wi
64
64
65
65
:::
66
66
67
-
These limits are suitable for high-demand applications and also have burst rates higher than those documented above. Hitting these limits will result in packet drops.
67
+
These limits are suitable for high-demand applications and also have burst rates higher than those documented above. Hitting these limits will result in packet drops.
0 commit comments