Guides

List icon Contents
Close
Introduction

Licensing

This guide focuses on technical aspects of different license types.

For pricing information and details on terms and conditions, see the Licensing and Pricing section.

DotNetBrowser needs a license key which represents a string with combination of letters and digits. Follow the instructions outlined in this article.

Commercial licenses

When you purchase a commercial license, we email you with a license key.

You can use this license key both for development purposes and distribution of our library as part of your application.

Indie license

This license is issued to a person.

It includes a 1 year of Standard Support subscription which includes product updates and technical support.

The technical support is provided via allocated account at DotNetBrowser Help Center. We will create one account for the license holder.

Only the license holder has rights to use DotNetBrowser, receive free updates including minor and major versions, and contact technical support during active Standard Support subscription.

DotNetBrowser Individual License Agreement

Project license

This type of license is issued to a company.

The license is tied to a namespace of your project. When you purchase a Project license, we ask to provide the namespace where you plan to create an IEngine instance. You can work with the created IEngine instance and make calls to the library’s API in other namespaces without any restrictions. The namespace name is expected to be in the Product.Module format. See examples below.

Let’s assume that the license is tied to ProductNamespace.MyNamespace. The license key can then be used in the following way:

namespace ProductNamespace
{
    namespace MyNamespace
    {
        public class MyClass
        {
            public void InitializeEngine()
            {
                IEngine engine = EngineFactory.Create(new EngineOptions.Builder
                {
                    LicenseKey = "your_project_license_key"
                }.Build());
            }
        }
    }
}

Namespace ProductNamespace
    Namespace MyNamespace
        Public Class [MyClass]
            Public Sub InitializeEngine()
                Dim engine As IEngine = EngineFactory.Create(New EngineOptions.Builder With 
                {
                    .LicenseKey = "your_project_license_key"
                }.Build())
            End Sub
        End Class
    End Namespace
End Namespace

You can also use this key in the classes located in the inner namespaces, for example:

namespace ProductNamespace
{
    namespace MyNamespace  
    {
        namespace InnerNamespace  
        {
            public class MyOtherClass
            {
                public void InitializeEngine()
                {
                    IEngine engine = EngineFactory.Create(new EngineOptions.Builder
                    {
                        LicenseKey = "your_project_license_key"
                    }.Build());
                }
            }
        }
    }
}

Namespace ProductNamespace
    Namespace MyNamespace
        Namespace InnerNamespace
            Public Class MyOtherClass
                Public Sub InitializeEngine()
                    Dim engine As IEngine = 
                        EngineFactory.Create(New EngineOptions.Builder With
                        {
                            .LicenseKey = "your_project_license_key"
                        }.Build())
                End Sub
            End Class
        End Namespace
    End Namespace
End Namespace

If you create the IEngine instance in another namespace, the license exception will be thrown. For example, if the license is tied to ProductNamespace.MyNamespace, the following code will throw an InvalidLicenseException:

namespace ProductNamespace
{
    namespace AnotherNamespace
    {
        public class MyClassInAnotherNamespace
        {
            public void InitializeEngine()
            {
                IEngine engine = EngineFactory.Create(new EngineOptions.Builder
                {
                    LicenseKey = "your_project_license_key"
                }.Build()); // <- InvalidLicenseException
            }
        }
    }
}

Namespace ProductNamespace
    Namespace AnotherNamespace
        Public Class MyClassInAnotherNamespace
            Public Sub InitializeEngine()
                Dim engine As IEngine = EngineFactory.Create(New EngineOptions.Builder With
                {
                    .LicenseKey = "your_project_license_key"
                }.Build()) ' <- InvalidLicenseException
            End Sub
        End Class
    End Namespace
End Namespace

It includes a 1 year of Standard Support subscription which includes product updates and technical support.

The technical support is provided via allocated account at DotNetBrowser Help Center. We will create 2 accounts for the license holder.

DotNetBrowser Project License Agreement

Enterprise license

The license is issued to a company.

The library can be used by an unlimited number of developers for any number of projects in your company.

It includes a 1 year of Standard Support subscription which includes product updates and technical support.

The technical support is provided via allocated account at DotNetBrowser Help Center. We will create 4 accounts for the license holder.

Trial period

You can try DotNetBrowser for free for 30 days.

To start your free trial, please fill in this form. You will receive an email with your personal trial license key and a quick start guide.

Expiration

When your trial period is over, DotNetBrowser will stop working and throw “Your trial period has expired.” exception message. If you request another 30-day trial key, it will not work in the environments where you already used the expired one.

Please consider buying a commercial license to continue using DotNetBrowser in this case.

Extended trial period

There might be cases when your company’s procurement procedures take longer than 30 days. If you need more time to finalize the purchase formalities, please contact our Sales team at sales@teamdev.com with brief details of your situation.

Chromium open-source components’ licenses

DotNetBrowser is based on Chromium open-source project that includes the source code and libraries written by developers in Chromium community. The project also includes a number of open-source third-party libraries.

DotNetBrowser is using Blink, FFmpeg, libsecret, and Wayland Protocols KDE components, supplied under LGPL. Learn more about DotNetBrowser Compliance with LGPL.

One of the key questions with an open-source code used in commercial products is the permitted use of the open-source code and possible restrictions on use and distribution of the works based on this open-source code.

We perform a regular review of the licenses associated with the Chromium components used by DotNetBrowser to make sure there are no terms restricting commercial distribution of DotNetBrowser or customer applications using it. We also make sure that licenses requiring disclosure of the source code (like GPL) do not apply to DotNetBrowser or applications based on it.

Below you can find the links to Chromium components licenses associated with DotNetBrowser releases:


If you have any questions, email us at sales@teamdev.com.

Go Top