A star chart of everything you know

Every system, table and field we have found, and what is actually in them.

• Connect a system yourselfEnter credentials, validate them, and start the first look without waiting for anybody.Available now

  Enter credentials, have them checked, and start the first look without waiting for anybody. Checking stores nothing: the button that validates and the button that saves are two separate clicks, because a stored-and-broken credential looks exactly like a working one on every screen that lists connections.

• System, table and field censusEvery table and field found, and how full each one is.Needs a connected system

  Structure only. KWAYZER Atlas records that a column exists, what shape it holds and how full it is, and never copies a value out. Where a count hit a cap it is shown as a floor rather than a total, and where no count was taken it says so instead of showing zero.

• Discovery confidenceHow much of your estate this has actually seen, and what it has not.Needs a connected system

  How much of your estate this has actually seen, and what it has not. Every discovery carries a confidence and the basis for it, so nothing is presented as certain because it happened to be easy to compute.

• Ownership proposalsWho looks accountable for each dataset — proposed, never assumed.Needs a connected system

  Proposed from observed activity — who actually touches a dataset — and confirmed by a human. Ownership nobody accepted is recorded as unowned rather than assigned by default, which is the difference between a register and a guess.

• Sensitive-data classification queueFields that look like personal or secret data, for a person to accept or reject.Needs a connected system

  A queue, not a wall of red. Proposals arrive ranked by materiality, and you confirm, correct or say you cannot judge — and cannot judge is a real answer that routes onward rather than being coerced into a decision.

• Personal-data flowWhere personal data enters, where it goes, and where it leaves.Needs a connected system

  Where personal data enters, where it goes and where it leaves, with the boundary stated: what was examined, what was not, and why. Detection is at the level of names and shapes; the values themselves are never examined.

• Change-aware rescanningWhat moved since the last look — volume, freshness and shape.Needs a connected system

  Re-read on a schedule and report what moved — structure, volume, freshness, shape. When a number changes you can see whether the data changed or the definition did.

• Dark-data detectionFiles kept outside your system of record, compared against it.Run with your KWAYZER contact

  The tables and files nobody has queried in years: the rows that cost storage, carry risk and serve nobody. Usually the first number that makes a finance director sit up.

• Normalization and ambiguity checkDates, numbers and times that could be read two ways — before anything moves.Run with your KWAYZER contact

  Dates, numbers and times that could be read two ways — before anything moves. A column that is ambiguous between two readings is reported as ambiguous rather than being silently resolved to whichever one the parser preferred.

• Health by kind of dataHow complete, how current and how owned each kind of data is — three readings, never added up.Needs a connected system

  Your estate grouped by what each dataset appears to BE — people, organizations, tickets, transactions — with three separate readings for each: how complete, how current, and who owns it. They are never added into one number, because a gappy table, a stale one and one nobody owns need three different conversations, and a single score hides which you have. Where a scan could not measure something, it says so rather than counting it as a problem.