Video Streaming distributes video content through the Gcore CDN network. The CDN is fully integrated — no additional configuration is required to start delivering content globally.
Edge servers pull videos from storage or live streams from the media server and relay or cache them for viewers across 210+ locations worldwide. Integrated CDN delivery includes:
- Edge delivery from 210+ global locations for live streams and VOD content
- Automatic caching at locations closest to viewers for VOD files
- Adaptive bitrate playback using renditions produced by Video Streaming
- Built-in player with CDN-optimized streaming
Billing for integrated CDN
Video Streaming with integrated CDN is billed on a per-minute basis based on the selected tariff plan. Billing is calculated in seconds and converted to minutes.
If viewers watch a total of 10,000 minutes of content in a month, billing is 10,000 minutes at the plan’s per-minute rate.
If a player downloads a video segment to buffer, it is considered delivered and billed. For example, if a player buffers 30 seconds before playback starts, those 30 seconds count toward billing regardless of whether the viewer watches the content or closes the player.
Default CDN subdomain
Video Streaming uses an automatically managed CDN resource with a default subdomain:
The clientID is the numeric account identifier visible in the profile dropdown (click the user icon in the top-right corner of the portal). For example, if the client ID is 12345, the default subdomain is 12345.gvideo.io.
This CDN resource is invisible in the dedicated CDN resource list and is managed automatically by Video Streaming. No configuration or management is required.
This subdomain is included in the playback URLs for all videos and live streams:
- Live stream:
https://12345.gvideo.io/cmaf/12345_00000/master.m3u8
- VOD:
https://12345.gvideo.io/videos/12345_ABcdefg123HiJ
Delivery approaches
The integrated CDN is sufficient for most use cases. If the use case requires custom domains, geo-blocking, or access control policies, two additional approaches are available.
Video Streaming transcodes raw input from RTMP, SRT, WebRTC, or pulled HLS streams into multiple quality levels, packages the result into HLS and MPEG-DASH, and delivers it through the integrated CDN described above.Choose this if: the input requires transcoding and the integrated CDN provides all the delivery controls needed.
Uses Video Streaming for transcoding and delivers the resulting streams through a custom CDN resource. This combines full transcoding capabilities with advanced CDN controls unavailable in the integrated CDN.Choose this if: transcoding and advanced CDN controls are both required (custom domains, geo-blocking, or access policies).The Custom CDN resource guide covers origin group configuration, CNAME settings, and per-feature security policies. Delivers already-prepared HLS or MPEG-DASH streams through the Gcore CDN without transcoding. The origin must provide ready-to-deliver streams.Activation: Video CDN delivery requires approval by Gcore Support before use. Contact support@gcore.com to request activation.Choose this if: an HLS or MPEG-DASH stream is already available from the origin and advanced CDN features are needed (geo-blocking, custom domains, or access policies).The Video CDN guide covers CDN resource setup, HLS/DASH cache configuration, and origin protection.