Nearly two years ago, I was in the thick of working at Mozy, the cloud storage and backup company. If you’re curious about my time there, checkout my “Wins” page. For those of you who aren’t aware, at the core of Mozy is a mind-bendingly awesome storage infrastructure. The first years at Mozy were spent focused on that storage platform, enabling Mozy to scale from the first few terabytes of customer data stored to the 70+ petabytes of customer data it currently maintains. Never heard of a petabyte? One petabyte is 1024 terabytes. This will help.

Mozy’s infrastructure is what sets it apart from all other competitors. When we talk about big data, there are two critical considerations: redundancy and cost. The first, redundancy, is what ensures that your data is never lost. In Mozy’s case, customer data is stored across a dozen or more physical machines, potentially spanning even different data centers in distinct regions of the world. What’s more: the cost of this is mere pennies on the dollar. Mind bending.

What does this have to do with Mozy’s Stash? Mozy’s infrastructure is one the best clouds in the world. The core set of services built around this cloud is tailored to backup. What if that world-class cloud could be extended to do something more? What about giving you access to your files wherever you are, on whatever device you’re using, exactly when you need it?

Let’s take that step back in time again, two years in the past. I was a Software Architect attached to the storage infrastructure at Mozy. Just to be clear, I had nothing to do with the design, architecture, or implementation of that infrastructure. Regardless, it was my area of responsibility at the time. And the above questions bothered me. Mozy already had a fresh copy of all of your data and gave rudimentary access via the web. That was a solid start. The next problem to solve seemed obvious: synchronizing files across the devices you use every single day.

And thus Stash was born.

Pat Bozeman, our brilliant VP of Engineering, loved the idea. Others did not. So we proceeded forward with Stash as a skunkworks project. I spent the next few months prototyping, getting help from Mozy’s awesome engineering team (thanks Cody Cutrer, Jeremy Stanley, Mark Suman, BJ Homer, JT Olds, and many more!). Eventually, we had a working, screaming-fast, ultra lightweight, file synchronizing client built on Mozy’s cloud. And this is just where things started to get fun.

Once we had something to show, Ted Haeger, a Product Manager/Evangelist and one of the shining stars at Mozy, began to work his magic. He saw the potential for giving people a secure, world class, cloud-based synchronization service and how naturally it fit with Mozy’s core backup business. He ran the gamut of Mozy and EMC’s management, helping them see the value of this little skunkworks project. It was by his efforts that Stash became an official project at Mozy, with dedicated engineering resources and, as you can witness today, an official launch date.

In the thick of all of this, around 13 months ago, I made the decision to leave Mozy and take a job at Instructure. I don’t regret my decision; while I had a fantastic experience over the 5 years I worked at Mozy, 5 years is a long time to spend at any company in the software space. Unfortunately, it meant that I left before Stash’s launch and I’ve had to watch from afar as Ted and the team pulled things through to what you see today.

I’m proud of what they’ve done. I’m extremely proud to have been a part of it. It’s not often that a person has the opportunity to create something new. It was a gift for me to have had the chance to work on Stash with the geniuses at Mozy I still call my friends. Now I’ve got the t-shirt to prove:

Mozy Stash’s creator is proud of Stash.