KWAYZER Atlas
Every system you have, what is in it, and what it means.
Companies whose data is spread across systems nobody has a full list of — and companies old enough that the people who knew what the fields meant have retired.
What it does
DiscoverEvery system, table and field, recorded and searchable.
A crawl records what exists: datasets, field names, fill rates, how many records were seen. 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.
RememberWhat the data MEANS, including what was never written down.
Statements about meaning are proposed, then confirmed or corrected by the people who know, and stored with who decided and when. A statement nobody has answered is counted separately from one that has been settled — an unanswered question is not an agreed meaning.
OrganizeOne agreed definition per thing, and where your systems disagree.
Trust signals are computed per dataset and reported as counts rather than a score, because one of them can never be earned from a source export and a ratio would sit below full forever on a perfectly governed dataset.
ServeHand your own tools the governed definition and how to connect.
A data dictionary is produced from what was recorded — dataset, field, type, fill rate, the governed term. Your tools connect to your systems; what they get from us is the definition.
Why this is hard to copy
Each of these names the mechanism that makes it true and where to check it. A claim without one is a sentence anybody could write.
We never hold your business records.
Because every server module that writes to the catalog's tables routes through a check that throws on a row carrying a record payload, and a test enumerates the write sites and states exactly which are exempt and why.
tests/atlas-holds-no-rows.test.ts
A reference that turns out to be somebody's email address is tokenised.
Because the one column where a customer's own field value could reach a permanent table is tokenised per workspace, keyed to the reason it would otherwise be refused.
src/lib/migration/tokenisation.ts
A failed read never renders as an empty estate.
Because every pillar returns three states, and the could-not-read branch is evaluated before the nothing-recorded one, so the reassuring answer cannot win a tie.
src/lib/atlas/tenant-server.ts
Pricing
Scope varies with the size of the estate, so there is no list price. Tell us what you have and we will tell you what it takes.
The rest of KWAYZER
Five products on one identity, one permission model and one audit log. You can buy one and add another without a migration.