The new design
Try it
Section titled “Try it”Open Settings in Keryn Web and turn on Try the new design. Turn it off the same way. To look at it for one page without changing the setting, add ?ui=exploration03 to the address (?ui=classic shows the current design); that choice is never stored. The theme choice applies in the new design too, so it has a light version as well as a dark one. Your scans, results and decisions are the same in both designs: only how they are laid out changes.
What changes
Section titled “What changes”The left rail becomes six places in a fixed order: Start, Scan, Decision, Evidence, Trust graph, AI-BOM. On a phone the rail is a bar at the bottom. Each screen leads with one sentence. The pictures below are of the new design scanning the help-desk sample and the trip-planner sample; the pictures below show the dark theme.
Start: “See where input becomes action.”
Section titled “Start: “See where input becomes action.””The place to give Keryn a repository, folder or file, with a faint path from code to agent to tool behind it. Next to it, the lines that say where the scan runs: in your browser, local files never uploaded, rules run locally, and that results are saved only in this browser.


Scan: “Evidence is taking shape.”
Section titled “Scan: “Evidence is taking shape.””The stages of the scan, each marked done, running, waiting or skipped, and the findings found so far. Each early finding carries its state (a raw match, provisional or final), and the list does not reorder as the scan goes on.


Decision
Section titled “Decision”The status as one large object with its word, HOLD here, the reason in one sentence, the number of findings, the trust score and the risk score, and what would make it Go. There is an Inspect blocker action and a count of accepted risks.


Evidence
Section titled “Evidence”The finding as a sentence, its severity, status and proof level (pattern, path, confirmed), the code at the line, and why it matters, the trace, the fix and the owner. Previous and Next move through the findings.


Trust graph: “One path crosses the boundary.”
Section titled “Trust graph: “One path crosses the boundary.””Three layers (external input, agent runtime, tenant data), the one path drawn in amber with a marker where it crosses a boundary, and the path card docked at the bottom with a link to the full map. When there is no such path, the sentence says so.


AI-BOM: “Know what your agent depends on.”
Section titled “AI-BOM: “Know what your agent depends on.””Models, SDKs, MCP servers and other tools in groups, each with a Passed or Review mark and where it was found (source, lockfile, config or endpoint), and a ring that counts the policy checks that pass.


One status colour system
Section titled “One status colour system”The same four states look the same on every screen, and each one is also written out in words, so colour is never the only signal.
| State | Colour | Label |
|---|---|---|
| Hold or blocking | Amber | Hold, Blocking |
| Go or passed | Mint | Go, Passed |
| Needs review | Violet outline | Review |
| Unknown | Grey | Unknown |
Severity and where a finding came from stay neutral: colour is reserved for what you should do about it.
For designers and engineers
Section titled “For designers and engineers”The new design adds tokens to the existing design system and does not replace it: the design system lists them next to the current ones. Every screen works at 1363 and 390 pixels wide and is checked for contrast, keyboard use and screen readers.