Can AI replace Frame.io?

KINDA · weekend project

price $25/moyou'd save $300/yrbuild time weekendcategory 🎬 audio & videoreplaced by 0 peoplebuild unverified

The review loop itself is not the hard part: a player, timecoded comments, version stacking, and an unlisted share link are a weekend of work for one editor and a few clients. What you cannot rebuild is the rest of the product · Camera to Cloud from set, the Premiere and Resolve panels that put comments on your timeline as markers, transcoding and CDN delivery that hold up when a client scrubs a 4K cut from a hotel wifi, and the security paperwork studios ask for. Solo and small-shop review is genuinely vibecodeable. Delivery infrastructure is not.

the prompt

Build me a video review and approval app to replace Frame.io for a one-person edit shop. Requirements:

- Node + Express + better-sqlite3 running on my own VPS behind an existing reverse
proxy. Server-rendered pages, one vanilla JS player, no frontend framework.
- I drop a master into ./incoming/<project>/<asset>.mov; chokidar picks it up and
ffmpeg writes a 1080p H.264 proxy and a poster frame into
./media/<project>/<asset>/v<N>/. Frame rate comes from ffprobe.
- Versions stack: the same asset name dropped again becomes v2, v3, and so on. The
review page gets a version dropdown that swaps the source at the current playhead.
- Each asset has one unguessable /r/<random-id> link. A reviewer types their name
once into localStorage, then comments; every comment stores the exact frame and
renders as HH:MM:SS:FF at the asset's real frame rate.
- Comments list beside the player and tick along the scrubber. Clicking one seeks to
that frame. Each has a reply thread, a resolved checkbox, and an unresolved filter.
- An export button per version writes notes.csv (timecode, author, comment, resolved)
and a DaVinci Resolve marker .txt I can import onto the timeline.
- SQLite holds comments and versions, media stays in plain folders, so nothing is
trapped in the app. No accounts and no telemetry: admin pages sit behind basic auth
with the password in .env, share links are the only other way in.
- Out of scope: Camera to Cloud, NLE panels, watermarking, and a mobile app. Do not
build accounts, teams, or roles. The unlisted link is the entire permission model.
- README: installing ffmpeg, raising the proxy upload limit, and an honest warning
that you now own the storage bill, the egress bill, and the 2am playback outage.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

why people still pay

They pay so the client link never buffers and the note never gets lost. A director opens a Frame.io link on a phone in a car and it plays; the editor opens the Premiere panel and the same notes land on the timeline as markers. That round trip, plus a transcode and delivery layer nobody has to think about, is the product. The comment box was never the expensive part.

what you lose

xCamera to Cloud ingest straight off set

xPremiere, After Effects, and Resolve review panels that sync comments to timeline markers

xa transcode farm and global CDN, so client playback is only as good as your box

xforensic watermarking, SSO, and the security posture studios require

xthe iPad and mobile review apps clients actually use

xstorage, transfer tooling, and uptime bundled into the seat price

prior art · use these instead of building, if you'd ratherKitsuOpen-source production tracker with a real review loop: versioned previews, annotations, and comments. Heavier than a share link, but the closest self-hosted equivalent.↗OpenRVAutodesk's RV, open-sourced under the ASWF. Reference-grade review playback and annotation for desktop; no web sharing layer.↗