Cloudflare Stream

Build the smallest Stream integration that satisfies the product contract. Treat Stream as an asynchronous managed video pipeline: the application owns authorization and business metadata; Cloudflare owns ingestion, encoding, storage, and delivery.

Before changing code

1. Inspect the repository's existing Cloudflare client, configuration, domain model, webhook handling, player, and tests before adding anything.
2. Identify the actual mode: on-demand upload, direct creator upload, playback, live, analytics, or lifecycle operations.
3. Fetch current Cloudflare Stream documentation through Context7 before relying on endpoint schemas, limits, pricing, beta status, or SDK syntax. Prefer the official Stream docs and API reference. Never invent an endpoint or field.
4. Read only the references needed for the task:
   • Product fit and architecture: decision-guide.md
   • Authentication, API conventions, and video lifecycle: api-lifecycle.md
   • Uploads and media preparation: uploads.md
   • Playback, privacy, captions, and downloads: playback-security.md
   • Live streaming: live.md
   • Webhooks, analytics, costs, limits, and operations: operations.md

Non-negotiable boundaries