Demo profile
Audience: presenter · Profile:
demo· Read this when: you are showing the dashboard to someone and want the story rather than the feature list.
The default profile, and what every existing install already is. An estate instance manages your infrastructure: your cloud accounts, your hypervisors, your images. You show it to people.
That is the difference from the POV profile, where each environment belongs to a customer and points at the customer's own BeyondTrust tenant. See the gate for why the two cannot be the same instance.
If you are not demonstrating anything
You are still on this profile, and the pages below are not the ones you want.
demo names a tenancy shape — one BeyondTrust tenant of your own — rather than a purpose,
and administering infrastructure you actually depend on has that same shape. Nothing about
the profile is pretend: the VMs are real, the accounts are really onboarded, and the
rotations really run.
What differs is which documentation is yours. The capability docs at the docs root are the whole of it — deploying a VM, onboarding it, rotating its credential and reaping it are the same pages whether the estate is a lab or production. This folder holds only the material that exists because somebody is presenting: the per-role narratives and the purpose-built demo environments. Skip it.
Pages
| Page | What's in it |
|---|---|
| Personas | One page per role — what that person owns, the four-layer story in their language, and the use cases to run for them. Estate instances only: a POV instance has no focus axis. |
| OT Demo Cell | A simulated OT/ICS plant cell — PLC simulators and a web SCADA/HMI in an egress-less subnet, reached only through a Gateway. The air gap is the demo. |
| OT protocol clients on Windows | Setting up a rep machine to read that cell: the four Python clients, a runnable snippet per protocol, and why DNP3 answers nothing. |
| Network Demo Cell | Preview. A VyOS router/firewall with no inbound rule, reached only through a recorded Shell Jump — the emergency rule change, made on a credential nobody sees. |
| Agent Demo Cell | Preview. A non-human principal that reads the estate through the MCP server, attested by SPIRE — and stops when you revoke its token while the room watches. |
Everything else is a capability doc
Almost every feature an estate instance has is documented once at the
docs root rather than here, because the page describing how to deploy an
EC2 instance is the same page whether you are demoing or running a lab. Each of those pages
carries **Profile:** demo in its header block — the config value, not a statement about
what you are doing with the instance.
What lives here is the material that only makes sense as a demo: the per-role narratives, and the purpose-built demo environments.