2
1 Comment

Every major video editor is moving to the cloud. CapCut, Clipchamp, Descript, even Premiere Rush before Adobe killed it.

I'm bettting the opposite.

I'm Robert. I'm the solo founder behind AetherCut — a video editor that runs 100% in your browser. No uploads, no cloud account, no servers see your footage. You can open DevTools, hit the Network tab, import a 4K clip, and watch zero outbound traffic carry the media bytes. Verifiable in about 30 seconds.

What's actually shipped today:

  • Browser-native editor (WebCodecs + FFmpeg.wasm + MediaRecorder for export)

  • 20-language i18n

  • PWA + Android TWA on Google Play (closed test finishing today)

  • Stripe Pro tier ($14.95 one-time) — refund flow live-tested this week

  • 100+ regression tests, including a pytest that fails CI if marketing copy uses words like "best" or "the only"

The honest numbers:

  • $0 MRR — Pro tier ships when Play production access lands (estimated next week)

  • 12 closed-test testers, 14 days, 0 tester-reported bugs

  • ~30 indexed SEO pages, mostly competitor comparisons + privacy transparency

The most surprising thing I learned this week: my Stripe webhook was silently failing on refunds — I'd been listening for charge.refunded but Stripe was firing refund.updated and charge.updated. The money came back to the customer correctly. Their Pro flag stayed True. Caught it by doing a real $14.95 live refund test instead of trusting unit tests. I now have an admin-gated reconciliation endpoint + 13 new regression tests for the variant. The lesson keeps repeating: code-level tests prove logic; live transactions prove plumbing.

What I'm asking for from IH:

Honest feedback on the positioning — does "100% in your browser, verifiable in DevTools" land for you, or does it feel like a niche play? Also: anyone here gotten Play Store production access on a TWA? Any traps I should know about?

Thanks for reading.

posted toAvatar for product AetherCut
AetherCut
  1. 1

    I'd be careful with one thing.

    The interesting question may not be whether the privacy claim is true.

    It's whether that's the reason someone ultimately chooses the product.

    Those can look aligned early on while leading to very different conclusions about what is actually being validated.

    I wouldn't make that call casually in a thread.