ComplyLayer
Allow, flag or block — in under 100 ms, against rules a compliance officer wrote.
- Python
- Django
- PostgreSQL
- Docker
The problem
Compliance rules live in an engineer’s backlog. The person who understands the regulation writes a ticket; somebody who does not implement it; and the gap between the two is where the fine comes from.
ComplyLayer lets the compliance officer author, test and approve the rule themselves — through a maker-checker workflow, with no pull request and no deploy.
What I built
- A verdict in under 100 ms: allow, flag or block, with the regulation it implements cited on the decision.
- A deterministic, integer-only rule grammar so a decision made six months ago reproduces exactly.
- Maker-checker approval — nobody ships a rule alone — and row-level security for tenant isolation.
Decisions worth naming
- Division is not in the rule grammar. Floating point makes a decision that cannot be reproduced, and an unreproducible compliance decision is indefensible in front of a regulator.
- Every verdict carries a message a customer can read, not a rule id.
What is not finished
- Rule packs ship for CBN AML/CFT; other regimes are a data exercise rather than a code one.