Baobyte AML Suite
Book a demo
Documentation contents

Start here

Getting started

The shape of the platform in one read — enough that every other page makes sense on its own.

Baobyte AML Suite is an AML/CFT operating platform: customer due diligence, transaction monitoring, screening, investigation and governed reporting in one system, with the evidence behind each decision retained alongside it. This page is the orientation — enough of the shape that the concept pages, the guides and the API reference each make sense on their own.

One deployment, many institutionsPermalink to this section

Every row belongs to exactly one tenant, and no query path spans them. Isolation is enforced in five independent layers rather than by application code that remembers to filter. Authentication is delegated to an identity provider; authorization belongs to the platform, and every one of the API's operations declares the permission it requires.

The lifecyclePermalink to this section

  1. 1

    Understand the customer

    A party is any person or entity the platform knows about; a customer is a relationship with one. CDD answers are captured against a versioned form and stored verbatim, identity evidence records how strongly it was verified, and weighted factors produce a risk band.

  2. 2

    Detect

    Transactions arrive by batch or API into one table. Monitoring rules — a window and a predicate over a declared field vocabulary — raise alerts, and screening compares parties against watchlist entries with the per-attribute evidence retained.

  3. 3

    Investigate

    Alerts and hits about one subject are worked together in a case that assembles the customer record, ownership, transactions, notes and evidence. Dispositions carry a rationale and an author.

  4. 4

    Report

    Reports are generated through versioned mappings, validated with the evidence retained, and reviewed and approved by someone other than the generator.

What governs a decisionPermalink to this section

Three mechanisms recur, and most of what is distinctive about the platform follows from them. Configuration is versioned rather than mutable, so the rule in force when an alert was raised is recoverable. Approval is one generic maker-checker primitive rather than a workflow per feature, so no surface quietly permits self-approval. The audit trail is hash-chained per tenant, so history is not merely append-only but tamper-evident to anyone holding the database.

Where to go nextPermalink to this section

  • Evaluating: read the concept pages in order, then the security model.
  • Integrating: API conventions, then authentication, then the endpoint reference for your area.
  • Operating: the guides, in the order your role touches them.
  • Auditing: the security model, the audit and evidence concept, and the document register for what is released under agreement.