// the find
ballerine-io/ballerine
Open-source infrastructure and data orchestration platform for risk decisioning
Ballerine is a KYC/KYB and fraud risk workflow platform — document collection flows, a case management back office, a rule engine, and plugin system for connecting third-party verification vendors. It targets fintechs and payment companies that want to own their compliance stack instead of paying per-verification to a SaaS provider. The monorepo covers frontend SDKs, a React back office, and a NestJS workflow service.
The workflow engine design is genuinely useful: you define KYC/KYB journeys as JSON state machines, which means compliance teams can adjust flows without redeploying. The back office component library is thorough — case assignment, document review, resubmission requests, and risk rule display are all built out. Plugin architecture for third-party vendors (identity verification, AML screening) is the right call for a compliance tool where vendor relationships change constantly. CI/CD pipeline with ArgoCD, preview environments, and separate deployment workflows per service shows production-grade infrastructure thinking.
The README has a prominent banner saying the OSS repo is undergoing a major rebuild and is not actively supported — that is a hard stop for anyone evaluating it for production use today. The rule engine is flagged as still under construction in the same README, which is the core differentiated piece; without it you're building your own rules on top of an incomplete foundation. It's a large, complex monorepo (NestJS backend, React backoffice, Svelte SDK, multiple workflow apps) with no clear getting-started path beyond running one of two Docker Compose examples — customizing beyond the demo requires reading a lot of undocumented internals. Self-hosting the full stack for a compliance use case means you own the audit trail, document storage, and data residency concerns yourself, which is non-trivial.