Interactive runtime preview

Try the operator experience without exposing the private deployment.

This is a public-safe reconstruction of the real platform UI. Menus, workflow shapes, status concepts, and operator actions come from the current runtime. Identities, hosts, credentials, tenant data, and mutable backend actions are synthetic or disabled.

real menu modelsanitized stateinteractive controlsno production access
Real structure

Operator menus and actions

Operations, identity runtime, FreeIPA, Okta, sync, mapping, federation, and database controls reflect the platform's current UI vocabulary.

Safe data

Nothing private is required

Sample identities use reserved invalid domains and synthetic hostnames. No real credentials, tenant IDs, or infrastructure names are embedded.

Next stage

Live isolated demo

The same public tour can later hand off into an isolated resettable VM running FreeSCIM with seeded demo data.

Hands on

Move through the control plane and try the safe actions.

Start in Operations, then switch through Identity Runtime, FreeIPA, Okta, Sync, Mapping, Federation, and Database. The public simulation intentionally preserves the distinction between observe, preview, governed, and apply.

What is authentic

The interaction model comes from working runtime surfaces.

The preview is not a generic dashboard invented for marketing. It is a sanitized projection of current template and front-end behavior.

Operations

Runtime widgets and command queue

Derived from the operations command center, runtime widgets, diagnostics, failing-route, DB, and job controls.

Identity

Lookup and access explainability

Derived from identity runtime, canonical identity, trust indicators, HBAC drilldown, and dry-run reconciliation.

Sync + Mapping

Compare before write

Derived from snapshot capture, drift computation, plan preview, mapping validation, conversion preview, and gated apply controls.

Federation

Maturity and readiness

Derived from runtime, replay, trust graph, application catalog, launch readiness, drift, reliability, and provider maturity workflows.

Database

Preview, backup, verify

Derived from schema drift checks, migration preview, retention, backup, bounded maintenance, and guarded apply workflows.

Safety

Public interaction stops before real mutation

Buttons that would modify directory, tenant, or database state are disabled or simulated until the later isolated live-demo environment exists.

Toward a live VM

The preview is the front door. The isolated runtime can become the final room.

The intended progression is public simulation first, then a resettable demo VM with synthetic directory data, demo-only credentials, bounded network access, session expiration, and no route to private production systems.

Review runtime truthExplore operations