But AFAIK it is not even a definate that they will ever end up doing that, let alone when.

Personally I agree that it would be a great thing, but we'll have to wait and see.

In the meantime I would personally be arguing the point further up the chain of command at your work. Surely they undestand the importance of backups? (There's probably a policy about that?!) And AWS storage is pretty cheap and far more reliable than a local hard drive, tape or DVD will ever be! I think if you did a bit of homework around what your works privacy, security and data protection policies are, and some research on how they are satisfied by the Hub and its interface with AWS (eg data encryption, private keys, AWS reliability, etc) I think you could make a near bullet-proof case for allowing use of TKL Hub for backups in your corporation.

So could you focus in more specifically on what part of the Hub your organization would object to you using? Maybe we can work around that somehow.

Regarding supporting private instances of the Hub, that's tricky. The current design doesn't support that. It might not be obvious, but TKLBAM owes a big part of the streamlined usability to the tight integration between the appliances, the Hub and Amazon Web Services.

The Hub was designed as infrastructure, not as standalone software that you could run private instances of.

OTOH, it actually does make sense that you would want to do this in certain circumstances, but I imagine this would mostly be a requirement of large bureaucratic organizations, which TurnKey so far has not been targeted at. It's a different world which we don't really know much about.

It helps when people such as yourself share their perspectives from behind "he iron enterprise curtain". Eventually, we'd like to make TurnKey as universally appealing as possible, but it will take time. On the flip side, there could be opportunities in serving large organizations. What they sometimes lack in good sense they make up for with access to resources which the open source community could find a good use for.

OK, Liraz maybe I misunderstood some parts....

I am only interested in the backup and migration part...without being dependent on the hub while I doing a backup or a restore...

If I need to connect to the hub once every xx time for getting the correct backup profile or a profile for a migration, I don't mind. that is just as the security updates... 

So at first registering at the hub and getting the correct backup profile for the current appliance sounds good. But what is needed for a restore if something went wrong ? Do I need to connect to the hub first or is that information stored with the backup.

The only objection about the hub depends how critical it is in a backup/restore situation. If it is not required at that moment, then there is no problem.  If it is required then I have to guarantee it will be there when needed. But what I understand from the demo is that I need the hub for seeing the backuplist and I need to use it for restoring..

Yes, large bureaucratic organizations is a challenging world...  Sometimes it is easier to try to work around the rules, buy something yourself and write some extra hours instead of trying to do that officially, which probably won't work or take months...... purchase orders, approvals, preferred suppliers..... For technical people it can be very very frustrating... :)