EKP Dialog, EKP Web, and EKP Lite: how to assemble a work contour
A common buying mistake is to tender "messenger", "browser", and "mobile app" as three unrelated lots. Value appears when they are one scheme: a server, two clients, one IAM.
Use this order to keep the pilot from splitting into three islands.
Roles without confusion
- Private Web holds people, sign-in providers, spaces, and services. SSO starts here.
- EKP Dialog runs the chat stand. Matrix accounts show up in the person directory.
- EKP Web is the protected browser. After sign-in the right pane talks to the Dialog stand; the left pane shows services from spaces.
- EKP Lite is the phone. The Dialog tab points at the same stand; Home points at the same services.
The Unified Corporate Platform page describes a wide contour (messenger, browser, AI). The Dialog / Web / Lite line makes server and clients explicit, which is easier for architects and procurement.
Rollout order
- People catalog and SSO in Private Web.
- EKP Dialog stand in the perimeter, bound to Matrix accounts.
- EKP Web pilot in one unit: services on the left, chats on the right.
- EKP Lite pilot on the same group: confirm the rooms match.
- Metrics: share of chat on the stand, time to revoke access, number of shadow channels in scope.
Avoid raising clients before the server, unexplained separate stands for web and mobile, services missing from spaces, and a "just in case" extra messenger account that breaks SSO.
Client-to-stand connection is in the EKP Dialog docs; browser and app UI live under EKP Web and EKP Lite.