Licensing

Licensing facts:

• The applications you build can be distributed royalty-free.
• Licenses are per-developer.
• The license key is used for the full version of the product.
• No call-home license key validation.
• Volume discounts are available.
• Source code is available.

Product Licensing Model

Is your license on a per-developer basis? Does each developer using your products require a license?

Yes. Each developer that uses our products must have their own license. We don't license per machine, per server, or demand any royalties or run-time fees. For more information, refer to our End-User License Agreement.

How many licenses do I need?

Polar Components is licensed on a per-developer basis.
This means you have to obtain a valid license for each developer who accesses Polar Components for development purposes.
Examples of activities for which you need a license:

• Writing code which calls Polar Name Explorer API
• Calling Polar Name Explorer API via one or more proxy or wrapper layers
• Building or compiling project which depends on Polar Name Explorer assemblies
• Writing unit tests for code which depends on Polar Name Explorer assemblies

Do I need a license for testers?

No, if they are only using your completed and compiled application (basically in the same way as your end users).
Yes, if the testers are also acting as developers. For example, if they are compiling applications.

Do I need a license for our automated buildserver?

No. Only developers need a license. License is not needed for continuous integration tools, as long as all developers are properly licensed.

Can I use the component on multiple machines?

Licensed developers can use the component on any number of machines as long as they are the only persons who access the component.

Can I redistribute your components with my product?

In most cases that's OK (of course), but there is one exception. You cannot use Polar Name Explorer Component in a product which directly or indirectly competes with Polar Name Explorer Component. Rule of thumb: If your users are developers of any kind and you enable them to create code which calls Polar Name Explorer component via some kind of proxy layer, then the answer is: No, it's not allowed.

Can I redistribute Polar Name Explorer library with my own library?

No. Every developer who is using Polar Name Explorer library must have a license - even if he uses it via a third party library.

Can I repackage your component and distribute it as a competing library?

The answer is no. This applies to both commercial and free libraries.

Do we have to pay for each copy of our software we ship that includes your component?

No. The component is licensed per-developer, not per user. Once you have purchased a license for each of your developers, you can redistribute the component DLLs with your application royalty free and to any number of end users and to any number of computers.

I lost my license key. How can I obtain my license key?

Please contact our Licensing Team via email at sales@polarsoftware.com to obtain your license key.

Do you provide source code?

Yes, contact us at sales@polarsoftware.com.

What are Trial license limitations?

Trial license is valid for 30 days. It's called "evaluation period". When evaluation period is over you must stop using the trial license and uninstall the trial version. You cannot redistribute trial DLLs.

License keys for NuGet packages

When are license keys needed?

You need it when you reference commercial Polar Name Explorer Component assemblies from NuGet.org.

How do I get my full version license key?

When you make a purchase we will send the license key to your email.

How to use the license key? How to Upgrade from trial to full version of Polar Name Explorer component?

You need to register the component in source code with full version license key like this.

// Add this line to your application to set your key before working with Polar Name Explorer classes.
Licenser.RegisterLicense("put-your-full-version-license-key-here");

Is the key validated online?

No. There is no call-home license validation functionality. All license checks are performed offline.