Aspose Developer licenses are per user, not per named user. We understand that members of a coding team may change over time and that it is not practical to have to update licensing each time that occurs.
All developers who are working on the project need to be licensed. In this situation Aspose sees your team as having four members (even though they work at different times).
No, we are happy that customers use Aspose products on one server for solution building purposes at no extra cost. This installation should not be used to circumvent the license terms of your agreement with Aspose and should respect any redistributable or location limitations imposed by your purchased license.
No. Our products are licensed to the organization, not an individual within the organization. Our software are not personal tools that you can move freely from one workplace to another.
If you are working for a company to implement a solution that they will deploy, it is that company's responsibility to ensure that they have licenses for the tools that you need. If you are working as part of their development team, they should buy sufficient licenses to let other members of the team continue maintaining the code when you have left.
On the other hand, if you are self-employed and develop solutions that you sell to other companies, then you should have a Developer OEM License. This allows you to use the product in any number of derived works and deploy them freely.
When you buy an Aspose product you get two things: a license and a subscription. The license entitles you to use the software. The subscription entitles you to software updates for a year. The subscription expiry date is stored in the license so when you renew your subscription, you get a new license file.
The number of sites (locations) that the derived work can be used at. An OEM license allows you to use the derived work at any number of sites. This is appropriate when the derived work will be distributed to others outside the organisation, or offered as an online service to any number of people, all in different physical locations. Some licenses allow you to deploy to a specified number of sites:
Exactly what a license entitles you to depends on the platform: .NET and Java licenses give you slightly different rights from SharePoint and Android licenses, for example. Read about License Types to find out more.
Head to the pricing information page for further details.
Aspose will not agree to licensing more than one company under a single order. Aspose’s products are licensed by the number of developers and deployment locations, to single entities. However, Aspose does offer temporary licenses which can be used in these cases. Click here to learn how to obtain a temporary license.
No. Aspose products are licensed are per platform. If multiple platforms need to be supported, then Aspose offers a “Product Family” suite which licenses all platforms.
Often times we are asked what the term “physical site” or “physical location” applies to in terms of licensing. A physical location is any office or building with it's own postal address. So if you have several different buildings each with it's own postal address you would need to purchase a separate license for each location (which will be utilizing the product).
How do you classify off-site servers?
If your business has off-site hardware, such as: build machines, backup servers, disaster recovery servers, co-location servers or test servers then you will need to purchase an additional license for each off-site location. A location can include an unlimited number of servers, that still counts as just one location in terms of licensing.
All developers who are working on the project that uses Aspose products need to be licensed, even if they do not directly use the Aspose products.
Yes, a Site license can cover a distributed team as long as the size of the team does not exceed the maximum user count.
Yes, you can purchase a product family package for which includes every platform for that product. This is useful if your organisation uses several different technologies and is discounted for the number of products it contains.
In addition there is the Aspose.Total product suite which includes all products for a particular platform e.g .NET or Java. If you are using three or more Aspose products then cost-wise it becomes cheaper to buy Aspose.Total instead of each product individually.
Finally there is a Product Family for Aspose.Total which includes everything, all products for all supported platforms. This is massive value for a great price.
While Aspose products are extremely powerful we cannot guarantee that every feature is available. If you find a missing feature or a bug please report it on the support forums and it will be communicated to our development team to fix. For mission circuital issues consider purchasing paid support for increase priority.
That depends in in part on where you intend to use the derived works (the applications you use Aspose products to create). We recognize that a team can be distributed and allow that in our license structure. In this case, you have a team of five. Whether they are in the same physical location or not, you need enough licenses to cover five developers. They also need to cover the number of locations that the derived work will be used. Here are some scenarios:
That depends on how many physical offices are in New York and Paris. Here are a couple of scenarios:
Yes. If the developer permanently leaves the team and will no longer be working with Aspose products then their license can be transferred to a different developer. See the next question for details about that process.
Aspose licenses are not tied to a particular machine or account so the license file can be copied and installed to a new machine provided that any redistributable or location limitations imposed by your purchased license are still respected.
Refer to the Metered Licensing FAQ for further details.
The .NET and Java licenses are concerned with the number of developers and the number of locations to which any derived works (products created with the APIs) are used in. A location can be an office, for example, or any building with its own postal address.
The Android licenses work a little differently. They look to how many apps are created, as well as how many places they are deployed to. There are two options for the latter: Enterprise deployment (for use in one company only) or OEM (unlimited deployment to unlimited companies). An OEM license is used if you are selling the app on a marketplace. A Developer license lets you develop one app and a Site license lets you create up to ten.
The Exporter licenses (SharePoint, Reporting Services, JasperReports) work differently as well, once a SharePoint component is installed, for example, it's features are available to all users of that SharePoint site. So instead of looking at physical locations, the license limits the number of physical servers that the component can be used on.