# Paul Nguyen, Head of Engineering (Indie Consulting, Formerly Media SaaS) — read of iroh-p2p-video-collaboration, June 24 2026

> 12 years in software, 4 of them at a startup that built cloud video review tooling. I know what Frame.io charges per seat. I take BART from Oakland, do jiu-jitsu three nights a week, and I read IndieHackers the way some people read the news.

---

## How I got here

Someone dropped this in the #tools channel of a Slack group I'm in for indie operators. The message was just the link, no context. That alone made me curious -- the people in that group don't share things unless they think it's worth at least 90 seconds of attention. I clicked expecting either a live WebRTC product or someone's open-source repo. I got neither.

## What I clicked first

The hero is doing a lot of work: "Edit together, anywhere. Peer-to-peer remote video collaboration. Real-time sync. No servers. No latency."

I stopped at "No latency." That is not how networking works. P2P is faster than a roundtrip through a data center, sure, but it is not zero latency. My first instinct was: whoever wrote this has either never shipped a distributed system or is writing for an audience that won't push back on that claim. I kept reading because I wanted to see how deep the technical hand-waving goes.

## Where I paused

The "How it works" section actually calmed me down a bit: "Timeline changes sync without requiring a server in between. Your media files stay on your local drives." OK -- so this is CRDT-style timeline sync over a P2P channel, not actual video streaming between peers. That is a real, buildable thing. It's basically what Liveblocks or Yjs does for documents, applied to a video timeline. That's not magic, but it's also not nothing.

The cryptographic signing line ("All edits are cryptographically signed to prevent tampering") caught my eye as unusually specific. Most idea pages this vague don't bother with implementation detail. Either someone who knows the domain wrote this, or they're cargo-culting security language. I genuinely couldn't tell.

## What I distrusted

Three things, in order of how much they bothered me:

First: "Start editing now." That button goes nowhere useful. There is no product. The hero is written like a SaaS landing page but the actual offer doesn't show up until you scroll to the scoring section. The mismatch between the tone of the top half ("Start editing now") and the reality of the bottom half ("we don't have live customers on this idea yet") is jarring. If I hadn't read all the way down, I would have bounced confused.

Second: "$-33,948 Year-1 take-home (Fermi)" and "1 in 11 Meaningful-success odds" and "financial upside: 1/10." I respect the honesty. I actually do. But these numbers are doing a number on the pitch. You are asking me to pay $99 to adopt a business idea that your own scoring system says has a 1 in 11 chance of meaningful success and a first-year take-home that is negative. The honest disclosure is refreshing. The math is not inspiring.

Third: The whole "Wishdeal Factory scores every idea against 10 Adoptability axes" framing. The axes sound rigorous ("buyer clarity: 10/10," "credibility: 9/10") but there is no methodology linked, no description of what "market openness: 4/10" actually means or how it was measured. It feels like a rubric built to create confidence without being auditable. I would want to see what "credibility: 9/10" is based on when there are zero live customers.

## What would convince me

I don't need case studies because I understand this isn't a live product. What I'd need is:

A working prototype or technical proof -- even a 3-minute Loom of two machines syncing a DaVinci Resolve timeline over a LAN with actual latency numbers on screen. Not a demo of the concept. A recording of the code actually running.

Competitive positioning that takes Frame.io seriously. The page says "No monthly bills. No vendor lock-in." Frame.io is $15/seat/month. That is not the barrier. The barrier is that every post house already has it and their clients expect it. The page doesn't grapple with why an editor would switch workflows, only with why cloud is conceptually bad.

One real person who's seen this pitch and said something specific. Not a testimonial -- even an unattributed "a post-production supervisor at a 20-person studio said X" with a real reaction.

## What I'd ask in an email reply

1. The page says "timeline changes sync instantly" but media stays local. So what actually happens when a collaborator who doesn't have the source files tries to view a change? Do they see a proxy? A placeholder? Nothing?

2. How does session discovery work? "Join a session by sharing a simple link" is fine for the pitch, but P2P connections fail constantly behind NATs and firewalls. Are you using a STUN/TURN relay? Because if you have a relay server, "No servers" becomes a marketing claim rather than a technical one.

3. The $99 "adopt" tier includes "working code starter." What is that, exactly -- a repo with WebRTC boilerplate and a Premiere plugin skeleton? Or something that actually runs?

## Verdict: on-the-fence

The underlying idea is real and genuinely underexplored. But the page is confused about who it's talking to: the hero talks to video editors, the pricing structure talks to entrepreneurs, and the honest-math section talks to people who are comfortable with startup risk math. I'm the third person, and the numbers aren't making the case. I'm not closing the tab, but I'm not clicking $99 either.

---
*Memo by skeptic persona, generated 2026-06-24. Studio breaks own self-grading loop.*
