Public launch plan

Production roadmap

The local MVP is now strong. These are the major upgrades needed before opening the tool as a public hosted service.

User accounts

Add secure login so jobs, cloud connections and review links belong to authenticated users.

Move source uploads and previews into private object storage such as S3, R2 or Supabase Storage.

Run video processing on a separate worker/server rather than inside the web app host.

Store jobs, shares, users, cloud provider metadata, expiry dates and audit events in a database.

Use encrypted OAuth tokens, signed URLs, rate limiting, stronger password hashing and access logs.

Add domain, analytics controls, onboarding, pricing, help docs and production legal review.

Suggested production structure

Frontend: Vercel / Next.js app

Worker: Dedicated FFmpeg processing server

Database: Supabase or Postgres

Storage: S3, Cloudflare R2 or Supabase Storage

Auth: Clerk, Supabase Auth or custom OAuth-based accounts

Domain: mxfviewer.co.uk or mxf.ninththeory.co.uk