|
I would imagine that you'd probably have two types of customers, the ones that want to host it on premises, and the ones that want you to host it for them so they don't have to think about it. Take Atlassian for example, they offer Bitbucket as well as Stash to satisfy the needs of different customers. For the ones that you host for them, does it have to be a separate environment for each customer? Or could you turn it into a multi-tenant solution where you can host multiple customers on the same set of servers? quote:What kind of support would the company be expected to give to whomever buys the rights to use this service? That's really a business strategy question that I don't think we can give you an answer for. The short answer would be, whatever they are willing to buy that you are willing to sell. For some businesses, support/services is a big chunk of revenue. For others, not so much. As far as the packaging/distributing question, there's a lot of different answers. Maybe something like a custom AMI on the Amazon Marketplace that is pre-configured and ready to roll so customers can spin it up and pay you by the hour for usage. Or maybe you spin up that AMI and manage the EC2 instance for them. Or maybe you could have a 'Deploy to Heroku' button and handle billing separately. Maybe you just send them a Vagrantfile or Dockerfile and they can do whatever they want with it. Maybe it makes sense to use something like Chef or Puppet in conjunction with these others so you can easily make changes to all the different customer environments at once.
|
#
¿
Jan 6, 2015 04:19
|
|
|
|
| # ¿ May 14, 2024 09:59 |
|