Hubfly spaceDocs
Console

Streams

Managed Streams

Send one stream up, combine it with others, then spread it to your own player and to every platform at once. Schedule it, record it, and pay for the speed you reserve and the bandwidth you send.

A stream server is an instance in a Managed service project, next to any Managed Databases and Realtime servers. Hubfly space runs the media engine, gives the server a hostname with TLS, and meters every byte. You manage it in the Dashboard, with hubfly stream, with the SDKs or through the Streams API. Your site plays it with @hubfly/streams or the embed page.

Choose a guide

How it fits together

text
inputs ──┬──────────────► channels ──► playback (WebRTC, LL-HLS, HLS, audio, pulls)
(push,   │                  ▲   │
 pull)   ├─► mixers ────────┘   ├──► destinations (restream)
         │   (scenes, graphics) └──► recordings, clips (Hubfly space Storage)
playlists┘
(Storage, URLs)          schedules ──► live control of any of the above
ResourceWhat it isPer server
Stream serverOne managed instance with a speed cap, a processing cap and a host such as acme-tv.live.hubfly.app. A project can hold several.—
InputWhere media comes in: push (RTMP, RTMPS, SRT, WHIP, Icecast) with a primary and an optional backup key, or pull from an RTMP, RTSP, SRT or HLS URL.50
MixerCombines inputs, playlists and graphics into one program with scenes, layers, audio and transitions.5
ChannelWhat people watch: a source (an input, a mixer or a playlist), a backup, its encoding, playback outputs, latency, DVR, access and recording.20
DestinationA restream target fed by a channel or an input.50
PlaylistAn ordered list of Hubfly space Storage videos or https URLs, played once or looped.50, with 500 items each
ScheduleControl actions at a start and an end time, once or repeating, in the server's time zone.100
Playback keySigns viewer tokens for channels in token mode.10
WebhookSigned event deliveries to your HTTPS endpoint.10
GraphicAn image, SVG, font or HTML bundle used by mixers and slates.200, 500 MiB in total
Storage linkAccess to one Hubfly space Storage bucket for recordings and playlists.10
Custom domainYour hostname for playback, ingest or both.10

Ids have a prefix per resource: sin_ inputs, smx_ mixers, sch_ channels, sds_ destinations, spl_ playlists, ssc_ schedules, spk_ playback keys, swh_ webhooks, sgr_ graphics, ssl_ storage links.

Ingest protocols and ports

ProtocolURLStream key goes inPort
RTMPrtmp://<host>/liveThe stream key fieldTCP 1935
RTMPSrtmps://<host>:443/liveThe stream key fieldTCP 443
SRTsrt://<host>:9000?streamid=publish:<key>streamidUDP 9000
WHIP (WebRTC)https://<host>/whip/<input id>Authorization: Bearer <key>TCP 443, UDP and TCP 8189
Icecast<host>:8000/radio/<input id>Password, with user sourceTCP 8000 or 443
PullAn rtmp, rtmps, rtsp, rtsps, srt or https (HLS) URL on the input—Outbound

Inputs accept H.264, H.265 (HEVC) and AV1 video (VP8 and VP9 over WHIP), up to 4096×2160 and 60 fps, with AAC, Opus or MP3 audio, at up to 80 Mbps. Ingest is never billed. Encoder settings are in OBS and encoders.

Playback outputs

OutputURLTypical delay
WebRTC (WHEP)POST https://<host>/whep/<channel>Under 1 second
LL-HLShttps://<host>/hls/<channel>/index.m3u8 with latency low3–5 seconds
HLSThe same URL with latency standard15–25 seconds
Audiohttps://<host>/radio/<channel>.mp3, .aac or .opusA few seconds
RTMP and SRT pullrtmp://<host>/play/<channel>, srt://<host>:9000?streamid=read:<channel>A few seconds
Embed pagehttps://<host>/embed/<channel>Uses the best of the above
Thumbnail and statushttps://<host>/thumb/<channel>.jpg, https://<host>/status/<channel>.json—

Each output exists only when it is turned on for the channel. When nothing is live, viewers see the server's offline slate, and the status JSON says "live": false.

WebRTC needs streams without B-frames

Browsers cannot play WebRTC video with B-frames. Set B-frames to 0 in your encoder to keep WebRTC a free passthrough. Otherwise WebRTC viewers get the first rendition of the channel's transcoding ladder (billed as processing), or the player falls back to LL-HLS when the channel has no ladder.

What Hubfly space runs for you

  • The media engine. Ingest, the router, packaging, WebRTC, transcoding workers, the mixer, recordings and restream pushes, on a dedicated high-bandwidth node. Media goes straight to the node, which terminates TLS itself.
  • A speed cap per server. Your server's outbound traffic is capped at the speed you chose, so no other customer can slow it down. Raise or lower it at any time, live.
  • Keys. Stream keys are generated by Hubfly space and stored as hashes on the node. They are shown once when created or rotated, or through an explicit reveal; logs and events show only fingerprints.
  • Health and alerts. Live bitrate, frame rate, keyframe interval, B-frames and SRT link stats for every publisher; destination status and retries; viewer statistics; and alerts for failing destinations, processing that does not fit, speed throttling and billing.
  • Billing. Usage is measured per minute on the node and billed per complete hour. See pricing and limits.

Restarts, upgrades and outages

EventWhat publishers and viewers notice
Speed or setting changeNothing. Changes apply live; unaffected inputs, channels and destinations keep running.
Engine upgradeRTMP and other TCP sessions stay connected. SRT and WebRTC sessions reconnect, and players reconnect on their own.
Stopping the serverPublishers are refused and no media is served. The status JSON and the embed page show that the stream is offline. Speed is not billed while stopped.
Billing blocked (no balance or a spend cap reached)Ingest stops and the embed page shows a paused card until you top up or raise the cap.
Node maintenanceEvery stream on the node stops until it is back. The status page reports the media node's health.

One node at launch

Stream servers share one dedicated media node. There is no region picker and no failover between nodes yet. Use a backup input and an offline slate to cover encoder problems; they do not cover the node itself.

Team access

PermissionAllows
stream:readSee servers, resources, live status, events, viewer statistics and usage. Never secrets.
stream:operateGo live and off air, switch scenes, start and stop destinations and recordings, cut clips, use the studio and mint test playback tokens.
stream:adminCreate, start, stop and delete servers, change speed, create, edit and delete every resource, reveal and rotate keys, and manage bindings, domains and storage links.

Organization owners and admins have all three; viewers and developers have stream:read.

From the terminal

This creates a 100 Mbps server with a first input, prints the encoder settings and the stream key once, and shows what is live:

bash
hubfly stream create acme-tv --speed 100 --project new
hubfly stream channels create acme-tv Main --source input:sin_cam1abcd --latency ultra
hubfly stream channels playback acme-tv Main
hubfly stream live acme-tv

hubfly live is a short alias. See the hubfly stream reference for every command.

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top