Marble

Key features

• Real-time decision API Returns approve, review, or decline in under 50 milliseconds at p99 with 99.99 percent availability, so transaction flows can block on a decision without timing out the checkout.[1]

• Visual scenario builder Lets risk operators compose trigger, rules, screening, and outcome blocks into versioned scenarios, keeping policy changes in the hands of the team that owns fraud outcomes.[1][2]

• Dry-run testing Runs a scenario against historical or sample traffic before it goes live, so a new rule proves itself against known fraud patterns instead of learning on production.[1]

• Data-enrichment plugins Pulls third-party and internal data into the decision context at evaluation time, widening what a rule can see beyond the raw transaction payload.[1]

• Fuzzy matching Catches near-miss name and entity variations that exact matching would let through, which matters for sanctions and watchlist screening quality.[1]

• Sanctions and watchlist screening Screens entities against sanctions, PEP, and adverse-media lists via an OpenSanctions integration, with matches flowing into the same review queue as rule hits.[1]

• Case manager Gives analysts a review workspace with assignment, snoozing, transfers between queues, and resolution actions, closing the loop between automated decisions and human judgment.[1][2]

• Scheduled executions and webhooks Re-evaluates entities on a schedule for ongoing monitoring and pushes decision events to your systems; scheduled rules plus snoozing mean an entity that looks clean today can be re-checked automatically when new data arrives.[1]

Who will love it

• Real-time fraud teams Groups blocking payments, signups, or transfers on a risk decision get sub-50 ms answers with a review path for the uncertain middle, not just a binary score.[1]

• Compliance operations with screening load Teams running sanctions, PEP, and adverse-media checks get screening wired into the same scenario and case queue as their fraud rules.[1]

• Policy owners who want testability Risk owners who need to prove a rule change before it ships get versioned scenarios with dry runs rather than edit-and-hope configuration.[1]

Who should avoid it

• No free or OSI-open starting point Paid cloud plans start at $499 per month and the licence is source-available Elastic License 2.0, so budget-free or strictly open-source shops should look elsewhere.[1][2]

• Developers required The scenario builder is visual, but integrating the decision API, enrichment, and webhooks into production flows still needs engineering support.[1]

• Quote-based enterprise pricing Business-plan pricing is custom and quote-based, so budgeting at scale requires a sales conversation rather than a listed plan.[1]

Alternatives and deployment