Hi,
I think the problem here is that my.openHAB is rather a piece of complex infrastructure than some source code.
The main feature that could be „duplicated“ within personal cloud-instances is the remote access. But this is nothing more than a reverse proxy and there are many ways you can easily realize this on your own - most securely probably using a VPN. my.openHAB is simply the service for the users who are NOT capable enough to setup their own VPN, DynDNS, etc.
Besides remote access, my.openHAB brings a commercial grade SSL certificate and does the integration with GCM, APN, IFTTT etc. - all of this is tight to this specific server and can not be moved to private instances.
But I guess Victor can explain the problems best, if there is any doubt left.
So in short: We never want to make anybody dependent on a cloud service, that’s why most of our users are happily using openHAB without my.openHAB. It is really just a service to make life easier for users, who do not want to deal with the complexities of remote access, push notifications etc.
Best regards,
Kai