How We Built a Cloud Agnostic SaaS for Video Review

Most SaaS post mortems start with a victory lap. This one starts with a bill.

We were three months into building PlayPause when a single region outage took a chunk of our media offline for a few hours. Editors could not pull their cuts. Clients could not leave comments. The whole point of a video review tool is that the video is there when someone wants to look at it, and ours was not. That outage is the reason we went cloud agnostic. Not for a slide in a pitch deck. Because video files are heavy, expensive to move, and the worst possible thing to lock into one vendor's whims.

Here is what we learned building a video review and approval platform that does not bet the company on a single cloud, and why that decision quietly makes the product better for the people who actually use it.

Why Cloud Agnostic Matters More for Video Than Anything Else

A text app can lose its database for an hour and recover. A video review platform cannot afford to lose access to the asset, because the asset is the work. When an editor uploads a 4K master, that file might be 40 gigabytes. You do not casually re-upload that. You do not want it trapped behind one provider's pricing changes either.

So we treated storage as a commodity we rent, never a marriage we are stuck in. Three rules guided every decision.

• No proprietary storage primitives in core code
• Proxies and originals stored separately so playback never waits on a huge file
• A clean abstraction layer so swapping a provider is a config change, not a rewrite

The payoff is not abstract. It shows up as uptime. It shows up as the ability to put a customer's files in the region their compliance team demands. And it shows up in price, because when you are not locked in, you keep your costs honest, and honest costs are how we hold flat per workspace pricing instead of charging you per seat like everyone else.

The Architecture Decisions That Actually Held Up

We made plenty of mistakes. A few choices, though, earned their keep and I would make them again on day one of any media heavy product.

That third point is the one people underestimate. If feedback lives loosely next to a video, every new version orphans the old notes. We tied every comment to a frame. When an editor uploads version four, the version three notes still point at the exact moment they were about. Nothing gets lost in the shuffle. That is the difference between a tool that organizes feedback and a folder that hoards it.

Version stacks came out of the same thinking. Instead of v2_final_FINAL_thisone.mp4 scattered across a drive, every cut stacks under one asset. You scrub through the history. You put two versions side by side and compare them frame by frame. When a client signs off, an approval lock freezes that version so nobody quietly swaps the file after the yes.

How This Shows Up for the People Leaving Feedback

None of this architecture matters if the reviewer experience is clumsy. A producer does not care that your storage is portable. They care that they can open a link, scrub to 0:42, and draw a circle around the logo that is the wrong color.

So the agnostic backend feeds a deliberately simple front. Frame accurate comments with drawing tools and @mentions, so a note lands on the exact frame and the right person gets pinged. Guest upload with no account, so a client or a freelancer drops a file in without another login to forget. Secure share links you actually control, with passwords, expiry dates, domain restriction, and watermarking, so a rough cut does not wander off into someone's group chat. Viewer analytics, so you know whether the client even watched before they say it looks great.

Picture a real Tuesday. A brand client needs a 60 second spot approved by end of day. The editor cuts version one and shares a password protected link that expires Friday. The client watches on their phone during lunch, taps to 0:42, and leaves a frame accurate note: logo too small. The editor sees the comment land on the exact frame, fixes it, uploads version two. Both versions stack under one asset, ready for side by side compare. The client approves, the approval lock snaps the final version in place, and a Slack message fires to the whole team. No email thread with seven attachments. No guessing which file is current. No per seat invoice for adding the client to the review.

The Pricing Decision Hiding Inside the Tech

Here is the contrarian part. Most of the industry charges per seat, and that pricing model is not a coincidence. It is a consequence of architecture and investor math. When every collaborator costs money, you think twice before adding the freelance colorist or the client's marketing lead. The tool that is supposed to gather feedback starts pushing you to gather less of it.

We went the other way on purpose. Because we are not locked into one expensive cloud, we can price by workspace, not by head.

And to be blunt about the alternatives that are not even review tools: email, WeTransfer, Google Drive, and Dropbox move files around just fine, but they were never built to collect timestamped feedback, stack versions, or lock an approval. You can absolutely run your review process through a shared Drive folder. You will also lose track of which file is final, where the notes went, and who actually approved. That is not a workflow. That is a future argument waiting to happen.

What I Would Tell You Before You Build or Buy

If you are building a media product, stay portable from the first commit. Abstract your storage, separate proxies from originals, and tie feedback to frames, not files. The agnostic choice feels like extra work on day one and pays you back every day after in uptime, flexibility, and pricing freedom.

If you are just trying to get a video approved without the headache, the lesson is simpler. The right tool gathers feedback instead of scattering it, keeps every version straight, locks the approval so it sticks, and lets you share securely without leaking. And it does not punish you with a per seat fee for inviting the people whose opinions you actually need.

That is the whole bet behind PlayPause: a frame accurate review and approval platform that stays affordable because it stays portable.

Try PlayPause free. Upload a cut, share a secure link, and watch how much faster the yes arrives when feedback lands on the exact frame and nobody is counting seats.