Use case
Video for SaaS apps
Drop fast, private, analytics-ready video into a SaaS product without running a transcoding pipeline. Users (or your team) upload a file; your backend gets a video.ready webhook and surfaces an HLS URL to the player. Gate private content with signed tokens per user, and bill predictably per gigabyte.
When to use rehelios for this
Choose rehelios when your app needs to store and play user or product video, you want per-GB costs that scale with usage, and you'd rather receive a webhook than poll a job queue.
- video.ready / video.failed webhooks — no polling
- Per-viewer signed playback tokens for private content
- Per-GB billing scales with real usage
How it works
- 1
Upload or import
Call the API (or
rehelios upload) when a user adds a video, or import an existing URL server-side. - 2
Get notified
Handle the
video.readywebhook and store the returned id against the user/record. - 3
Play, gated
Read
playbackUrlfromGET /v1/videos/{id}; mint a signed token per viewer for private content. - 4
Measure
Pull per-video views, watch time and completion to drive product analytics.
Fastest path
One command (or one MCP tool call) gets you started:
# your backend kicks off an upload, then waits for ready
npx @rehelios/cli upload ./onboarding.mp4 --wait --json