Use case

Video for user-generated & social apps

Social and UGC apps take video from thousands of users, transcode each to adaptive HLS, and serve it back fast without running a pipeline. Users upload straight from the browser with resumable uploads, so a dropped phone connection resumes instead of restarting; your backend gets a video.ready webhook and serves an HLS URL. Per-GB pricing means cost tracks real storage and delivery as the community grows, not a per-seat or per-minute premium.

Start free Read the docs

When to use rehelios for this

Choose rehelios when your app accepts video from many users, you need each one transcoded and delivered adaptively, and you want cost to scale with usage rather than a flat plan you outgrow.

  • Resumable browser uploads that survive dropped connections
  • video.ready webhooks — no polling a job queue
  • Signed tokens to hold a video private until it's moderated
  • Per-GB pricing scales with your community, not seats

How it works

  1. 1

    Upload from the browser

    Users upload directly with resumable (TUS) uploads; large files survive a flaky connection and never pass through your server.

  2. 2

    Transcode and notify

    Each upload transcodes to adaptive HLS; handle the video.ready webhook and store the id against the user's post.

  3. 3

    Moderate before publish

    Hold a video private with a signed token through your moderation step, then make it public once approved.

  4. 4

    Serve at scale

    Deliver from the edge; per-GB billing tracks the bytes your community actually watches.

Fastest path

One command (or one MCP tool call) gets you started:

shell 
# users upload from the browser; your backend reacts to the webhook
npx @rehelios/cli upload ./clip.mp4 --wait --json

Agents: see /agents and /mcp.