Jube vs Ojuri

Jube is a free, open-source platform for real-time suspicious-transaction detection, AML case management, and fraud prevention. Its monitoring combines threshold, velocity, and aggregation checks with sanctions screening, supervised and unsupervised machine learning, TTL counters, and suppression. Interfaces support synchronous, asynchronous, and hybrid operation over HTTP and AMQP. Redis stores real-time state, PostgreSQL provides durable storage and audit logs, and RabbitMQ handles inbound and outbound events. Case management covers AML, fraud, and compliance streams, with investigator dashboards, document versioning, escalation, and audit trails. Jube says Bayesian Network and decision-tree outputs can be explained to regulators and describes calibration against BASEL practice. The software runs in Docker and Kubernetes, supports multiple tenants, and can be deployed on customer infrastructure or cloud tenancy. Jube is available under AGPLv3 with all features. Support and training are separately priced, including sandbox, growth, scale, enterprise, and training options.

Ojuri is a self-hosted fraud detection engine for fintechs, payment gateways, and mobile-money platforms. It scores transactions and returns accept, review, or decline decisions, with applications able to call its POST /v1/predict API. The Real-Time Detection Agent scores payments on the authorization path using an XGBoost model served through ONNX Runtime. A Pattern Analysis Agent follows account, device, and payee relationships over time to identify fraud rings and mule networks. Decisions record reason codes and the data considered by the model in an audit log. Sentinel provides a review queue, decision stream, model registry, and analyst overrides that can become training data. Other agents monitor drift, retrain on verified labels, and check evaluations before model promotion. An optional investigation agent creates reports for declined transactions using a self-hosted language model, separate from live scoring. Ojuri says its services and transaction data remain within the operator’s infrastructure. The project is MIT licensed, with no per-call fees or rate limits.