AquaStudio uses a hardware-aware licensing architecture designed to combine software protection with local controller operation.
The licensing system is designed around the controller environment rather than relying exclusively on a permanent cloud connection.
This approach allows licensed AquaStudio installations to continue operating locally even when no permanent internet connection is available.
AquaStudio is designed so that licensing remains closely connected to the local controller environment.
License information can be validated locally instead of requiring a permanent connection to a cloud service.
This reduces unnecessary dependencies on external services during normal controller operation.
The licensing architecture uses controller-specific hardware information as part of the local license environment.
The controller therefore becomes part of the licensed installation rather than being treated as an unrelated external device.
Core license validation is designed to operate without continuous internet access.
Internet connectivity may be required for specific services or future functions, but normal licensed controller operation is designed around local validation.
Licensed installations use a cryptographic license token as part of the local license environment.
Internal secrets and verification material are never exposed through the public website or normal user interface.
The licensing environment connects the software license with the controller on which the licensed system operates.
A valid AquaStudio license is issued for the selected product or package.
AquaStudio identifies the relevant controller hardware and its local hardware environment.
The licensed environment uses the corresponding cryptographic license information for local verification.
Once the license environment is successfully validated, AquaStudio can operate the licensed functionality locally.
AquaStudio is designed around the principle that software protection should not require the controller to be permanently connected to an external licensing server.
The local controller environment therefore forms an important part of the licensing architecture.
This allows the system to combine licensing protection with the practical requirements of aquarium installations where reliable local operation is more important than permanent internet connectivity.
AquaStudio documents the general licensing architecture and the user-facing behavior of the system.
The general licensing architecture and user-facing behavior can be documented publicly.
This allows users to understand how the licensing environment is designed without exposing sensitive implementation details.
Internal cryptographic keys, salts, verification secrets and implementation details are intentionally not published.
Publishing these values would weaken the very protection the licensing system is designed to provide.
AquaStudio does not publish internal cryptographic keys, salts or verification algorithms. This page describes the architecture and user-facing behavior, not the internal security implementation.
AquaStudio is designed for real aquarium installations. A controller should continue doing its job even when the internet connection temporarily disappears.
The licensing architecture therefore follows the same principle as the controller software: local control first, external services where they are actually useful.
The result is a licensing model designed around the hardware that actually runs AquaStudio.
AquaStudio's licensing architecture is designed to protect the software while keeping the controller operational and independent from a permanent cloud connection.