This may be a solution further down the road but our code at the minute changes literally daily and it would be counter productive to have to test every deployment against previous versions
We actually discussed this very point in work today, I still class our product, 2 years down the line, to be in beta. We are actively working towards a version 1, if you will.
We could revisit at a later point and probably will but the time it would take to document all db changes and create a version every day would far outweigh the benefits.
Distributing to other peoples data centers comes with it's own host of issues as well, we would have to charge for a maintenance contract for 1. We would need to bring on a customer service team to support people. At the minute, bug fixes can come straight to developers via our technical director as we can deploy straight away. We would need a team to asses what their setup is, if they have everything needed installed etc etc.
Deployment to our own servers helps us and the customer a lot, we don't charge a lot for hosting, our uptime last year was over 99.97% and bug fixes and functionality are rolled out on a daily basis without interaction from the customer.
We did a massive project recently that the customer ended up deployment on their own $5 hosting company, turned out the company didn't support what we needed and we ended up coding around the road blocks. Ended up costing the customer more.