Hi, I’m Waimun. Armadoc started as the version of secure file sharing I wished already existed, then quietly grew into the version other people wished existed too. Here’s the short story.
I needed to send a stack of personal documents to someone I trusted. Email felt wrong — attachments linger in inboxes and on servers I’d never control. But the cloud tools felt wrong too: they’re built to store your files, not send one. Sharing a single document meant dropping it into a permanent drive the provider could read, wiring up access for a one-time handoff, and trusting myself to revoke it later. I wanted to hand someone a sealed envelope that opens once and disappears — not give them a key to my filing cabinet.
I’m a software engineer by trade. I’ve spent fifteen years building web applications across healthtech, edtech, and financial services — the kinds of places where data sensitivity is a daily concern. Between roles, I sat down and started building the version of this that should have always existed: end-to-end encrypted, recipient verified by a one-time code, no signup required on the receiving end, and gone from my servers when the link expires. That became Armadoc. I still use it for my own paperwork — every rough edge lands on me first.
It would be easy to write “built by a small team” and let you assume there are five of us. There aren’t. There’s one. I write the code, run the infrastructure, answer the email, and decide what ships next. For a product that handles your most sensitive files, I think a small surface area is a feature, not a footnote — fewer engineers means fewer hands on the keys, fewer accounts with production access, and fewer people who could quietly change what the system does with your data.
You don’t have to take my word for any of this. Your file is encrypted in your browser with a one-time key, and that key is sealed so only your recipient’s device can open it — using a private key that never leaves their browser. The encrypted blob sits on my storage; the key that decrypts it never does. When the link expires, the blob is permanently deleted. There is no admin tool that can decrypt your files, because the server never holds the key that opens them. That’s not a policy. It’s how it’s built.
The boring commitments are usually the important ones. So:
Armadoc is funded by Pro subscriptions and nothing else. There are no investors, no acquisition target, no growth team optimizing for engagement metrics. The product earns its keep by being useful enough that some of you choose to upgrade, and that’s the entire business model. It keeps the incentives clean, and it keeps the roadmap honest: the next thing I build is the next thing that helps the people already paying.
If any of this resonates — or if you’ve got a question, a concern, or a feature request — I’d love to hear from you. The reply will come from me, not a help desk.
hello@armadoc.linkWaimun Yeow