Skip to content

The work behind the screen

Every obligation you read here comes from the text of the standard it names

Not a summary found on the web. Not a paragraph written by a model while you wait. We hold the standards, regulations and codes as published, read each one clause by clause, and write every requirement out with its clause number and the evidence an auditor asks for. The tools on our subdomains read your own list against that library and quote the clause that reaches each row.

Today that library holds 1,248 standards and regulations, 54,693 requirements, and more than 315K judged links between them, every one of which you can open and read.

1

We hold the standards themselves

ISO standards, EU regulations, national laws, sector codes and frameworks, kept as the published documents. When a new edition is issued, the new edition is read beside the old one and the difference is recorded, clause by clause.

2

Each one is read clause by clause, by a person's rule

Every requirement is written out as its own entry with its clause number, what it asks for, and the evidence an auditor would expect to see. A placeholder is never allowed to stand in for a requirement. When we only hold part of a document, the entry says so and carries a lower confidence, and it is read again when the full text arrives.

3

The requirements are linked to each other, one judgement at a time

Where two standards ask for the same thing, that link is judged on the two texts, not on how similar the words look. Links that do not hold are refused and the refusal is kept on record. That is why a security standard maps deeply into one law and barely at all into another: the judgement follows the text.

4

The tools do arithmetic on your rows and quote the clause

Each tool reads the list you already keep, in your browser, and matches every row against the requirements that reach it. What comes back is your own numbers and the obligation that attaches, cited to its clause. Nothing is written while you wait; the text was read long before you arrived.

5

Every line can be checked

Click any clause on any tool and it opens on the compliance platform, where the same requirement sits under its standard with its citation and its links. The platform publishes its own measured uptime and a benchmark of answers with and without this library behind them.

What this is not

  • Not generated on demand. Nothing on a tool page is written at the moment you click. The requirement text exists before you arrive and is the same for every reader.
  • Not a scrape. A summary page on the web is not a source. Where we do not hold the text of a standard, the tool names the obligation and says the text is not quoted.
  • Not a verdict. A tool shows your own numbers and the clause that attaches. It never rules that you comply, never rates a vendor and never says a task is lawful. That call is yours, with the text in front of you.
  • Not your data, kept. The first run of every tool happens in your browser. What you paste does not leave it unless you choose to save a register on an account.

Check it yourself

Open any standard
every requirement with its clause and citation
Read what we publish about trust
how the library is checked and what is refused
See the benchmark
the same questions answered with and without the library

Every tool built on it

Each one reads a list you already keep and gives it back with the obligations attached. Free first run, no account, nothing you paste leaves your browser.

Read the library for yourself

Every standard, every requirement, every judged link, open to read on the compliance platform.

Open the standardsTry a tool on your own list