Users Guide > General Information > Licensing > Licensing overview

Licensing overview

CSDK offers the following license types:

Page Pack license

  • Page Pack license can be used by multiple computers.

  • Page Pack licenses can be managed on a central license server, that distributes the license to any number of computers, where the CSDK runs

  • All features are available on all computers, that use the Page Pack license.

  • Page Pack license contains a number of available credit. There are Page Pack licenses that contains 50k - 40M credits, which makes possible to process much more pages than 25000 per month. To process a page costs 1 credit.

  • Page Pack license has an expiration date. The license becomes invalid on the expiration day.

Seat license

  • Seat Licenses can be used by only one computer at the same time.

  • Maximum 25000 pages per month can be processed.

  • It contains the Western OCR feature, and it can be extended with add-ons, for example Asian OCR, or Barcode features.

OEM License

  • OEM Licenses can be used by multiple computers at the same time. The access is protected by a private key.

  • Maximum 25000 pages per month can be processed by each computer.

  • It contains the Western OCR feature, and it can be extended with add-ons, for example Asian OCR, or Barcode features.

Beside these licenses, Test license are used for evaluation purposes. CSDK can be installed to ten different computers with Test license.

CSDK manages the licenses through OPLA and OPLicMgr tools, and the Activation Server. OPLA and OPLicMgr tools have both command line interface, and UI.

OPLA manages Page Pack licenses. It has to be run as a Windows service, connected to at least one licensing server. OPLA creates report files, that contain the number of used credits per day. Report files can be used to recover license after a system crash. Ensure that your files are archived regularly.

OPLicMgr manages Seat licenses. OPLicMgr does not need to be run as a Windows service, as it counts the pages throug KernelAPI.

OEM licenses are managed by KernelAPI itself. They must be activated through OPLicMgr, but OPLicMgr is not needed for their use.

If there are multiple available licenses, first the credits of the one with the closest expiration date is used. If the expiration date is the same for multiple licenses, credits are used in a way, that the Credit/Used Credit ratio remains approximately the same among the licenses.