Why I Built MnemoShare

In 2023, the MOVEit breach stopped being "industry news" for me and became something painfully personal.

It was not our fault. We were not careless. We trusted a vendor, and that trust failed in the worst possible way.

The damage was real. People lost their jobs through no fault of their own. Customers paid the price. Vendors felt the impact. Our company lost millions. There was nothing abstract about it. It was raw, disruptive, and deeply human.

And it forced me to confront something I had seen for decades in technology: we keep accepting fragile security models in places where failure is catastrophic.

Thirty Years of the Same Pattern

I have spent more than 30 years in IT, from building one of my own web hosting companies in the early days of the commercial internet to leading architecture and technology strategy for large enterprises. Across every era and every scale, I have seen the same pattern repeat: systems that are considered "secure enough" because they work the way they always have.

Managed file transfer is one of the clearest examples.

Too many legacy platforms still depend on static SSH keys that live for months or years, wrapped in layers of VPNs, IP allow-lists, and network rules that create the appearance of control without truly solving the problem. It is security by accumulation, not security by design. And when those systems fail, the cost is not just technical. It is operational, financial, and deeply personal.

We Already Know How to Do Better

The frustrating part is that we already know how to do better.

For the web, we moved forward. We embraced HTTPS, TLS, mutual authentication, short-lived sessions, stronger identity, and end-to-end protection. We stopped assuming the network itself was trustworthy. We built around proof, not hope.

So I kept asking myself a simple question:

Why are we still protecting file transfer like it is 2005?

Building MnemoShare

MnemoShare came from that question.

I did not set out to build just another managed file transfer platform. I built MnemoShare because the old model keeps failing organizations that did nothing wrong except trust the wrong system at the wrong time.

MnemoShare applies modern security principles to file transfer from the ground up: zero-trust access, ephemeral credentials, identity-bound controls, and strong application-layer encryption. It is designed to reduce standing privilege, minimize blast radius, improve auditability, and make secure operation the default rather than the exception.

Just as important, it is built for the realities of adoption. Security only matters if organizations can actually implement it. MnemoShare is cloud-native, Kubernetes-ready, integrates broadly into enterprise environments, supports modern compliance workflows, and is designed to help teams migrate away from brittle legacy systems without years of consulting pain.

More Than Technology

But the technology is only part of the story.

MnemoShare exists because I have seen what happens when this category fails. I have seen the financial damage. I have seen the stress it puts on customers and partners. I have seen good people lose their jobs because a system everyone assumed was safe turned out not to be.

That should not be normal.

We should not keep telling organizations that the answer is more perimeter layers, more exceptions, more static trust, and more operational complexity. We should be building systems that reflect the threat landscape we actually live in now.

I did not reinvent the wheel. I just refused to keep relying on one that was already coming apart.

MnemoShare is my answer to that experience — and to a problem our industry has tolerated for far too long.