
Real-time audio & video SDKs, ready to launch 🚀
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Dyte (W21).
Dyte sold the layer between a developer's product and the hard parts of a live call. Its SDKs handled participant state, audio and video, roles, layouts, chat, polls, recording, live streaming, and interactive plugins. A customer could ship a branded meeting experience without building a media stack or accepting the fixed interface of a consumer conferencing app.
Abhishek Kankani and Palash Golecha started the Bengaluru company in 2020 and entered Y Combinator's Winter 2021 batch. Dyte raised an $11.6 million seed round, grew beyond fifty employees, and said its infrastructure had reached hundreds of thousands of people. In June 2025 the whole team joined Cloudflare. The product became Cloudflare RealtimeKit, and the old Dyte SDKs entered maintenance mode.
The transaction price is not public. This was nevertheless a clear strategic sale: Cloudflare supplied a global SFU, STUN, and TURN network, while Dyte supplied the client SDKs, UI components, and developer journey that made that infrastructure usable.[1]
Image 1 / 1
Kankani and Golecha began building in November 2020, when remote work and online classes had made video a default product surface. Their first idea was a standalone calling application. The turning point came when customers asked to embed the technology inside their own products. Dyte moved down the stack and sold an API and SDK instead.[2]
The first implementation carried a revealing debt. A client wanted the founders' demo application as an SDK, so the tiny team adapted it. UI elements and business logic remained tangled. That helped Dyte ship, but made customization and maintenance harder. The company later rebuilt the product around Web Core, a lower-level state and media SDK, with UI components layered on top.[3]
That progression defined the company. Dyte was not only renting media servers. It was converting repeated integration work into primitives that a customer's engineering team could control. Kankani described the product as something its developer-founders would themselves want to use: fast to integrate, well documented, and open to customization.[4]
Dyte's basic unit was a meeting that a developer created through an API and joined through a client SDK. Presets defined participant roles and permissions. UI Kit supplied setup screens, participant grids, controls, chat, and polls; Core SDK exposed state and media for teams that wanted their own interface. Recordings, RTMP broadcasts, webhooks, analytics, and plugins extended the call.
The product spanned web, React, mobile, and desktop environments. TechCrunch showed Dyte changing brand colors, visible controls, roles, and plugins in minutes. Plugins could add a shared browser, whiteboard, file viewer, or game without reducing the meeting to screen sharing.[7]
Read the complete post-mortem, the rebuild playbook, and the exact reasons Dyte is still worth studying now.