I work for a company that does a lot of work for other companies who, in turn, have multiple clients of their own.. Each of our clients has expressed an interest in us providing a community/social platform to them, that they can offer to their clients

Of critical importance in such a process is that each community be separate for confidentiality reasons. Suppose our client ABC is conducting research and developing communities for two competing soap companies and a third, a soft drinks company.. We'd want to be able to say to our client "yes, the following URLs lead to online communities where there is a forum, members have wall posts, can upload photos, message each other etc, and the URLs are http://ourserver.com/ABC/LeverBrothers, http://ourserver.com/ABC/JohnsonAndJo... and http://ourserver.com/ABC/CocaCola "
ABC can then advise certain people out there in the real world, that there is a place where they can discuss their use of various products.. As noted though, it's of crucial importance that cocacola registered users cannot just stray into the other boards (unless they are invited to sign up for them by ABC)..

And we don't really want to get into running multiple sites in IIS, one for every client of our client.. Just wondering if one instance of DNN in one IIS can play host to multiple communities that do not intereact with each other, and there's an easy management interface for manipulating them.. ?

Thanks in advance for any assistance