Trust & residency

Follow identity data through sign-in.

The local build shows how sign-in, workspace access, and audit events fit together. The same data path must be verified independently for each planned hosting region.

Local sign-in

From browser to workspace

  1. BrowserRedirects to Keycloak
  2. CallbackExchanges the code
  3. ConsoleCreates a session
  4. WorkspaceChecks membership
Regional launch review Planned

Where data may leave the app

  • Edge and DNSTrace inbound requests
  • Backups and logsVerify storage locations
  • Recovery and supportCheck processor access

The local sign-in path

  1. Browser to identity issuer

    The browser goes to local Keycloak for authentication. The app receives an authorization code at its registered callback URL.

  2. Callback to session

    The console validates the signed ID token, issuer, audience, state, and nonce. The browser receives an opaque session cookie while the console stores session state on the server.

  3. Session to workspace

    The console uses the authenticated session and current membership to decide which workspaces the user can access. Changes to access are recorded in the workspace audit log.

The planned production boundary

Each deployment will have a regional issuer, application database, backup path, and audit storage. The exact operators and approved destinations are part of the launch review.

  • Inbound traffic

    Identify every service that can see a request or terminate its encrypted connection before it reaches the regional issuer.

  • Operations and recovery

    Trace where logs, monitoring events, recovery emails, and backup data are processed. Verify support access and rehearse recovery within the selected region.