mobileFX WebKitX ActiveX
Advanced Topics / Commercial Distribution
In This Topic
    Commercial Distribution
    In This Topic

    A single Commercial License allows Independent Software Vendors (ISV) to develop an unlimited number of Windows Desktop Applications linked with mobileFX ActiveX controls and distribute them freely to an unlimited number of their customers. ISVs are required to obtain one license per Developer Workstation. The license is perpetual and we offer 20% discount for upgrades to customers that upgrade to immediate next release within the release's fiscal year. Commercial License explicitly excludes non-desktop application development such as Terminal, Virtual and Embedded applications.

    If you own a Commercial License of WebKitX ActiveX control, you need to add in your program your license. By doing so, the component will supress licensing messages at run-time (when compiled). Please add the following lines in your code:


    Finding your Developer UUID

    In some programming languages such as PowerBuilder, Delphi, Embarcadero RAD Studio, when placing the control on the Form does not display the Developer UUID. To find your Workstation's Developer UUID for WebKitX, locate the DeveloperUUID.exe program in WebKitX installation folder and run it.



    Developer Workstation Activation

    Our licensing policy requires each Developer Workstation to be licensed.

    To satisfy this agreement we ask you to bind your Commercial License with at least one Developer Workstation and the process is transparent and on-line. WebKitX control generates a hash of your Developer Workstation that consists of your computer name and hashes of hardware devices such as your hard disk, motherboard, etc. This hash is the Developer UUID and each Developer Workstation has a unique hash. When WebKitX detects a DESIGN-TIME ENVIRONMENT it first checks your Registry for the Workstation Key. If the key is not present in your registry then WebKitX will try to register your Workstation with our license server and download the key in your Registry.


    Validation of the Developer Workstation takes place ONLY when you are at design-time, that is when you use WebKitX from your IDE like Visual Studio, Visual Basic, Delphi, etc. Validation of the Developer Workstation NEVER takes place at runtime, so in other words it never takes place when your software runs in your client's computers.

    Our Developer UUID hash is future proof, meaning that if you need to upgrade faulty components of your Developer Workstation such as the Hard Disk, then as long as 4 out of 6 Developer UUID hashes remain the same, you are entilted to quest a new Workstation Activation code. Even if you need to fully replace  your Developer Workstation with a new one, you can contact us to disable your old binding so that a new binding between your Commercial License and your new Developer Workstation can take place.

    WebKitX contacts our License Server over HTTP on port 8076. You need to add this exclusion in your Firewall or Antivirus program for the activation to be successful.


    Terminal Activation

    Complementary to perpetual Commercial License is subscription-based Terminal Licensing. Terminal Licensing applies to Independent Software Vendors (ISV), Managed Software Providers (MSP), IT Solution Providers (ITSP), Systems Integrators (SI) and it is required if-and-only-if an application linked with mobileFX ActiveX products is deployed on Windows Embedded operating systems, or deployed through Terminal Services, or Virtual Appliances. Terminal services include any remote session WinStation such as Remote Desktop, Citrix Clients and Terminal Server Clients, and any Virtualization container such as VMware, Virtual Box, Parallels, etc.

    The term Terminal applies to distinct terminal client hardware devices and not distinct terminal end-users, nor your Terminal Server, and each Terminal requires 1 valid Terminal License to run WebKitX over remote, embedded or virtual sessions.

    Some sample cases:

    Some ISV cases:

    Some IHV cases:

    The common factor in all examples above is that you need at least 1x Commercial License for your business and 1x Terminal License per Terminal Client device. WebKitX hashes certain terminal hardware identifiers of the client computer (not software identifiers, nor user properties) and generates a Terminal Hash. The way Terminal Licensing works is that you must have 1x Terminal License per 1x Terminal Hash. Please note that you do not need an equal amount of Commercial Licenses and Terminal Licenses; a single Commercial License can be bound to any number of terminals for any software for any of your clients. In fact, your software products, versions and your clients are completely concealed from us.

    Depending on your product and company profile you can choose between on-line or off-line Terminal License Validation. For example, Banks and Telco Operators that deploy proprietary software to retail terminals often choose off-line validation because their software runs on isolated networks. Likewise Hardware Manufacturers producing hardware products that include WebKitX. However, ISVs that produce consumer software products often choose on-line validation.

    For Off-Line Terminal Licensing (aka. Enterprise Licensing) we generate a single Wildcard Terminal License Key that you must enter in your source code before compilation of your product. The Terminal License Key is validated at COMPILE-TIME, meaning that you need a valid key only during the compilation of your product. At run-time we do not validate the expiration of the key, which means that you can even distribute your software products to your clients beyond the expiration date of your Terminal key and rest assured that your products will continue to run past the expiration date of the Terminal License Key. Enterprise Licensing is non-auditable and enables any number of Terminals. However, if the Terminal License Key expires you won't be able to compile new products or newer versions of existing products.

    For On-Line Terminal Licensing we offer a pay-as-you-go subscription where you pre-pay for an arbitrary amount of Terminal Licenses that you decided based on your business development forecasts; in fact it can be as low as 1 Terminal Licenses. The licenses are stored on our license server in a RESERVED state. When any of your clients attempt to run your software from any terminal configuration (Embedded OS, VM, Citrix, Remote Desktop, etc.), then WebKitX discretely connects to our license servers and binds the Terminal Hash with an available Terminal License. However, there is technical catch: WebKitX contacts our License Server over HTTP on port 8076 and your clients need to add this exclusion in their Firewall or Antivirus program for the activation to be successful, or your software must care for this.

    Some bullet points about off-line Terminal Licensing:

    The expiration date is not part of the Terminal License and this is by design in order to give you ample time to renegotiate your commercials at the beginning of each fiscal year. We will not “pull the plug” if a license expires; we will contact you and give you time to decide how many licenses you will need for the new fiscal year. Say you start on 2020 with 100 licenses and you find out you only need 50 in 2021, you can ask for 50 on Jan 2021. Likewise, you start with 50 on 2020 and you realize you need 100 on 2021, you normally get them at same price. If we lower our prices, you take advantage of this. If we increase our prices, you are covered and retain the original price as long as you renew every year.

    We do not offer an automatic increase mechanism for Terminal Licenses but you can add more licenses to your pool at any time by ordering them at We can arrange that you never run-out of licenses and that your license pool is automatically replenished if depleted as part of an explicit contractual closure. However, you are granted ample grace period of at least 3 months to re-license as we do value your business continuity. We understand that sometimes there is paperwork and internal processes that need their time to conclude.


    Hardware Licensing

    Complementary to Perpetual Commercial License for Desktop Application Development is subscription-based Device Licensing. Device Licensing applies to Independent Hardware Vendors (IHV) and it is required if-and-only-if a software linked with mobileFX ActiveX products is distributed as part of, or embedded in, a Hardware Product, such as but not limited to IoT Devices and Gateways, POS Devices, Self Service Terminals, Vending Machines, Digital Signage Kiosks, Automation Devices, ATM Devices, etc. Device Licensing is volume-based and as low as £ 5 GBP for volumes over 10,000 items. Optionally can be offered along with SLA support and Escrow-based source-code branching at additional cost.

    Hardware Licensing is in essence the same as Enterprise Licensing for Terminals as described above and validation is off-line.


    Commercial Distribution

    Creating a setup script to install WebKitX on a different computer should be straight-forward:

    1. For x86 your script must copy the files of the C:\Program Files (x86)\WebKitX CEF3 ActiveX\bin folder to the other computer.
      The destination folder is irrelevant and can be anywhere you choose.

    2. For x64 your script must copy the files of the C:\Program Files\WebKitX CEF3 ActiveX\bin folder to the other computer.
      The destination folder is irrelevant and can be anywhere you choose.

    3. For x86 your script must run Microsoft Visual C++ 2015 Redistributable Package (x86) for the Windows OS and Service Pack bundle of the other computer.
      For detailed information please see the WebKitX Runtime Dependencies paragraph above.

    4. For x64 your script must run Microsoft Visual C++ 2015 Redistributable Package (x64) for the Windows OS and Service Pack bundle of the other computer.
      For detailed information please see the WebKitX Runtime Dependencies paragraph above.

    5. Your script must register WebKitX ActiveX into the Windows Registry using this command: regsvr32 /s WebKitXCEF3.ocx

    6. If your product does not use Chrome DevTools, you may skip devtools_resources.pak to decrease size.

    7. If your product uses Flash Player you should add Pepper Flash Player. 


    WebKitX Runtime Dependencies

    WebKitX requires Microsoft C++ Runtime. During installation WebKitX setup will automatically install Microsoft C++ Redistributable Package for the following list of Windows Operating Systems:

    The latest supported Visual C++ downloads by Microsoft

    .NET Redistributables (for C# samples)

    Visual Basic 6.0 Redistributables (for VB Samples);en-us;290887