Please see my comment to the question.
You need to understand: HTTP-based Web applications are different: 1) server-side code is not accessible to the client and
does not need protection; 2) client-side scripts are delivered to the client side in full and
cannot be protected.
The only concern could be trying to protect the code from the people working at your hosting company, but it could really would be difficult to achieve for shared Web service. Apparently, it could be possible to do for a dedicated private host, virtual or not, and of course, if you self-host the Web site. I doubt that this was your concern, but this is the only subject we could further discuss.
[EDIT]
Probably, the discussion on comments comes to the point where we need this "future discussion".
This is the concern of protection of the software from stealing by hosting company people. In this case, these are the people supporting server on company Intranet. In this case, protection is much harder. One possible solution could be: using the compiled version of the site. Please start here:
https://msdn.microsoft.com/en-us/library/399f057w%28v=vs.85%29.aspx[
^].
When the site is compiled, it can include assemblies protected using some available copy-protection products, for example, dongle-based. Of course, using the dongle resembling keeping the customers in handcuffs. Besides, any protection can be broken; at the same time, protection using purely legal means (proper license, signing of the service contract with appropriate legal terms) could work for most or all customers. I would thing first of all at this: is your software so valuable that somebody would steal it?
—SA