Advanced option — run signaling in your own environment.
Self-Hosting
Advanced. Most teams should use Hosted Signaling.
Self-hosting means you run the Alaznah signaling service (and related infra) yourself, then point the SDK at your URL.
config={{
signalingUrl: 'wss://signal.your-company.com',
userId: currentUser.id,
getAuthToken: fetchCallingToken,
}}The mobile SDK API does not change — only signalingUrl and your token issuer differ from Hosted Signaling.
Configuration checklist
Public docs stay configuration-focused (not architecture marketing):
| Area | You configure |
|---|---|
| Endpoint | HTTPS/WSS URL reachable from mobile networks |
| TLS | Valid certificates (no cleartext in production) |
| Auth | Same short-lived token contract as Hosted |
| ICE / relay | TURN / network settings required by your environment |
| Push | Console or self-managed push credentials for wake |
Operators
Licensed / self-host operators get deployment runbooks and reference images separately from the public SDK docs. App developers only need a working signalingUrl and a token mint endpoint.