License Management Architectures

Scenario 1.a: Single Machine with Hardware Key

Scenario 1.a: Single Machine with Hardware Key

In this setup, a single machine runs the customer's software and accesses the recognition engine. The hardware key, required for authentication and protection, is plugged directly into the machine. This model represents a straightforward deployment for individual systems, where the key and engine are housed within the same physical unit.

Scenario 1.b: Embedded Engine in a Camera

Scenario 1.b: Embedded Engine in a Camera

Recognition engines embedded in hardware products, such as cameras, also require licensing. In this scenario, the hardware key is built into the camera itself, enabling the camera to run the engine. A license file must be installed on the camera to enable offline usage.

Scenario 2: Cloud-Based License Management

Scenario 2: Cloud-Based License Management

In the cloud-based option, the customer network still comprises three hosts:

  1. A machine running customer software and the recognition engine.
  2. A camera running the engine.
  3. The License Service Client serves both the machine and the camera by connecting to the Carmen Cloud's public license service.

This modern approach leverages cloud technology to manage licenses, eliminating the need for physical hardware keys. The cloud-based infrastructure enables scalable, remote management and offers an accessible pathway to adopting newer licensing models.

Comparison

The following table provides a comparative analysis of the two distinct license management scenarios available for Adaptive Recognition's recognition engines. Understanding these differences will help you select the most suitable licensing model for your specific needs.

Feature / ScenarioSingle MachineCloud-Based License Management
Setup EaseModerate (Direct hardware setup)Easy (Quick setup; no hardware key)
Cost StructureUpfront cost (License)Gradual scaling with usage
Economy of ScaleSuitable for individual systemsFlexible, scales with needs
Centralized ManagementNot applicableAvailable
ScalabilityLimitedHigh
Technology IntegrationHardware dependentCloud-driven, modern approach
Offline Usage CapabilityAvailableRequires internet connection