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 on the free tier. 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 three 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.

No rocket science

None of this is invented. A transfer tool is a utility, not a research project — the encryption is the same AES-256-GCM and X25519 everyone else uses, applied the way the textbooks say to. That's the point: nobody should be inventing ciphers to move your stems around.

What's new is who does the assembling. I directed Claude Code the way I used to direct a dev team — I picked the patterns, it wrote them out, I read what came back. Some engineers will wince. But the job was never novelty. It was getting accepted patterns right, then getting out of the way.

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.

Get in touch

A question, a problem with the app, or something peeza should do: write to me at [email protected]. I read every message. For a bug, Report a bug in the app's account menu sends me the app's version with it.