mirror of https://github.com/hanzoai/aml.git synced 2026-10-30 18:48:24 +00:00

Files

T

zooqueenandHanzo Dev f885d601ea hanzoai/aml — Hanzo brand deployment of the luxfi/aml engine

Thin wrapper, the hanzoai/kms pattern: pins the engine version (ENGINE_VERSION),
builds the engine's own image on the native hanzo runner, and dual-publishes to
ghcr.io/hanzoai/aml and oci.hanzo.ai/hanzoai/aml. The binary white-labels by host;
this repo owns the Hanzo registry namespace and deployment config.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-30 05:08:15 -07:00

1.2 KiB

Raw Permalink Blame History

Hanzo AML

Real-time AML/CFT transaction monitoring, sanctions screening and case management — the Hanzo-branded deployment of the canonical luxfi/aml engine, the way hanzoai/kms is the Hanzo deployment of luxfi/kms.

All engine logic lives in github.com/luxfi/aml. This repository pins an engine version, publishes the image to Hanzo's registries, and carries the Hanzo deployment's configuration. The binary itself is brand-neutral: it white-labels by request host (Lux on lux.network, Hanzo on hanzo.ai, Zoo on zoo.ngo) and validates every token against that host's brand issuer, so one image serves the Hanzo surface at api.hanzo.ai.

Deployment shape

One deployment per institution: its own store, its own IAM application (AML_CLIENT_ID — the audience every token is pinned to), its own ingress host. Per-brand stores make a cross-brand tenant collision structurally impossible rather than merely guarded.

Canonical source: git.hanzo.ai/hanzoai/aml (this repo), mirrored to GitHub.
Image: ghcr.io/hanzoai/aml (canonical mirror oci.hanzo.ai/hanzoai/aml).
Engine module: github.com/luxfi/aml at the pinned ENGINE_VERSION.

1.2 KiB Raw Permalink Blame History

Hanzo AML

Deployment shape

1.2 KiB

Raw Permalink Blame History