Fairly much read up on JMS and I'm very impressed. Just some last minute questions before I buy the whole package.

1. While data and members are shared between master and slave (under config) the content defined to the slave sites is unique?
Meaning if I create 3 slave sites, the content will be shared to my master site. I need the content for slave1 and slave2 to never be together. Another way to look at this is that you go to slave1 site and see only slave1 content. You go to master and see content from all 3 sites. Is this true?

2. While unsure about a framework I was going to (try) to set this project up with Morph. What is the best supported framework and at a later time (If I am switching templates to work with a different framework) will JMS still function? [I.e: does JMS depend on any templates/frameworks or is it pure ACP and SQL functions?)

3. What are your TOS with regards to a free sign up blog host. Where the user (Outside party of purchase to JMS) can sign up to a site (Of mine where I will be using JMS) and get his own site.

4. What are your TOS for using/limiting JMS for profit and for bulk sites. (Under wordpress I have 230 sites running under a master) Would profit made through JMS (Pay to have a site or something) be allowed and is there a limit to how many slaves you can have?

Edit: Saw that you sell for unlimited installations.
More questions:

5. Update buying. Until what point will I be able to get updates. I read that from 1.1 to 1.2 you did not offer updates. Does this mean every major numerical update or what?

6. Does JMS support multiple servers? I might be running this project on multiple servers so would JMS be able to install slave sites across servers? (Its run on the same domain)
If it doesn't and I have to install JMS on the second server, would that be fine with TOS (Its under the same domain)

1) By default no data (content) is shared except the files and folders on the disk.
The data and members are saved in DB and as each website has its own DB or same DB with different table prefix then the content (data and members) is specific. (Not shared).

Sharing the content is a specific action that is possible for a limited number of extensions. The users can be shared when creating the slave site.

When you share an extension, all the website that share the same content will see it.
For example, if you share the users betwen the master and slave 1, slave 2 and slave 3 then Slave 1, slave 2 and slave 3 see the same info. It is shared. So identical for all the websites.
Another example, if you share the "kunena forum", all the slave 1, slave 2, slave 3 and master will have the same forum.
So you assumption is NOT true.

2) Most of the framework bypass Joomla and are not compatible when working under JMS Multisites. This include morph framework that is not compatible.
For the moment, we know that Joomlart old T3 framework (I think the 2009 version) is OK.
The latest T3 version 2 framework need a patch that we will deliver in the next release.
RocketThemes gantry framework also has a problem and a partial patch will be delivered in the next release.
Concerning YooThemes WARP 5 framework, we will release a new product that will fix the Yoothemes framework. This will be another product because it is binded to each new Yoothemes templates and because Yoothemes does not seems want to include the bug fix in their distribution.

So for the moment, we consider that all the specific template company that have developed their own framework to bypass the joomla framework are not compatible.

3, 4) What mean TOS ?

5) We consider that after 1 year that a new version is release and that customer declined all the proposal to upgrade with a lower price that the discount is no more provided and that you have to purchase the new version at full price.

www.jms2win.com/en/forum/23-general-ques...bership-get-you#5405

6) Yes and NO.
Yes because you can have the DBs located on several servers.
No because the concept of JMS Multisites is to share the files and folders on the disk.
So share the same Joomla PHP code that by definition is on the same server.

TOS = Terms of Service.
Meaning after you sell it to me, do I have the ability (Right by law) to make profit off it.

Meaning can I offer the slave site to another person? (I will be the only one for the master site)

Also meaning can I say "$5 to have your own site on our database" using JMS slave sites.

@ the other questions. Thanks for the answers. Will be buying shortly.

If you want to slave the website creation from the front-end, in this case, you have to enable the "billable website" functionlaity and buy "website quota".
www.jms2win.com/en/forum/23-general-ques...s/3926-website-quota

When the website creation from the front-end is free then there is no additional fees.

If you create website from the back-end for your customer then this is also free.

See also the "bridge for VirtueMart" that is a plugin that allow automate the "billable website" creation and that use VirtueMart to process the ordering of a "billable" website creation until its payment.
www.jms2win.com/en/joomla-multisite?page...33&category_id=1