Platform
Everything you need to host, protect and deliver video
Four groups of capability: getting video hosted and delivered, controlling who can watch, presenting it under your own brand, and measuring what happened. Each one has a page of its own that describes the mechanism and states the boundary rather than listing adjectives.
The shape of it
What DynTube is for
DynTube hosts video that plays on pages you own. You upload; the platform transcodes into an adaptive HLS ladder, delivers it, and provides a player and an embed. What that buys you over a free public platform is context: no advertising, no recommendations for other people’s content, and access rules you set.
The capabilities below are grouped by the question they answer rather than by what is easiest to list. Protection features answer "who can watch this"; the player answers "what does my audience see"; analytics answers "did it work". Reading them in that order is usually the fastest way to work out whether the platform fits.
Hosting and delivery
Getting video in, and out again quickly
The pipeline every other capability sits on top of.
Video hosting
Account-scoped uploads, transcoding into an HLS ladder planned from your project settings, and delivery to viewers through the player. The core product page, including how cost is decided.
Live streaming
RTMP ingest from the encoder you already use, HLS playback through the same embed, scheduling and multistream — with the encryption and retention boundaries stated plainly.
Adaptive streaming for uploaded video
Where a project produces several renditions of an upload, the player selects between them from the connection it observes and switches mid-playback. Live streaming is a separate, simple path: one encoder contribution, no ladder.
Delivery and bandwidth
How delivery is measured, why adaptive streaming changes what a view costs, and how to estimate a month before you commit to a plan.
Protection and access
Control access and add visible attribution
Four separate mechanisms rather than one "security" bucket, because they solve different problems and have different limits.
Screen recording protection
Layer practical capture deterrence, viewer attribution and access controls according to the value and audience of each video.
Online video encryption
AES-128 packaging for on-demand HLS, with key requests following the allowed-origin rules you configure — an empty list or the account-level key exemption leaves them unrestricted. An intercepted segment is not a watchable media file.
Video DRM protection
Certified Widevine, PlayReady and FairPlay paths, where each licence request re-runs your authorisation rules and refuses replayed or revoked sessions. Entitlement-gated.
Dynamic watermarking
A subscriber identifier or client IP overlaid on playback when available, plus the Screen Shield deterrence pattern. Attribution rather than prevention.
Presentation and access management
What your audience sees, and what they are entitled to
The surfaces your brand appears on, and the model that decides what a member can reach.
The player
Appearance and behaviour options per project, your logo on plan-entitled accounts, adaptive playback, subtitle and audio tracks, and casting where the viewer’s device supports it.
White-label branding
Carry your brand through the player, configured per project so one account can present several distinct video experiences.
Video subscriptions
Subscribers, plans, subscriptions and access grants — the access model your own billing system drives. Access management, not payment collection.
Channel pages
A hosted, branded page that presents a project’s library to an audience, so a catalogue has somewhere to live besides individual embeds.
Automatic subtitles
Generate and translate editable transcripts, or upload WebVTT and SRT files per language, then deliver every published track through the same player.
Build and measure
Making video part of your product
For teams where video is inside the application rather than beside it.
Video hosting API
Video, upload-session, project, live-stream, subscriber, subscription-plan, subscription and access-grant operations, three upload paths, and webhooks.
Video analytics
Aggregate plays, watch seconds, completion, audience, quality and bandwidth, plus optional customer-supplied user identifiers on Plus and larger plans.
Documentation
Procedures, parameters, examples and limitations for the parts you will actually configure.
Developer quick start
Authenticate and make a first request against the current contract.
Before you compare
Match capabilities to the right plan
This page describes what the platform can do. It deliberately does not tell you what your plan includes, because that changes and a feature page is the worst place to keep a copy of it. The plan cards on the pricing page render the current billing catalogue, so what you read there is what you would be buying.
- Plan inclusions, storage and delivery allowances: the pricing page, read from the live catalogue.
- Entitlement-gated capabilities — DRM, dynamic and IP watermarking, player branding: confirm for your plan before a launch depends on them.
- Protection modes are per project, and certified DRM and AES-128 are mutually exclusive on the same project.
- Encryption covers on-demand delivery, and HLS segment encryption is available for eligible live streams and plans — confirm it for your stream before a sensitive event.
- Custom user analytics is available on Plus and larger plans when your embed supplies your own user identifier.
If one of those boundaries is decisive for you, ask us to confirm it in writing before you commit. We would rather have that conversation now than have you discover a gap during a launch.
Try the parts that would decide it
Upload a real video, lock it to your domain, embed it, and look at the reporting. The features that matter to you will be obvious within an hour.