For MSPs and managed security providers
One judged mapping, reused across every client who needs the same two standards, with the reasoning attached so a client can check it rather than take your word.
The job: Deliver compliance outcomes at a margin, which means not rebuilding the same mapping for each new logo.
A released pair carries the coverage, the evidenced controls, the gaps, and the claims rejected in review. The next client on the same two standards is the same report.
See what is ready nowFree tools over MCP and REST, no key needed for the research calls, so the graph can sit behind a runbook, a ticket template or an internal bot rather than being another console someone logs into.
Connect in one pasteA client holding two certifications and facing a third wants the marginal number. Combined coverage says what two frameworks reach together and what neither of them touches.
Run it without an accountThis is not a multi-tenant GRC console. There are no client workspaces, no per-tenant dashboards and no white-label portal. If you need to show each client their own live posture, this is a data layer underneath that, not the thing itself.
Not as a programme. The data licensing page covers bulk and feed access, and for anything beyond that the answer is a conversation rather than a tier, because inventing partner mechanics for a business this size would be pretending.
The reports are yours to use in an engagement. Leave the stated level of review on them: a client is entitled to know the mappings were judged by Claude Code with a pass that argued against them, rather than read line by line by a practitioner.
The graph holds 686 frameworks and 59,673 judged cross-framework mappings, with 29,549 more that were judged and rejected and kept where you can read them.