What is StreamHost?
StreamHost is a technical live stream access system for productions, events and remote monitoring. It provides private stream ingest, browser playback, public preview links and multiview pages.
FAQ
What is this service?
A practical explanation of what StreamHost is designed for — and what it is not.
Is this a public video platform?
No. StreamHost is not a public video-sharing platform, social media platform or open audience streaming marketplace. It is designed for controlled production workflows and event-based stream access.
What is it useful for?
Typical use cases include private signal transport, event monitoring, client preview links, remote director or producer monitoring, controlled browser playback, multiview walls and temporary access for production teams.
What is it not intended for?
It is not intended as a replacement for Twitch, YouTube, TikTok Live or general gamer streaming platforms. It is also not intended as an open upload platform, piracy platform, public CDN or mass audience entertainment service.
Can it be used for concerts or ticketed events?
Technically yes, but the event organizer or Client is responsible for all rights, licences, ticketing, viewer eligibility, payments and customer communication. StreamHost provides the technical access infrastructure.
Can music events be streamed through it?
Yes, if the Client has the necessary rights and permissions for online transmission. Having rights for a physical event does not automatically mean that online streaming, replay or download rights are included.
What is a public browser link?
A public browser link is a token-based viewing link. It can be opened without a user login while the token is valid and enabled. It can be disabled or regenerated if access needs to be revoked.
Is a public browser link private?
It is private in the sense that it is not publicly listed. However, anyone who receives the valid link may be able to open it. For named or stricter access control, viewer accounts should be used instead.
What are viewer accounts?
Viewer accounts are login-based access credentials. They can be used when access should be controlled per person, with individual settings such as stream visibility, order and playback latency.
What is multiview?
Multiview is a browser page that can show multiple internal or external sources on one screen. It is useful for monitoring several cameras, feeds, program outputs, YouTube/Vimeo sources or HLS streams in one place.
What ingest protocols are supported?
The system is designed around production-style ingest workflows such as RTMP and SRT, with browser playback through HLS. Exact protocol availability may depend on the current server configuration.
Why use this instead of YouTube or Vimeo?
Public platforms are excellent for public distribution, but they may be inconvenient for private signal transport, temporary preview links, rights- sensitive events, low-latency workflows or controlled production monitoring.
Can the stream be restreamed to other platforms?
Yes, restreaming can be part of a setup if required. Availability, target
platforms and reliability depend on the destination platform, stream format,
access credentials and pre-event testing.
(Under construction)
Can the stream be watched worldwide?
In principle, browser playback can be accessed internationally. However, local networks, firewalls, national restrictions, platform availability and internet conditions may affect access. Country-specific delivery should be tested before the event.
Can streams be recorded?
Recording and temporary replay archive are planned or optional features,
depending on storage availability and the agreed setup. Recording also
requires that the Client has the necessary rights for recording and replay.
(Under construction)
How long can recordings stay available?
If enabled, temporary replay archive is intended for short retention periods such as 24–72 hours, with optional browser replay and download access. Longer retention may require a separate agreement.
Does it guarantee perfect playback?
No live streaming system can guarantee perfect playback in every environment. Stability depends on the source encoder, internet connection, server capacity, viewer device, browser and local network conditions.
What can improve stability?
Use wired internet where possible, avoid overloaded Wi-Fi networks, choose a realistic bitrate, test before the event and increase HLS latency when multiple playout devices or unstable networks are involved.