Great, I appreciate getting back control on my files, and it seems this could help. For instance a web-app could have some configuration and save it in a text file instead of in some cookie or session data. Then I could backup this config, sync it with other accounts, etc. For any serious web-based editing, I certainly would need such a tool.
By the way, recently I started to use BTsync to get back control (I would prefer an open-source implementation, but hey) and it feel so much better. Sample workflow: take picture with DSLR, import them on desktop at work, near-instantly get them synched to my phone, check and remove bad shots on my phone, also rotate and adjust them, have the edited and filtered pics ready on my laptop back at home, have all the thing on a linode where I have some scripts doing renaming and analysing. And, guess what, all of this in China, where dropbox and google drive are often unreachable.
The most important in this workflow, which I also use for music, is that when I remove a picture or a track, I want it removed from all the devices, and never come back before my face. It is suprisingly difficult... (In both senses: it is artistically difficult and necessary to decide to delete for good a file, and it seems technically impossible with services like Google photo, Dropbox's camera upload, etc.)
This is a very exciting project! Well done! This and the "Remote Storage" movement  seem to be making movements towards a web with data in the hands of the users. This is important if smaller SaaS companies want to sell into the big enterprise that have strict policies about data storage remaining on the internal network.
I can see the use case, but I can't yet figure out how MakeDrive is different from a syncing solution (say, OwnCloud, SparkleShare, SeaCloud etc.) combined with a node.js service which allows to access local files.