Jube
7.3#3 in financial crime compliance softwareFrom $350 a monthFree planWebAPILinuxSelf-hosted
Visit| Fact | Jube | Ojuri |
|---|---|---|
| Deployment | Jube is containerized for Docker and Kubernetes, supports multi-tenancy, and can run on an organisation’s own infrastructure or cloud tenancy. | The quickstart uses Docker Compose and requires Docker and Node 20; the investigation model is optional and downloads about 7.6 GB of weights when enabled. |
| Explainability | The site says Bayesian Networks and decision-tree rule output can be explained to regulators and describes calibration and validation against BASEL practice. | Responses include reason codes, feature contributions, observed values, model version, threshold, and audit ID. |
| Integrations | The product page lists PostgreSQL for durable storage and audit logs, Redis for real-time state, and RabbitMQ via AMQP for inbound and outbound events. | The stack uses Kafka, Redis, PostgreSQL, ONNX Runtime, Docker Compose, NGINX, and Prometheus/Grafana components. |
| License | The site says Jube is fully open source under AGPLv3 and that all features are available. | The repository is released under the MIT license. |
| Purpose | Jube is an open-source platform for real-time suspicious-transaction detection, AML case management, and fraud prevention. | Ojuri is a self-hosted fraud detection engine that scores transactions and returns accept, review, or decline decisions. |
Jube is intended for compliance teams, financial institutions, fintechs, and organizations adopting AML or fraud detection. It suits teams able to manage a self-hosted deployment and account for AGPLv3 obligations.
Ojuri suits fintechs and payment platforms that need transaction scoring within their own infrastructure. It may also suit teams that want analyst review, model monitoring, and investigation tools alongside live scoring.