kredis

kredis builds and maintains the compliance file on each counterparty a trading house deals with. It pulls company registry data, checks sanctions lists, maps who ultimately owns a company, and has an agent draft a risk assessment.

Nothing is cleared or rated until a named person approves it. Every step goes into an append-only history, so the file shows who decided what and when.

1. Assemble. The entity is built from official registries and screened against sanctions lists.
2. Map ownership. An ownership graph is drawn from beneficial-ownership filings.
3. Draft. An agent writes the risk assessment.
4. Approve. A person signs off, in one of two lanes.
5. Close the gaps. Counterparty outreach closes what is missing from the file, and a worklist shows what needs a human now.

Operations and board analytics views sit on top.

Agents propose, people dispose

No code path sets a clearance, a decision or a risk rating without a recorded human approval, and key actions need two people. The agents only draft and propose.

A decision endpoint with no model in it

The endpoint other systems call for a decision is deterministic. It reads precomputed state, and no language model sits in that path.

History you can replay

Case history is append-only. Every table is tenant-isolated with enforced row-level security. Policy grading uses versioned policy packs, so a past decision can be reconstructed against the policy in force on that date. It runs on GLEIF and Companies House data and on embedded OFAC, EU, UK and UN sanctions lists. Commercial data vendors plug in on the customer’s own licence.

kredis is for compliance, credit and risk teams at trading houses and other firms that onboard and monitor counterparties. Agents prepare the file, the team reviews it, and the history shows who decided what. It fits teams that need a defensible record for every clearance.