{"repo":"sofeikov/ezrules","free":true,"listed":false,"github":"https://github.com/sofeikov/ezrules","clone":"git clone https://github.com/sofeikov/ezrules.git","description":"Welcome to an open-source transaction monitoring engine! This product is designed to simplify the definition and management of business rules while also offering a scalable infrastructure for rule execution and backtesting.","language":"Python","stars":11,"topics":["business-rules-engine","fintech","transaction-monitoring"],"license":"Apache-2.0","category":"analytics","readme_excerpt":"ezrules Website & live demo · Documentation · Blog Open-source transaction monitoring for teams that need clear rule control, auditability, and fast operational changes. ezrules gives fraud, risk, and compliance administrators a web workspace for managing decision rules without turning every policy update into an engineering project. Rules can be drafted, tested, reviewed, promoted, paused, rolled out, and audited from one place, while your systems keep sending events to a simple evaluation API. Why Teams Use It - Own the rule lifecycle. Create rules, keep drafts separate from live logic, pause risky rules, restore older revisions, and promote changes deliberately. - See what happened. Review canonical served decisions, the outcome returned, every rule that fired, and the exact event version those rules used. - Work the exceptions. Turn non-neutral decisions into resolvable cases, track rescoring changes, and publish case/evaluation events to external systems. - React to outcome spikes. See new alert incidents in the live notification badge and open the affected cases directly from a bounded, scrollable inbox. - Improve rules with evidence. Use labels, precision/recall reports, backtests, shadow rules, and percentage rollouts before changing production decisions. - Use reproducible historical features. Computed counts, distinct values, sums, averages, extrema, standard deviation, and days-since features follow documented point-in-time, correction, null, and type semantics. - ","default_branch":null,"files":null,"tree":[],"storefront":"/r/sofeikov","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/sofeikov/ezrules/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}