1. Create and select your event
Sign in, open Streams and create a named event. A successful creation should provision its own input; a failed provisioning message is not a ready stream. Open that event to find its server URL and key. Keep the key private and avoid reusing another event’s credentials.
2. Connect the source encoder
In OBS or compatible hardware, use the exact server URL and key shown for the selected event. Match the required transport—RTMP and RTMPS are not interchangeable. Set output resolution, frame rate, bitrate and audio at the source. A destination label or pricing calculator does not change source resolution.
3. Add the destination channels
Get the server URL and private key from each platform’s live dashboard. Add them to the correct event and enable the intended destinations. The number in the wallet calculator is an estimate input, not permission to exceed the account’s destination limit. Check whether each platform also requires you to publish or start its event.
4. Prepare logos and graphics
Open the selected event’s Studio, upload an asset, drag it into position, resize it and save. The saved overlay belongs to that event. A raw relay cannot burn graphics into video. Browser-controlled outgoing graphics need the cloud renderer activated; the alternative OBS Browser Source workflow applies graphics in OBS rather than in the cloud.
5. Check the browser preview
Send your source feed and refresh the event’s signal status. Browser playback depends on the correct input and enabled playback/recording settings. A destination may be live while a preview is unavailable; do not infer failure solely from a blank player. Confirm input status, playback settings and event selection before changing keys.
6. Understand minutes before topping up
At the current 1080p planning rate, one studio minute costs ₹2 plus ₹1 per destination. One destination therefore costs ₹3/minute and ₹299 corresponds to approximately 99.67 minutes. Extra destinations reduce estimated available time. A top-up is prepaid credit, not a subscription upgrade. Review payment information; automatic metering and paid activation are still pending.
If the encoder keeps reconnecting
Check the selected event’s current input exists, verify the URL and key without adding whitespace, and confirm the provider account can accept the feed. Look at the encoder log and provider input status. Avoid repeatedly regenerating keys during an event: an old key will stop working. Do not assume port 443 alone is the cause—transport, credentials and input provisioning must also match.
If payment succeeds but access looks unchanged
Confirm you used the intended signed-in account and whether checkout was Test Mode. A verified top-up changes credit, not the subscription tier. Keep the order and payment IDs if credit is missing. Never share card details or stream keys. A funded balance does not override pending usage controls or unlock a planned feature.