Video
Video in the same control plane
Upload library videos once; SialFlow owns project binding, tenancy, and publish URLs while encode and ABR delivery run on the managed video path. Transcription, chapters, and smart crop remain roadmap.
What you get
Library upload & bind
Upload and bind videos per project. After conversion, the portal surfaces HLS, DASH (derived), and progressive MP4 when ready.
Same tenancy rails
Videos sit beside images and documents under org → workspace → project. Capacity meters include library video bytes.
Flow ingest (optional)
Flow step library.video.ingest hands a project object into the managed video path (sync, size-capped). Large files use portal chunked upload.
Honest roadmap
Subtitles, chapters, smart crop, transcription, and live streaming are not pretended live. Interactive video projects stay optional.
Differentiation
What ships on video today
- Library list / upload / bind / import
- ABR HLS + derived DASH + progressive flavors after conversion
- Project-scoped exclusive bindings
- Flow library.video.ingest (object → managed encode, ≤256 MiB sync)
- Interactive project playback/embed when kind=project
- Native in-process VOD encode — not the product path
- Transcription / scene AI — roadmap
- Live streaming — deferred
Example
Same auth and tenancy headers as the rest of the API. Where a capability plugs into Flows today, that is called out on the product page — we do not imply every media type shares one live pipeline yet.
POST /v1/library/videos/upload
# Multipart upload (portal BFF or API). Encode transfer may finish async.
# Or Flow: library.video.ingest with object_id (sync ≤256 MiB).
{
"object_id": "obj_01J8V...",
"step": "library.video.ingest"
}Ship with Video
Open the portal, follow the docs, or talk to us about rollout for your agency or commerce stack.