Membership access

Video subscriptions, where the access is managed and the money is yours

A video subscription is two systems pretending to be one: something that collects money, and something that decides who may watch. DynTube is the second. Keeping them separate is what stops a cancelled member walking away with a link that still plays.

Start free trialSee the subscriptions API

Access that ends when the subscription does

  • A member record that matches yours

    Create a member for a person in your own system and read their state and activity.

  • Plans that describe what may be watched

    Attach a plan when your billing says they are entitled; manage it when that changes.

  • Gated video that is actually gated

    Encrypted delivery, domain-restricted keys and signed links with expiry.

  • Engagement you can attribute

    Retention and completion per video, tied to your own member identifier when you pass one.

The problem this solves

Make video access follow the subscription lifecycle

Almost every gated video library fails in the same place. Payment is handled properly, the member area is behind a login, and the video URL underneath works for anyone who ever had it.

Without control

Gating the page, not the video

The member area requires a sign-in. The video it embeds does not, so the protection ends at the page boundary.

  • The playback URL works for a cancelled member
  • The embed plays wherever it is pasted
  • Nothing connects access to the payment state
  • No record of which member shared what

On your own terms

Gating the playback

Playback needs a key, the key needs a rule, and the rule follows the member record your own billing keeps current.

  • Segments are encrypted; a direct fetch returns ciphertext
  • Key requests follow the allowed-origin rules you configure
  • Signed links expire and can be view-limited
  • Plan changes in your backend change what a member may play

The distinction that matters

Connect access to the billing system you already use

Your product keeps the commercial relationship while DynTube applies the viewing entitlement that your backend sends.

What DynTube doesAccess management
Holds members and plans, decides which member may play which video, encrypts delivery, restricts playback keys to your domains, and reports engagement.
What your product doesPayment collection
Presents the offer, takes the money through your own payment provider, keeps the customer record, and tells DynTube when entitlement starts and stops.
How they meetYour backend
One API call when a payment succeeds, and one when it lapses. That is the whole seam between the two systems.

The verified workflow

Member, plan, access — in that order

These are the calls the API actually exposes. Everything below is documented in the developer reference.

  1. 01

    Define your plans

    A plan describes what a member holding it may watch. Create them once from the dashboard or the API, and read them back when your product needs to show what is on offer.

  2. 02

    Create the member

    When someone becomes entitled, create a DynTube member corresponding to that person in your own system, so the two records can be reconciled later.

  3. 03

    Attach the plan

    One call. From that point the member may play what the plan allows, and nothing else.

  4. 04

    Manage the lifecycle

    On cancellation, payment failure or refund, your backend manages that member’s plan. Access follows your billing instead of drifting away from it.

  5. 05

    Read member activity

    Check a member’s current plans and activity when you need to answer a support question or reconcile a discrepancy.

Fitting it to what you already run

Integration with your existing site or app

Keep your product, accounts and pages in place while your backend connects billing state to the library's playback rules.

  1. 01

    Keep your sign-in

    Your application authenticates the member and keeps the session. Pass that identified member into DynTube so the playback decision follows the access rule your backend manages.

  2. 02

    Allow your domains before you publish

    Add your site and app to the project’s allowed origins and leave the account-level encryption-key exemption off. Anything else is then refused a playback key, which is what makes a copied embed inert; an empty list or that exemption leaves key requests unrestricted.

  3. 03

    Issue a playback token per request

    Your server issues a signed, short-lived token for the member in session, so a URL lifted out of the page stops working.

  4. 04

    Embed as you would any video

    The same embed grammar as an ungated video. Gating changes the authorisation, not the markup.

  5. 05

    Group the library into channels

    Channels give a plan something coherent to point at — a course, a season, a tier of the library.

Security and analytics boundaries

Protect access and measure member engagement

Encrypted on-demand deliveryOn-demand video
Segments are AES-128 encrypted with a key requested per playback, so an unauthorised segment fetch returns ciphertext. An entitled member can still record their own screen; combine encryption with access rules and viewer watermarking where available.
Time-limited accessPer link
Signed playback links carry an expiry and can be limited by view count. That is the verified form of time-based access.
Per-viewer watermarkingAvailability depends on your plan
Overlay identifying information so a captured copy points back to the member who made it.
Engagement reportingAggregate and per-user
Plays, watch seconds and completion, plus audience and device views. On Plus and larger plans, supply your own member ID or email address for per-user viewing reports.

Questions

Questions about video subscriptions

Does DynTube bill my members?

No. There is no DynTube checkout and no recurring billing for your members. You collect payment in your own product with your own provider, and tell DynTube who is entitled to watch.

Does DynTube take a cut of subscription revenue?

No. There is no commission and no revenue share on anything you sell. You pay for hosting and delivery on your plan; what you charge your members is entirely yours.

Will it work with my payment gateway or membership plugin?

The integration begins after your billing system confirms an event: your backend calls the DynTube API to update entitlement. Validate that handoff with your chosen gateway and get any required provider-specific path confirmed in writing.

Does access update automatically when someone pays?

Your billing webhook triggers the update. When payment starts, changes or ends entitlement, your backend makes the corresponding API call so playback stays aligned with billing state.

Is there a DynTube membership site I can use?

No. DynTube provides video hosting, delivery, the player, channels, member and plan management and an API. The membership website itself — sign-up, sign-in, the member area — is yours to build and own.

Can I grant access for a fixed period?

Yes, through signed playback links that carry an expiry and can be limited by view count. That is the verified mechanism; longer commercial terms are expressed by your own billing and reflected through the plan you attach.

Keep the money in your product, put the access in ours

Members, plans and encrypted delivery on our side; the offer, the checkout and the customer record on yours.

Start free trialRead the subscriptions API