I'm Eric — a recording and mixing engineer in Montreal.

The problem, from my point of view

A session can easily weigh 20, 40, 100 GB — stems, alternates, three versions of the same song. Sending large files to my clients and partners was miserable. WeTransfer caps you at 2 GB free. Dropbox throttles your bandwidth. And every send means uploading the whole thing to a server, waiting, then making the client wait to download it — twice the wait, and a copy of unreleased work left on a server I don't control.

Why it's built this way

So I built the tool I wanted, with my friend Francis. I spent two decades developing complex, secure software for enterprises — VP of Products at a couple of companies that got acquired, a patent somewhere in there — so the encryption isn't an afterthought bolted onto a demo, but there by design:

• Device to device. Straight from my machine to yours, or to my own machines, wherever they are. Nobody waits twice.
• No ceiling. 400 GB sends the way a photo does.
• Nothing left behind. Bandwidth used at 100%. No material sitting in a cloud you don't own. Peeza keeps no copy — it never had one.

How I keep Peeza alive

The relay that carries fallback traffic is mine to run, and a small paid tier will eventually cover it. No investors, no acquisition waiting to hollow the product out.

Beyond Peeza

When I'm not building software, I'm mixing records at Studio le cachot →. Twenty-odd years leading product and engineering before that — the enterprise-software chapter's on LinkedIn → if you want it.