Oneseco Media GITHUB

Make your apps truly interactive with Cloudflare Realtime and RealtimeKit 2025-04-09 Zaid Farooqui Will Allen Abhishek Kankani 7 min read Over the past few years, we’ve seen developers push the boundaries of what’s possible with real-time communication — tools for collaborative work, massive online watch parties, and interactive live classrooms are all exploding in popularity. We use AI more and more in our daily lives. Text-based interactions are evolving into something more natural: voice and video. When users interact with the applications and tools that AI developers create, we have high expectations for response time and connection quality. Complex applications of AI are built on not just one tool, but a combination of tools, often from different providers which requires a well connected cloud to sit in the middle for the coordination of different AI tools. Developers already use Workers, Workers AI, and our WebRTC SFU and TURN services to build powerful apps without needing to think about coordinating compute or media services to be closest to their user. It’s only natural for there to be a singular "Region: Earth" for real-time applications. We're excited to introduce Cloudflare Realtime — a suite of products to help you make your apps truly interactive with real-time audio and video experiences. Cloudflare Realtime now brings together our SFU, STUN, and TURN services, along with the new RealtimeKit. Say hello to RealtimeKit RealtimeKit is a collection of mobile SDKs (iOS, Android, React Native, Flutter), SDKs for the Web (React, Angular, vanilla JS, WebComponents), and server side services (recording, coordination, transcription) that make it easier than ever to build real-time voice, video, and AI applications. RealtimeKit also includes user interface components to build interfaces quickly.  The amazing team behind Dyte, a leading company in the real-time ecosystem, joined Cloudflare to accelerate the development of RealtimeKit. The Dyte team spent years focused on making real-time experiences accessible to developers of all skill levels, and had a deep understanding of the developer journey — they built abstractions that hid WebRTC's complexity without removing its power. Already a user of Cloudflare’s products, Dyte was a perfect complement to Cloudflare’s existing real-time infrastructure spanning 300+ cities worldwide. They built a developer experience layer that made complex media capabilities accessible. We’re incredibly excited for their team to join Cloudflare as we help developers define the future of user interaction for real-time applications as one team. Interactive applications shouldn't require WebRTC expertise  For many developers, what starts as "let's add video chat" can quickly escalate into weeks of technical deep dives into WebSockets and WebRTC. While we are big believers in the potential of WebRTC, we also know that it comes with real challenges when building for the first time. Debugging WebRTC sessions can require developers to learn about esoteric new concepts such as navigating ICE candidate failures, TURN server configurations, and SDP negotiation issues. The challenges of building a WebRTC app for the first time don’t stop there. Device management adds another layer of complexity. Inconsistent camera and microphone APIs across browsers and mobile platforms introduce unexpected behaviors in production. Chrome handles resolution switching one way, Safari another, and Android WebViews break in uniquely frustrating ways. We regularly see applications that function perfectly in testing environments fail mysteriously when deployed to certain devices or browsers. Systems that work flawlessly with 5 test users collapse under the load of 50 real-world participants. Bandwidth adaptation falters, connection management becomes unwieldy, and maintaining consistent quality across diverse network conditions proves nearly impossible without specialized expertise.  What starts as a straightforward feature becomes a multi-month project requiring low-level engineering to solve problems that aren’t core to your business. We realized that we needed to extend our products to client devices to help solve these problems. RealtimeKit SDKs for Kotlin, React Native, Swift, JavaScript, Flutter RealtimeKit is our toolkit for building real-time applications without common WebRTC headaches. The core of RealtimeKit is a set of cross-platform SDKs that handle all the low-level complexities, from session establishment and media permissions to NAT traversal and connection management. Instead of spending weeks implementing and debugging these foundations, you can focus entirely on creating unique experiences for your users. Recording capabilities come built-in, eliminating one of the most commonly requested yet difficult-to-implement features in real-time applications. Whether you need to capture meetings for compliance, save virtual classroom sessions for students who couldn't attend li

Create zone apex record Copy Page When you add a domain to Cloudflare, you may also need to create or review the DNS record on your zone apex. Zone apex refers to the domain (example.com) or subdomain (blog.example.com) that you are adding to Cloudflare. Usually, the zone apex record makes your domain accessible by visitors. In this case, the necessary record type (A, AAAA, or CNAME) and its content will depend on the provider that hosts your website or application. If you are using Cloudflare Pages, refer to Custom domains. If you are using other providers, look for their guidance on how to connect domains managed on external DNS services. ANAME or ALIAS ANAME or ALIAS are DNS records used by specific DNS providers. If your previous provider was using ANAME or ALIAS, you can recreate these records on Cloudflare as CNAME records. Cloudflare's CNAME flattening1 allows you to create CNAME records at your zone apex, removing the need for those other record types. Zone apex record To create a zone apex record, use @ for the record Name, as in the following example. Type Name IPv4 address Proxy status A @ 192.0.2.1 Proxied Dashboard API Log in to the Cloudflare dashboard ↗ and select your account and zone. Go to DNS > Records and select Add record. Select A, AAAA, or CNAME as the record Type, according to your needs: To point to an IPv4 address, select A, use your zone apex (@) for the record Name, and insert the IPv4 address in the respective field. To point to an IPv6 address, select AAAA, use your zone apex (@) for the record Name, and insert the IPv6 address in the respective field. To point to a fully qualified domain name (FQDN) ↗ (such as your-site.host.example.com), select CNAME, use your zone apex (@) for the record Name, and insert the fully qualified domain name in the Target field. Specify the Proxy status and TTL according to your needs. Select Save to confirm. Domain redirects Once you create a domain, you may want to route that traffic to other places. For more guidance, refer to Redirect domain to subdomain or Redirect one domain to another. Get free SSL certificates While DNS is what communicates where your website or application can be reached, SSL/TLS is what enables websites and applications to establish connections in a secure way. If your domain is not correctly covered by an SSL/TLS certificate, your visitors will find a warning on their browser stating that your website or application is not secure. Cloudflare offers free, unshared, publicy trusted Universal SSL certificates to all Cloudflare domains. Was this helpful? Edit page Previous Manage DNS records Next Create subdomain records Resources API New to Cloudflare? Products Sponsorships Open Source