License Activation Diagram

The following diagram shows the entire license activation workflow from when a customer enters their activation code through the periodic validation process that happens after successful activation.

1. The customer enters their activation code in the client application.
2. The application generates a unique hardware ID based on the machine’s characteristics.
3. The application sends an activation request to the Babel Licensing Service with both the user key and hardware ID.
4. The service validates the license in the database, checking if it exists and confirming it hasn’t expired or been revoked.
5. The service verifies that the maximum number of activations hasn’t been reached.
6. Upon successful validation, the service creates an activation token in the database, associating it with the specific hardware ID.
7. The service returns a digitally signed license token to the application.
8. The application stores this token locally for future validation.
9. The application displays an activation success message to the customer.
10. Periodically (e.g., every 5 days), the application validates the license with the service to ensure it remains valid.

The key distinction of the activation model is that the license becomes permanently bound to a specific machine through its hardware identifier. Unlike floating licenses that are temporarily allocated, activation licenses remain tied to the machine until explicitly deactivated. This activation process creates a more persistent licensing relationship, suitable for software that will be consistently used on the same device.