Solutions
Start from the job, not the industry label
The same platform underneath, described by what you are actually trying to do with video. Pick the closest match — the differences that matter are in the workflow and the boundaries, and each page states both rather than repeating a feature grid.
Start from the job, not the label
How to choose
The three questions that separate these pages
Industry labels are a poor guide, because a coaching business and a fitness studio have almost the same problem, while two universities can have entirely different ones. What actually differs is who controls access, where the embed has to live, and what has to survive afterwards.
- Access: does an LMS, a membership tool, your own application or nothing at all decide who can watch?
- Surface: is the embed going on your own site, inside a third-party platform, or into your own product UI?
- Afterwards: do you need a durable archive, library-wide engagement, or customer-identified viewing tied back to your own system?
If two pages look equally close, compare who owns access, which surface accepts the embed and where the final record must live. Those operating decisions usually identify the better starting point.
Teaching and training
When somebody has to learn something
These four share a problem: the video platform delivers, and a different system owns enrolment and records.
Online courses
Paid course libraries embedded in your course platform, with protection that travels with the lesson rather than depending on the LMS.
Education
Lecture capture and teaching libraries organised by curriculum, captioned and reviewed, embedded in the institution’s LMS.
Corporate training
Internal training delivered into your intranet or LMS, behind your own authentication — with the completion-record boundary made explicit.
Coaches and consultants
A coaching library on your own member surface, with signed expiring links instead of unlisted URLs.
Reaching an audience
When the video has to do commercial work
Here the question is what surrounds the video and who keeps the attention afterwards.
Marketing
Campaign and product video on your own landing pages, with no competitor recommendation at the end, aggregate completion and optional customer-identified viewing.
Agencies
A project per client with its own player settings, team scope and documented handoff, provisioned from your onboarding.
Real estate
Property tours on your own listing pages, managed across the listing lifecycle, with portal embedding treated as a per-portal test.
SaaS products
Video inside your application, driven from the /v2 API, with your app keeping identity, sessions and billing.
Members and communities
When a group returns to the video regularly
Playback reliability and durable archives matter more here than protection does.
Fitness and studios
Workout libraries watched on phones in bad rooms, where adaptive playback is the retention lever and casting is device-dependent.
Religious organisations
Weekly services streamed to your own site plus a sermon archive that survives a volunteer handover — with retention confirmed first.
Nonprofits
Appeal and programme video on your own pages, with the donation journey left entirely in your own tools.
Healthcare
Patient education, recruitment and staff training — with a clear line between content outside regulated scope and content needing review first.
True on every page
Capabilities shared across these solutions
Use these shared mechanisms as the baseline, then use the audience page to confirm the workflow and configuration that differ for your case.
- Delivery and playbackWhat it does
- Uploads are transcoded for adaptive HLS delivery and embedded on a page you control, through a player configurable per project.
- Access and identityThe handoff
- Subscription and member access rules and playback authorization are available mechanisms. Keep learning, identity and formal completion records in the organisation-owned systems responsible for them, and confirm the exact handoff for your workflow in writing.
- ProtectionPer project
- On-demand AES-128 or certified DRM, mutually exclusive per project and entitlement-dependent, plus origin restrictions and viewer watermarking for friction and attribution.
- MeasurementAggregate and customer-identified
- Plays, watch time, completion and related rollups for the library, plus per-user reporting on Plus and larger plans when your embed supplies your own identifier.
Describe the workflow you need to support
Tell us who watches, where the player must appear and which system owns access and records. We can confirm the relevant configuration before you move a library.