Open Source Seon Alternatives
A curated collection of the 2 best open source alternatives to Seon.
The best open source alternative to Seon is Ballerine. If that doesn't suit you, we've compiled a ranked list of other open source Seon alternatives to help you find a suitable replacement. Other interesting open source alternative to Seon is Tirreno.
Seon alternatives are mainly Compliance & Risk Management but may also be Finance & Fintech or Fraud Prevention. Browse these if you want a narrower list of alternatives or looking for a specific functionality of Seon.
Risk management infrastructure for payment companies and marketplaces, automating KYC, KYB, underwriting and transaction monitoring across the customer lifecycle.
Ballerine is risk management infrastructure for payment companies, marketplaces and fintechs that must decide, repeatedly, whether a merchant, seller or user is safe to onboard and keep. It reaches from account opening through KYC and KYB into underwriting and transaction monitoring, in one system rather than across several vendor dashboards.
The design is modular, held together by a workflow engine that defines the process steps and moves work between the parts. Self-hosting is the intended deployment for teams whose sensitive identity data has to stay inside their own infrastructure, and vendors can be added or swapped to serve users in different countries.
The system breaks into named modules.
- Workflow engine: orchestrates and automates the other parts of the system.
- KYB collection flow: document and information journeys that change in real time based on the user's risk.
- Rule engine: several rule types for checking a user against your risk policy.
- Plugin system: integrations with third-party vendors, APIs and databases.
- Back office: a case management dashboard for the decisions a person still has to make.
- No-code builder: marked in the repository as work in progress.
A local environment needs Node.js, pnpm and Docker Compose, and the repository ships KYC and KYB manual review examples that start with one command. One caveat outweighs the rest, and the maintainers put it at the top of the README themselves: the open source repository is undergoing a major rebuild and is not actively supported at present, with support questions pointed toward the hosted version.
Self-hosted security framework that watches user activity inside your application to catch account takeover, fraud and abuse.
Most breaches do not arrive through the network perimeter. Tirreno is a security framework that sits inside your product and reads the events it generates, so compromised accounts and application logic abuse surface in the one place firewalls, WAFs and SIEM tools never look.
The application is hand-written PHP backed by PostgreSQL, with few dependencies and a five-minute install. You send events through the API or through one of the trackers for PHP, Python, Node.js and WordPress, and a real-time threat dashboard fills in immediately.
The moving parts are deliberately few.
- Rule engine: risk scores are calculated automatically from preset rules or from ones you write for your own product.
- Single user view: behavior patterns, risk scores, connected identities and an activity timeline for one account.
- Review queue: threshold settings suspend risky accounts automatically or flag them for a human to look at.
- Field audit trail: changes to important fields are tracked, including what changed and when.
- Preset rules: account takeover, credential stuffing, bot detection, multi-accounting and promo abuse ship ready to use.
Requirements are modest. PHP 8.0 to 8.3, PostgreSQL 12 or later, Apache with mod_rewrite, and roughly 3 GB of storage per million events. A Docker Compose command, a Heroku button and a Composer package all work, and a cron entry every ten minutes handles background jobs. It suits SaaS platforms, marketplaces, internal and legacy apps, and air-gapped deployments.
