Reel Uploads

Client-Side Validation
- Runs before upload begins.
- Validates:
  - MIME type
  - File size (≤ 1GB)
  - Duration (3s-10min)
  - Aspect ratio (9:16 ± 0.01)
- Gives users early feedback and prevents most invalid uploads.
Mux Direct Upload
- Backend issues a signed upload URL via the Mux API.
- Creators upload directly to Mux — Nomey never touches the raw video.
- An upload document is created immediately to:
  - Enforce creator-tier limits
  - Track pending uploads
  - Ensure webhook idempotency
  - Recover gracefully if the client or webhook fails
Upload Lifecycle & Webhooks
- Mux emits lifecycle events (e.g. video.asset.ready, video.upload.error) to Nomey.
- Handled via a webhook endpoint that:
  - Validates video duration, aspect ratio, and file size post-upload
  - Associates the assetId with the original upload record
  - Creates a reels document on success
  - Flags invalid uploads gracefully (e.g., invalid ratio)
Reel Status & UI Updates
- The frontend polls or is notified when the reel becomes ready.
- Reel status is updated in real time based on webhook events.
- Failed uploads are visible to the creator with a retry path.
Async Task Handling
- QStash is used to:
  - Schedule or retry post-upload processing
  - Trigger UI revalidation or notifications
- Built-in retry and dead-letter queue ensures reliability

Layer	Validator	Purpose
Client	`validateFileSize()`	Reject >1GB files early
Client	`validateAspectRatio()`	Enforce 9:16 video ratio
Client	`validateDuration()`	Prevent too-short or too-long videos
Server	Post-webhook validation	Final gate for content & tier enforcement

All validations are mirrored client and server-side. Client improves UX; server enforces trust.

Reel count limits are not reduced if subscriber count drops — existing creators keep their tier until they go inactive.

Area	Decision	Benefit	Cost or Risk
Upload Path	Direct to Mux	Fast UX, offloads infra	Can’t reject invalids until post-hoc
Pre-Upload Checks	Client-side	Low latency, early feedback	Can be bypassed by bad actors
Processing Pipeline	No intermediate storage	Simpler infra, fast dev cycle	Less pre-upload control
Abuse Handling	Soft-limits via logic	Lightweight, low overhead	Doesn’t fully prevent cost exposure
Status Tracking	Webhook + DB lifecycle	Traceability + resilience	Slight delay in status change

Creator uploads are KYC-gated → spam & abuse are minimized.
No free tier → storage is directly monetized via subscriptions.
Upload limits scale with subscriber count → predictable cost exposure.
QStash handles async workflows → reliable background processing with retries.
Mux handles video infra → Nomey can stay focused on product.

Invalid uploads are rare, cost little, and do not break user flow.