I see your point, but I also think that most of the value in what we are offering here is the ability to turn WordPress on/off on demand, so you can forget about it after the changes.
How could this be achieve without hosting files and DB?
Sure, that's the front-end and the service you are providing, just the ability to use WP. Sure it's great that it's not "on" unless I'm editing or using it, but why not add an option to build/output the static to a user's Git account? I understand that may not be the market you are going after, however I don't think it will lose you any of the customers who just want an WP/hosting easy-button; it will just add the customer who know's what they are doing a little bit, can work with Git, and wants to host it where they want. I think you can only win by adding this as an option/feature..
Ok, about this we will release soon a new feature where users will be able to deploy their static site on a custom ftp/sftp server.
Adding a git repo as destination won't be a problem :-)
indigodaddy|8 years ago
zener79|8 years ago