Hi there,

We made pretty serious changes in the licensing policy for Image Uploader 6. It is not similar to the old one and someone may be confused with it. However I strongly believe that it is much more straightforward. That’s why I decided to write this post to explain our point of view on the licensing questions.

Single Domain vs. Express/Standard/Professional

From the very first version of Image Uploader, the primary license type was a Single Domain license. It was issued for a website with one full-qualified domain name, and it was limited by a single server. For more servers, a separate license type called Web Farm license was provided (the reason why multiple servers require additional licenses is outlined below). Things were getting complicated when such websites required multiple domains, etc.

Taking into account our past experience with customers’ licensing demands, we have reviewed our licensing system. Now each website requires only one license. This license allows using it with a single server and one domain (other limitations are omitted for brevity, so refer licensing pages for more details on this). If this is not enough, you should extend the license with so-called connectors. There are two kinds of connectors – server connectors and domain connectors.

This license plan is called Standard. It has a sibling – a license plan called Professional. The only difference is that the Professional version includes some additional features primarily interesting to the photo printing companies.

These license plans are more consistent comparing to the Domain and Web Farm licenses. However they may seem pretty expensive for a number of customers. But we wanted to keep Image Uploader affordable for startups and small websites as well. That’s why we offer an Express license plan in addition to Standard/Professional. It is very similar to the old good Domain License, but however it includes fewer technical support features.

I would like to comment this point with support. For a long time, our policy was to provide the same level of technical support to everyone. But in the course of time we got a number of customers who have special requirements for the support - guarantied response time. That’s why we made a difficult decision – we provide unlimited high-quality technical support with guarantied reply in 24 hours to Standard/Professional customers only.

But it does not mean that Express customers do not get any support at all. They still can submit up to 2 cases, and of course they can post messages on forums. According to our statistics, it should satisfy a big number of our customers.

About Server Connectors

Some people wonder why the price for the client-side software like Image Uploader depends on the number of servers, their CPUs, etc. Let me explain.

Ideal fair measure for a software price should be the intensity of its usage. When we talk about common standalone desktop applications, it is easy to estimate – the number of workstations where the software is installed is a good appraisal. That’s why this licensing model is so popular for such kind of applications.

However when we consider such application as Image Uploader, it is not so easy. On one website Image Uploader may be downloaded by 1000 people, on another one – by 1000000 people. And the worst thing is that a website owner is not always able even to calculate this number. The same situation we see if we try to use some similar metric, like amount of uploaded data or something like this.

That’s why we decided to use another metric – the power of the server side which processes the upload (i.e. the number of servers, etc). This value is clear and easily managed by the website owner. And it seems to be fair enough, because it is unlikely that someone will purchase and configure large web farms and let it be idle. So to make the licensing policy scalable, we just deem each additionalserver, CPU, or CPU core as a separate unit which requires purchasing a connector to the main license.

The arguable question here is whether to interpret multi-core CPUs in the same way as multiple single-core CPUs. On the contemporary market all new server CPUs are almost always multi-core, so it may seem not very good idea. But on the other side, it is obviously that 32-core SPARC is not the same as typical multi-core Intel or something like this. So the decision worthy of Solomon would be to set a threshold value for the number of cores which divides typical multi-core CPUs from something special like SPARC. In our case we consider CPUs with up to 8 cores as a single unit.

And the last aspect I would like to discuss regarding server connector is what to do if you use a virtual hosting rather than run it on real servers. This is especially actual because of growing popularity of such services as Amazon EC2, and similar.

Of course we do not have anyone to purchase licenses for all underlying hardware of Amazon EC2. Virtual hosting providers allocate resources in so-called Computing Units. Each such Computing Unit has the power comparable with common server with typical configuration. That’s why we just interpret such Computing Units as servers requiring connectors, not the real underlying hardware.

Single-owner Website vs. SaaS/Commercial Apps

In the previous section I explained how we make the price scalable based on the product usage intensity. But this is not the only parameter which should be considered. One more crucial parameter is whether the website is used by a single owner or itis an application used by multiple third party companies.

Imagine you build Image Uploader into a CMS engine. You host this engine on your server and let your customers an account, and create websites based on it.  From our point of view such usage of Image Uploader may be interpreted as reselling to third parties.

In such situation Express/Standard/Professional license plans do not work here. This is where we use classic license model for software component market. The idea is the following: instead of purchasing a website license with connectors, you purchase SDK licenses per each developer on the application development stage, and when you run it to the production, you purchase deployment licenses per each client.

Depending on your situation and what is preferable for you, you either purchase blocks of deployment licenses which cover all your present and future customers, or acquire a license for each separate customer.  But the general rule is simple – the price depends on the number of your customers, not on the intensity of the software usage.

