Knowledge base / regulation10.com product guide

The demo dashboard: a worked governance view of a fictional estate

The demo dashboard at /demo is a complete governance view of a fictional organisation, open to anyone, with no account and no live data. It exists so a buyer can see the working product before handing over an email address. It is a dashboard you read, not a form you fill in.

The split between what is real and what is invented is the whole point of the page, and it is stated on the page itself in a banner that does not scroll away. What is real: the risk classes and the triggers behind them, the obligation set that follows, the citations, the readiness score and the filing route. All of that is computed on the request by the same deterministic engines a paying workspace runs. What is invented: the organisation, its five AI systems, which artefacts it already holds and the monitoring signals shown against them.

Nothing on the page is a customer, a case study, or a measurement of this platform's performance. The fictional deployer is labelled as fictional everywhere it appears. If you screenshot a panel, the sample-data label travels with it, which is deliberate: a governance view is exactly the kind of image that gets pasted into a board pack with its provenance lost.

What the dashboard is genuinely good for is scale and shape. Five systems is enough to show what an estate looks like when it is being governed rather than listed: which systems carry the heavier duties, where the gaps sit, what a readiness figure is actually built from, and what an obligation looks like when it is tracked to a named owner instead of a policy document. Reading it for ten minutes explains the product better than a feature list does.

What it cannot show you is your own estate. The systems are not yours, so the classifications are not yours either. If you want a real result against a system you actually run, the sandbox does that in a couple of minutes, and a workspace does it properly and keeps the record.

The dashboard is regime-aware in the same way the rest of the platform is. The same five systems are presented against whichever regime this deployment serves, so the obligations and citations you see are the ones that would apply to you, not a generic set. That is also a fair demonstration of the underlying design: the jurisdiction is a data slot, not a separate product.