Quick start
Set up a project, upload assets, generate playback URLs, and verify delivery on your site.
- Project checklist
- Folder structure guidance
- Player validation
- Launch notes
Use these guides to launch faster. The documentation overview below is organized around the real workflows teams care about: upload, embed, protect, automate, and monitor.
Most implementations begin with one of three objectives: moving an existing video library, embedding a player in a website, or protecting course content. The sections below make those paths easy to scan.
Set up a project, upload assets, generate playback URLs, and verify delivery on your site.
Learn how to add HLS video to landing pages, lesson pages, and member-only content.
Protect private delivery with signed URLs, token validation, and access rules.
No. The documentation approach shown here is framework-agnostic and works well for static HTML websites.
Yes. Public docs can support search visibility if each page has unique intent, metadata, and substantial content.
Yes. This overview is built to expand into deeper implementation guides, reference pages, and API-related articles.
Yes. Many teams reuse the same docs structure to onboard developers, content managers, and support staff.
Compare plans, trial limits, and upgrade paths.
Explore adaptive streaming, secure delivery, and playback fit.
Learn moreReview protected playback, signed access, and private workflows.
Learn moreSee how the platform fits course libraries and lesson delivery.
Learn moreLearn how to embed HLS playback on websites and lesson pages.
Learn moreCompare delivery control, privacy, and workflow flexibility.
Learn moreKeep your public website lightweight and SEO-friendly while giving your video delivery architecture room to grow.