Security

The public proof of concept is not the production architecture.

The demo uses fictional data and browser-local storage. A customer deployment requires a separate production environment, controlled authentication, database policies and integration review.

Demo isolation

The public demo is only for evaluating the workflow. It should not be used for confidential operational, employee, production or maintenance information.

Production authentication

Production workspaces are intended to use authenticated accounts, role-based access and organization-specific permissions. Interface visibility alone is not treated as a security boundary.

Database and organization separation

Each production design defines how organizations, sites, users, tickets, assets, parts and integrations are separated before live data is introduced.

Industrial integrations

Historian, PLC, camera, radio or other facility integrations require explicit technical scoping and minimum necessary permissions. Public-facing software should not create a control path into operational technology.

Deployment choices

Standard cloud deployment can serve normal use cases. Larger organizations may require SSO, dedicated environments, private networking or self-hosted components as Enterprise scope.