Kandy Link - WebRTC & More

Service Providers looking for ways to provide a Communications Platform-as-a-Service (CPaaS) solution of their own or deploy WebRTC based clients and services often face regulations and restrictions that are not applicable to OTT services, particularly in the data privacy and sovereignty space. And many enterprises and large government organizations require a tighter security over the user’s data and media than public cloud solutions can provide.

Kandy Link has been created to condense the power of the Kandy communications platform into an on-premise solution that allows CSPs and enterprises to leverage APIs and SDKs to provide differentiated user experiences and make communications an integral part of user processes and applications.

Kandy Link becomes a local extension of the Kandy CPaaS solution and provides WebRTC gateway, REST API proxy, media broker capabilities and the ability to deploy additional services in the network as micro-services.

Kandy Link goes beyond basic WebRTC gateway functionality delivering value added capabilities that accelerate the deployment of new services that contribute to enhance user retention, facilitate new revenues and markets and optimize the total cost of ownership.

WebRTC provides the foundational elements to enable the delivery of a uniform and compelling user experience across any device, leveraging the reach and capabilities of the web. With Kandy Link, services can be delivered to any internet user via a web browser. However, using a browser as the primary means of communication has several limitations that hinder the user experience (need to keep the browser tab open, media/device selection buried within browser settings, limited notifications and alerts and more).

Kandy Omni Technology uses Kandy Link to bring together services uniformly across different end user platforms and environments. Omni-based clients leverage the REST APIs within Kandy link to create HTML5, CSS3 and JavaScript based clients that run natively within a binary container on the device’s operating system. The patent pending Omni container exposes the machine/OS resources to the web based client using JavaScript APIs. The application container is packaged and distributed to the end user with the client’s URL preloaded and after that, all new changes, functionality and capabilities are applied on the server, minimizing the cost of rolling out new software to the end user every time new features are introduced.

Omni is not about the technology, it’s about savings!

• One UI across all devices that you can customize for your world
• It costs less to deploy and no need to upgrade every few weeks
• Your users will not know the difference because it still installs and executes as any other application
• You can change the entire user experience by replacing the web content on the server