Install an SDK

Livqeno splits along one line: your backend holds the API key and mints tokens; your client holds a token and joins. Those are different packages, and neither can do the other's job.

The @ravenkash/* packages are on npm; the Python and Flutter SDKs are not on PyPI or pub.dev yet. For Python and Flutter, install from a checkout — see Installing from source.

One npm caveat, until 0.1.1 ships: @ravenkash/rtc@0.1.0 and @ravenkash/client@0.1.0 were published with an unresolvable workspace:* dependency and fail to install. Add an overrides entry to your package.json to pin the missing sibling, and drop it once 0.1.1 is out:
{ "overrides": { "@ravenkash/effects": "0.1.0" } }

Your backend

npm install @ravenkash/server

Not on PyPI — and do not pip install raven-sdk. That name belongs to an unrelated third-party package, so it installs someone else's code. See the Python SDK page.

pip install "git+https://github.com/atulsinghhhh/Raven.git#subdirectory=sdks/python"

Your client

npm install @ravenkash/rtc          # calls
npm install @ravenkash/chat         # messaging
npm install @ravenkash/client       # both, behind one object

npm install @ravenkash/rtc @ravenkash/react

Add @ravenkash/chat for a chat panel, @ravenkash/effects for camera filters. @ravenkash/react takes its Livqeno siblings as peer dependencies, so your application chooses the versions and there is exactly one copy of each in the tree.

npm install @ravenkash/react-native @ravenkash/rtc \
            react-native-webrtc react-native-incall-manager
 
cd ios && pod install   # iOS only

react-native-webrtc is a required native module — autolinking needs it installed directly in your app. You never import it yourself. See Permissions for the OS-level setup it also needs. react-native-incall-manager is optional, for call-audio routing.

dependencies:
  raven_rtc: ^0.1.0     # calls
  raven_chat: ^0.1.0    # messaging
  raven_live: ^0.1.0    # live streaming

Not on pub.dev yet — see Installing from source.

Which package does what

Package	Runs in	Holds
`@ravenkash/server`	Your backend	The API key
`raven-sdk` (Python)	Your backend	The API key
`@ravenkash/rtc`	Browser	An RTC token
`@ravenkash/chat`	Browser	A chat token
`@ravenkash/client`	Browser	Both, behind one `Raven` object
`@ravenkash/react`	Browser	Hooks over `rtc`/`chat`/`effects`
`@ravenkash/react-native`	iOS, Android	The same `Room` class as the web
`raven_rtc`, `raven_chat`, `raven_live`	iOS, Android	The same concepts, in Dart
`@ravenkash/effects`	Browser	Nothing — no credential needed
`@ravenkash/cli`	Your terminal	A dashboard session

Full per-SDK reference in SDKs.

Next steps

Generate a token — the first thing your backend does.
Browser support — what is verified and what is not.