The real console, with sample infrastructure
Not a video and not a screenshot tour — the same console a customer gets, loaded with fourteen targets, nine people, sixty past sessions and six real recordings. Nothing to install and no account. Halfway through, the tour offers to email you the install steps; skipping that changes nothing.
What to try
-
Tighten a session that is already running
An engineer is at a shell right now. Drop them to read-only from the admin console and watch the next write get refused — on the same connection, with no reconnect.
-
Watch over someone's shoulder
Open session shadowing on a live terminal and see what is being typed as it happens, including what the broker refused.
-
Replay a session that finished
Real asciinema recordings of real sessions, scrubable, with the blocked commands in them.
-
Take access away and watch it end
Revoke a grant and the sessions it justified close themselves. The audit log says who did it and when.
-
Look at it from the other side
Sign in as the engineer instead: the same product, showing only what that person is allowed to reach, and how they ask for more.
What it is, exactly
The pages, tables, filters, the terminal and the session player are the product's own code. What is replaced is the infrastructure behind them: the demo answers from a fixture captured from a working controller rather than from a database, and the sessions you govern are driven by a script rather than by a colleague.
So it is honest about the product and not about your infrastructure. Nothing here connects to a real host, and nothing you do in it reaches anything of ours. When you want the version that does, it is one command and ten minutes.