I am not sure if this is the correct forum so apologies if it isnt.

We currently provide webhosting services to people.  ASP, ASP.NET1.1, ASP.NET2, PHP etc with various databases. 

We are interested in providing DNN services.  I realize there is a difference between 3 & 4 and are concentrating on 4 for now.

My question is from a webhost point of view should we have one instance of a DNN4 site and database and create child portals from that or should we provide one instance per hosted site?  This is a simplified version of the real setup (webfarms etc) but the principle is the same.  For a normal hosting site we would have one instance of their site and then one database.  But DNN seems to allow multiple sites under the same site (as it builds from the database).

I have a strong .net development background but havent opened up the inside of DNN to look at the pros and cons of each.  I am sure there are many hosting providers out there who have evaluated both ways and found pros and cons to each and wondered if you would share them with us?

We also have reseller packages which may throw some complexity into the solution but i doubt it as it seems DNN can handle child portals having child portals if we go with the one instance.

How does DNN handle other domains under the one big portal scenario?  For example - if i have the dnn site as www.myhostingcompany.com and a company wants their site www.companyA.com i can setup dns to handle this normally to point to their site... but DNN has a mechanism too?  Or is this where i got lost and need to have one instance of DNN per domain?

Thanks in advance :)

Thanks for the reply
So really a mix n match depending on the package purchased... if they want a geocities type one then use the shared install and if they want a full setup with own customizations etc then give them their own instance.  Perfect... many thanks.

Now to get Helm setup with DNN ... joy! hahaha