Built because
the tools didn't exist.
A filmmaker's rejection letter from Frame.io turned into a tool. This is why RevCut exists — and why it's built the way it is.
The Problem
As a filmmaker and editor, I was using Frame.io to gather client feedback until it got rejected by a client's legal team. GDPR audit. US hosting flagged. AI training clauses buried in the fine print — or vague enough to raise red flags during audits. The alternatives? Either bloated project management suites I didn't need, or they had the same compliance issues or were just too expensive.
I wasn't going back to decoding timestamped emails, screenshots, or "unlisted YouTube links." Not after 20+ years of this work.
The Solution
I code. So I built what I needed: RevCut.
Upload video. Send link. Client reviews — no account, no login wall, no friction. Pin timecodes. Annotate frames. Select ranges. Export comments as PDF. Approve or request changes. Deliver the final cut in-app. Done.
EU-hosted. GDPR-first by design, not as an afterthought. Your content is yours — no AI training, no data mining, no corporate surveillance. Minimal interface. Maximum function.
Not a MAM. Not a collaboration circus. Just the bridge between rough cut and delivery. Built for solo filmmakers, editors, motion designers who need one thing to actually work.
Why It Matters
Like many of us, I got into video to make films. Ended up freelancing on commercials, music videos, corporate work. RevCut is the tool I needed for that reality. Built out of necessity, refined through use, released because it solved a real problem.
But here's the thing: if it's successful, it buys back what the industry took — creative and financial independence. Maybe it funds part of The Edge, the feature I wrote when everything fell apart. Maybe it doesn't. Either way, I'm building it and sharing it with you.
This is what happens when constraints become weapons. When the doors stay shut, you build your own. Tools that serve creators, not metrics.
Functional. Private. Yours.