As for a wiki farm, and the Confluence license, I've reread the 2.1 version of your license with careful attention to your comments. I have two thoughts:

#1 Need is for a Wikifarm for Content Management On A Large Portfolio of Owned Domain Names

1) My immediate need is for a centralized system to manage websites for about 500 domain names that I own. My main income from those sites is from google ads, amazon ads, and other affiliate programs. I need the wiki to serve as many pages as possible across those domains, without duplication. Administration functions, dashboard, and maybe a few other kinds of pages could be on a shared domain. But I should be able to define one or more Wikispaces that would serve out of a given domain, and others that would serve out of other domains. For a given space, it's current pages, revisions, attachments, etc., should be served from it's domain. The shared domain should not be able to serve that content, to avoid duplicate content penalties from search engines.

I don't see how getting Confluence to serve content from a single installation onto multiple domains in any way violates the license. And I don't think you were saying that would be a violation.

A licensing need similar to Confluence wiki: Hosting control panels I'd hope Atlassian will confirm that their Confluence licensing is more like how hosting control panels are done, like cpanel or ensim: You can buy various versions that place different limits on the number of domains it can handle, like 10, 50, 100, unlimited. They don't care whether they are your own domains, or someone elses domains. They just care you don't put your license for the control panel on more than one server, and they don't let you setup more than the allowed number of domains. That seems just like the plainest parts of the Atlassian license.

Essence of the terms of the Confluence License

The essence of the Atlassian license is one installation on a single physical server that serves a certain maximum number of "authorized users".

As long as I am not making multiple installations or finding a way to let an excess number of users have accounts within my licensed wiki installation, I am not violating the essence of the license.

I believe a reasonable reading of the Confluence wiki license supports the idea that how I choose to distribute the licensed number of user accounts on my wiki should be entirely my right within the license.

But your response to my letter seems to disagree with that interpretation.

So now I have to sit down and plan all the ways I might use the Confluence instance I was planning on purchasing. The issue of investing anywhere from $1200 to $8000 on users for a wiki that I can't really use to make money from is a very serious issue indeed. So I'm writing all this stuff to try and get a proper answer to the confusion, instead of writing plugins for the [CodeGeist] contest.

• Please go on to Sample Usage Scenario of A Small Web Hosting Company's First Confluence License

Related articles

• Confusion Over How Confluence Licensed Users Can Be Used Is An Example Of Why Open Source Licensing Was Developed
• Should a Confluence instance with limited user license count be exposed to the public internet for user account creation