Security and current limits

Public browser connections use HTTPS. Account sign-in uses the existing IONOVA identity service. The customer device-list and revoke routes filter records by the authenticated account.

Public and internal separation

The public customer interface must not include internal owner project registers. Customer projects start empty. Interface visibility is not an authorization control: the server must check permissions for every operation.

Beta limitations

The currently linked Windows package is unsigned and only registers the device. Customer workspace execution and a customer-authenticated MCP connection are not yet launched. A complete two-account isolation and revocation test remains a release requirement.

Report a problem

Email ss@lyngmose.com. Do not include credentials or other customers’ data.