> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vasl.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# SDKs

> Web, iOS, Android, and a server-side client.

SDKs are how your product opens a session. The server still does the ingest, the process, and the deliver. The SDK gets a person publishing or playing.

| Client | Use it for |
| - | - |
| Web | A browser that publishes and plays inside your app |
| iOS | The same session on an Apple device you ship |
| Android | The same session on an Android device you ship |
| Server-side | Creating streams and keys from your backend |

Browser publish and play can also speak [WHIP](/publish/webrtc) and [WHEP](/play/webrtc) directly when you want that protocol in the open. The SDK is the path when the session should feel like part of your product.

Package names and method references belong on this page once they match the release you ship. Use the packages that arrive with the license, and keep the [REST API](/api) as the source for creating the stream and rotating keys.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.