CORRECTED:
...and still restrict running servers based on commercial use rather than anything related to network impact in our Terms of Service, contrary to the net neutrality principle of allowing users to use any legal software on the network.
http://arstechnica.com/information-technology/2013/10/google...
Unless you're trying to run a commercial website from your apartment, but I don't think that's unreasonable.
Actually, I'd say regulating on commercial vs. noncommercial rather than traffic or even, as a fairly blunt tool, a straight server ban is actually more of a violation of the "any legal software" rule (rather, its equally a violation of that rule, and its no longer even superficially about network management, the potential basis for exception to the rule, but instead is pure market segregation.)
(And "Too much traffic" isn't a valid answer here: if I have a client, I can use as much bandwidth as I like — respecting the other sections of the ToS, which are outside the scope of this discussion.)
Even if it is not technical, it might be like garbage services in my area where commercial operations subsidize residential operations. Residential connections might be getting a discount that is paid by commercial entities and you would be cheating their pricing model.
I can't run commercial stuff on my line either, according to my contract. I think it is pretty standard to have that in the contract.
However I am way more concerned about other stuff in my contract.
It's all about economics, SLAs, etc. and network management.
They've already addressed this directly by mentioning how they plan on launching a business product eventually.
I'm perfectly ok with that.