We divide single-tenant and multi-tenant applications pretty long (at least from version5.0 or even earlier), but earlier it was less obvious, and it lead to misuse of some kind of old licenses. Hopefully now we managed to make it clearer.

Where is an IP license?

One of the main questions our previous customers may have is what an analogue for the IP license is.  This is quite ambiguous question.The answer depends on the nature of the website you run.

1. If you have single-owner website and need the IP license to cover all its domains (e.g. www.example.com, www.example.net, www.example-alias.com, subdomain.example.com etc.), you should switch to Standard or Professional license + appropriate number of domain connectors. If the number of domain connectors is not reasonable, we can provide special connectors for IP address or whole domain tree on aspecial request.

2. If you have a hosted application,you should switch to SDK/deployment model. If the number of clients of your application is more or less constant and do not grow extensively, most likelydeployment fee will be a block of licenses which will cover all your customers for the nearest year or other period of time.

Holders of the old IP license may have a concern about the price of deployment license block or IP connector. However I would like to ensure you that there will be no price skyrocketing. At least its order is the same as for old-fashion IP licensing.  

I hope I shed some light on new license policy and made it clearer. If you have any feedback or would like me to write one more post about some aspect of licensing questions, do not hesitate to leave a comment here.

We have noticeable reworked a portion of website related to Image Uploader pricing and licensing. Since Image Uploader licensing plans became more complicated, we have created a separate section which contains well-structured FAQ describing all possible options:

http://www.aurigma.com/Products/ImageUploader/Licensing.aspx

Also since a number of Image Uploader related online store items are getting exceed all reasonable limits, we have grouped them on the purchase page: 

http://www.aurigma.com/Products/ImageUploader/PricingLicensing.aspx

As always, I highly appreciate any feedback. If something is unclear here or you have any additional questions, do not hesitate to inform me. I will try to explain it better.  

As Alex wrote before, we have released new version of Image Uploader. In addition to a number of new features, we also made several modifications in our licensing model. In fact we wanted to do it much earlier, but we decided to do it together with the major release to reduce problems for existing customers who already purchased Image Uploader under old licensing terms.

Let's see what is new.

1. Different licensing for standalone servers and web farms

Now it matters whether you run Image Uploader on one server or on load-balanced multi-server web farm. In short:

1. Standard Domain and IP licenses are applicable for single server. Moreover, it should have 1 or 2 CPUs.
2. For multi-server environment an alternative licensing model is used: you should have one Web Farm license + Server Connector licenses per each server in the web farm.
   
   Example: Your website is running on web farm consisting of 4 servers. You need one Web Farm license + 4 Server Connectors.   
   
   
3. If you have no web farm, but have a single server with more than 2 CPUs, you should have a standard Domain or IP license (according to your needs) + as many Server Connectors as additional CPUs you have.
   
   Example: Your website is running on a server with 8 CPUs which uploads files to a single page (one domain). You need one Domain License + 6 Server Connectors.  

 2. Upload processing page (Action param) and the page which hosts Image Uploader should belong to the same website

Now you should not upload files from one website to another using Image Uploader. In other words, if the control is hosted on www.mydomain.com and uploads files to www.megapopularphotosharing.com, it will not work.

But it is still ok to upload to the page which is within the same domain (even if their full-qualified domain names are different). For example, it is correct to host the control on www.mydomain.com and upload to upload.mydomain.com (provided of course that you have a license for upload.mydomain.com). 

3. Standard licenses do not apply to SaaS solutions

If you create a SaaS solution, it is virtually the same as if you sublicense Image Uploader to your customers. That's why it requires another licensing model, which is discussed individually in each case.

You may wonder where is the boundary of SaaS apps and common websites. The criteria is the following - SaaS is a multi-tenant application. In other words if the account your customers create can be interpreted as a standalone application (as if it is installed on their own servers) - this is SaaS. Examples examples to name a few are hosted CRM solutions (like salesforce.com) where customers manage their own company's records, or hosted CMS systems where they build their own websites.

4. For private-label version owners - in some cases re-preparation of the pvt build is paid

Unfortunately pvt build preparation takes certain time. It is ok for us to do it once or twice, but when it happens too often, it slows down Image Uploader development process. That's why we decided to limit a number of free preparations of private-label builds. I hope for your understanding.

Of course, there will be some situations when pvt updates will be free. In particular they are:

1. First time.
2. Once per a minor update (i.e. when we replace, say, 5.0 to 5.1).
3. Critical bugfixes.
4. When it happens naturally (e.g. we send you a modified version for some reason).

Also most probably the price will vary depending on whether it is necessary just to recompile or also create a .CAB file signed with your digital cert. Of course we will provide you instructions how to do it yourself, so that you will also have a choice.

That's all. If you have any questions, feel free to drop email to sales@aurigma.com. Also, if you find that your old version does not fall under new licensing terms, and you wonder how to upgrade, feel free to let me know.