Powered by GKLive.TV
ID LIVE
One place to understand limits, costs, and how to preview your channel. Creating streams and signing playback uses server-side APIs through GKLive.TV — never in the browser.
Open anytime from the header: Create → ID LIVE.
Channel preview
Paste your playback ID or an approved player URL. Saves on this device only.
ID LIVE Offline
Add a playback ID to see your stream or replay here.
Streaming guidelines
- Fair use. Starter plans target up to ~10 hours of live encoding per month per creator unless your contract says otherwise.
- Quality. 1080p at 3.5–6 Mbps is the sweet spot for sports; 720p saves cost if networks are weak.
- Restreams. One active live per channel by default — contact us for multi-cam or simulcast.
- Compliance. Music, logos, and minors on camera must follow your league and GKZiD terms.
Replay & clips
When the live ends, GKLive.TV can keep a VOD asset for replay. The dashboard and APIs support clipping highlights you can share to Reel or social.
Exact features depend on your workspace settings and signed playback policies.
GKLive.TV ↗Usage & storage (illustrative)
Streams typically bill for encoding time, delivery, and stored minutes. Figures below are planning examples — confirm details on GKLive.TV ↗.
| Line item | What it is | Example tier |
|---|---|---|
| Live ingest | Per-minute while you are broadcasting | Included up to plan cap, then overage |
| Replay storage | Archived VOD after the event | 7-day / 30-day / season-long retention |
| Delivery | Bytes to viewers (CDN) | Scales with audience size |
| Clipping | Short segments from replay | Often minimal extra vs. storage of the master asset |
Turnkey setup (API)
- Work with GKLive.TV to provision API access (tokens stay on the server only).
- Your backend creates a live stream and returns the stream key to OBS / mobile encoder.
- After the event, read the playback ID from the asset and embed the player — or paste it above for a quick check.
- Optional: webhooks for
video.live_stream.active/idleto toggle ID LIVE badges in GKZiD.
We can wire a small Edge or Node endpoint (e.g. POST /api/mux/live) next — keep tokens in env vars, never in this page.