Controlled sharing on your own pages

Private video hosting for audiences you choose

Keep business video out of a public discovery feed and place it inside the page, portal or product you already run. Combine viewer gates, configured embed origins and managed private links according to who should watch and how long access should last.

Start free trialView pricing

Private playback inside the destination you control

Choose the access model by risk

Private video workflows that need more than an unlisted URL

The right control depends on what could go wrong. A forwarded review link, a copied course embed and an internal training portal are different problems.

Internal training and company updates
The viewer should be part of the organisation and the embed should stay inside the company portal.
On DynTube — Use a login gate with an origin allowlist configured for the portal. Add viewer watermarking when the plan supports it and attribution would be useful.
Paid courses or member libraries
A purchase or membership in your own commerce system should decide whether playback is granted.
On DynTube — Keep checkout and billing in your existing stack, then grant or revoke DynTube playback access for the customer and content they purchased.
Client review and pre-release screeners
Access should end automatically and a forwarded link should not remain useful forever.
On DynTube — Issue a managed private link with a start time, expiry, maximum plays or a single-play limit, and revoke it when the review ends.
Sensitive distribution material
A contract may require a licensing mode beyond ordinary HLS encryption.
On DynTube — Arrange certified DRM before upload. It is set up per account rather than by plan tier, uses its own project and output path, and a project runs it instead of AES-128.

Layer the controls

Four different decisions behind private playback

Privacy works better when each control has one clear job: identify the viewer, limit the link, restrict the embed and protect the delivered media.

Who is the viewer?Viewer gate
Require a password, access code, account login or completed purchase. Membership and checkout remain in your application; DynTube evaluates the playback entitlement you grant.
How long may this link work?Managed private link
Set a start, expiry, maximum play count or single-play rule. Play exhaustion is atomic, so two simultaneous attempts cannot both consume the final allowed play.
Where may the embed load?Origin policy
Populate the account or project origin allowlist so a key request from anywhere else is refused, then test from an origin you did not include. Keep the list non-empty and the account-level exceptions off, because each of those deliberately widens access.
How is the media delivered?Project output
Optional HLS AES-128 protects segment bytes when the account, plan and project enable it. It requires HLS output and applies to material processed after the setting is selected.

Set it up in the right order

A private video publishing checklist

  1. 01

    Choose the project before uploading

    Protection and output defaults are captured when a new upload or conversion record is created. Changing a default later does not rewrite existing renditions.

  2. 02

    Select one delivery protection mode

    Use plain HLS with optional AES-128, or arrange certified DRM with CMAF. The two modes do not stack on the same project.

  3. 03

    Configure the origin policy

    Add the sites that should host the embed and review any account-level exceptions. Then test the video from an allowed and an unlisted origin.

  4. 04

    Choose the viewer gate

    Use the identity signal your application already has: login, purchase, password or access code. An origin rule decides where an embed may load; the viewer gate is what decides who is watching.

  5. 05

    Issue bounded links when needed

    For direct sharing, create a managed private link with the smallest useful window or play count, then revoke it when the job is complete.

Protection options

Encryption, watermarking and DRM solve different problems

Choose the control that matches the requirement instead of treating every security label as interchangeable.

Encrypted on-demand deliveryOn-demand video
When HLS AES-128 is enabled for an eligible project before processing, an intercepted segment is not a directly watchable media file without the key. Video encryption is entitled on Pro and Enterprise plans by default; the pricing page renders the current inclusions.
Configured origin rulesPer project
Where origins are listed and the relevant exceptions are off, requests outside the list are refused. Empty lists and account-level exceptions deliberately widen this behavior, so test the final configuration.
Watermarking and Screen ShieldPer request
Viewer watermarking adds an identifier to the playback session and Screen Shield adds a moving visual pattern, so a captured copy is attributable and visibly second-hand. Dynamic watermarking, IP watermarking and Screen Shield are entitled on Pro and Enterprise plans by default.
Verify the controls before launchRefusal-path test
Confirm an authorised viewer can play, then test an unlisted origin, an expired link and a revoked entitlement. Live streaming uses a separate protection boundary, and certified DRM replaces rather than layers over AES-128.

Questions

Private video hosting FAQs

Who needs private video hosting?

Teams publishing internal training, paid courses, client reviews, product education, pre-release screeners or other video intended for a defined audience rather than public discovery.

Is an unlisted video private enough?

An unlisted URL removes public discovery but does not prove who is watching or stop forwarding. Add the viewer gate, origin policy or managed-link limits that match the risk.

Can private video play on my own website?

Yes. DynTube is designed for embeds on pages you run. Configure the allowed origins and use your existing login or commerce system when the viewer must be identified.

How much does private hosting reduce unauthorised sharing?

Materially, and in three different ways: an intercepted encrypted segment is not a directly watchable media file, an unlisted origin or an expired link is refused playback, and a viewer watermark makes a copy that does escape attributable. Capture on a viewer's own screen stays possible, which is why attribution is the layer that matters for content you would act on a leak about.

Which plans include the controls I need?

Video encryption, dynamic and IP watermarking and Screen Shield are entitled on Pro and Enterprise plans by default, and certified DRM is arranged per account. The pricing page renders the current inclusions — read them there and confirm any purchase-critical control in writing before uploading sensitive material.

Test private playback with the content you actually need to protect

Use a representative video, verify the intended viewer can watch, then verify an expired link and unlisted origin are refused before you publish the full library.

Start free trialTalk to us