Why I built AetherCut I spent three decades writing code as a hobbyist. Small utilities, weekend experiments, scratch-your-own-itch tools. None of it left my hard drive. Sometime in 2025 I tried to edit a short personal video and got stuck inside a workflow that wanted me to upload the file to a server I didn't control, wait for it to process, and trust whoever was on the other end with the footage. That bothered me. So I started building a browser-only editor where the video never leaves the device. The tool became AetherCut. Three engineering degrees turned out to be useful for one specific reason: none of them are computer science. The mechanical and electrical degrees trained me to think about systems with hard physical constraints — battery, memory, bandwidth, heat. The computer forensics degree trained me to assume every byte that leaves a device is a byte the user no longer controls. Put those together and you get an editor that runs entirely in your browser, measured in DevTools, with no server-side video processing to apologise for.

AetherCut

Privacy-First Zero Uploads, Verifiable in DevTools

Privacy-First Zero Uploads, Verifiable in DevTools