Security
Access follows membership, not a hostname or a QR code.
This page describes the controls in this build and the production controls that still depend on identity, hosting, and policy configuration.
In this build
Company records are stored in a server-side registry for the development workspace. A person sees a company only after sign-in and an explicit membership or a matching invitation. Search in the public demonstration uses fictional sample data and does not read that registry.
Custom hostnames resolve only through the hostname registry. An unknown host is unbound. A pending host does not open the workspace. QR codes in the sample are identifiers and are rejected when they are web links.
Sessions use an HttpOnly cookie. There is no password database. Keyra is not connected.
Production dependencies
Production sign-in, device revocation, retention, and certification claims wait on the deployed identity service and the company’s actual agreement. This site does not display SOC 2, ISO, GDPR, HIPAA, or zero-trust badges.
Customer content is scoped to the company. Training worlds are not switched to public access when a person is removed. Removing a person is designed to keep historical authorship and revoke future access.