Do you want to play a crucial role in shaping Jet Global products?
I think that we need to distinguish configuration database from reporting Jet Hub database. Reason for that are backups that we are making on JetServices database and possibility to move configuration for JAC to another environment. If customer is using Jet Hub constantly our JetServices database grows really fast. Backuping and maintaining big database might be unnecessary as we would like to store only configuration for users, datasources and permissions. If someone would like to store also backups for every Run of the report he could use different database instead, like JetHub database.