Ballerine is an open-source platform for identity verification and risk decisioning aimed at fintech and marketplace teams. It combines KYC, KYB, and sanctions-screening vendor orchestration with a rules and workflow engine plus a backoffice for manual case review, and it can be self-hosted on premise or bought as a managed SaaS.[1][2]
Quick verdict
Ballerine fits fintech and marketplace teams that need reviewable KYC, KYB, and sanctions-screening workflows rather than a black-box vendor check. Its strength is the combination of vendor orchestration, a versioned rule engine, and a backoffice where operators approve, reject, or revise cases. The constraint is maintenance risk: the public repo banners itself as undergoing a major rebuild without active support, and managed pricing is not published. If you have developers and can self-host or get a quote, shortlist Ballerine; if you need a fully managed check, consider Persona instead.[1][2]
Key features
Vendor orchestration Orchestrates KYC, KYB, and AML data vendors into one onboarding flow, including IDV with document and selfie liveness checks plus government database lookups, instead of integrating each vendor separately.[1][2]
No-code workflow builder Provides a no-code builder for KYB and onboarding flows such as the documented KYB parent-company ownership structure example, letting operators shape collection and decisioning steps.[1]
Backoffice case management Ships a case-management backoffice where reviewers approve, reject, revise, assign, and escalate verification cases, with omni-search and admin and viewer roles.[1]
Versioned rule engine Includes a deterministic, versioned rule engine that supports JavaScript snippets with access to API data for custom risk-decision logic.[1]
Document collection flows Collects applicant documents through structured flows synced with live review cases, covering passports, IDs, and supporting KYB paperwork.[1][2]
Sanctions and risk screening Covers sanctions-list screening and transaction monitoring in its merchant-risk scope, with vendor marketing claiming up to 90 percent fewer false positives, which is a vendor claim rather than an independently verified measurement.[1][2]
Plugin system Offers an extensible plugin system of integrations, workflows, and UI components for teams that need to add vendors or steps beyond the built-ins.[1]
Self-hosted deployment Supports on-premise self-hosting with full data ownership, plus a documented local Docker-based stack for evaluation.[1]
Who will love it
Fintech onboarding teams Fintech and marketplace teams running KYC, KYB, and sanctions checks that want one orchestrated flow ending in a human review queue.[1][2]
Ops-heavy risk teams Risk and compliance operations that need a real backoffice with assignment, escalation, and audit-friendly approve or reject decisions.[1]
Data-ownership teams Teams that must keep verification data on premise and have the developers to deploy and maintain a TypeScript and Docker-based stack.[1]
Who should avoid it
Maintenance risk The public repository banners itself as undergoing a major rebuild and not actively supported, so teams should confirm maintenance status before adopting it.[1]
No published SaaS price The managed SaaS has no published pricing, so budgeting requires a sales quote rather than a listed plan.[1]
Developers required Despite the no-code builder, setup, integration, and upkeep need developers, so non-technical teams without engineering support should avoid it.[1]
Alternatives and deployment
Persona for managed checks Persona is the listed proprietary alternative for teams that want fully managed identity verification without running infrastructure.[1]
AGPL-3.0 self-hosting The open-source edition is recorded as AGPL-3.0, which suits teams that can comply with strong copyleft while self-hosting.[1]
Managed SaaS option Ballerine also sells a managed SaaS for teams that prefer not to operate the stack, with sales contact published in the repository.[1]
Questions worth asking
What is the best Ballerine alternative for non-technical users?
For non-technical teams, Persona is the conditional pick: it is a fully managed proprietary identity-verification platform covering the same KYC, KYB, and risk workflows without self-hosting. Ballerine assumes developer involvement, so choose Persona when no one on the team can run infrastructure.[1][2]
Is Ballerine really no-code?
Partly. Operators use a no-code workflow builder and a backoffice UI for reviews, but deploying, integrating, and maintaining Ballerine still needs developers working with its TypeScript monorepo and Docker-based stack.[1]
How much does Ballerine cost per month?
Can you self-host Ballerine?
Yes. Ballerine documents on-premise self-hosting so teams own their own data, with a local Docker-based stack for evaluation. The catalogue records an AGPL-3.0 licence, and the public repo notes it is undergoing a major rebuild, so confirm maintenance status before committing.[1]
Sources and editorial review
Source research. Reviewed on October 7, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Ballerine: Risk Decisioning for Acquirers and Payment Facilitators
official · Observed October 7, 2026
Official homepage describing merchant-risk orchestration, IDV with document and selfie liveness plus government database checks, and vendor marketing claims. Visited October 2026.
- ballerine-io/ballerine repository
official · Observed October 7, 2026
Public monorepo README: open-source risk-management infrastructure, module list, rebuild notice, self-hosting and SaaS contacts. Observed October 2026.
- Ballerine brings open source to banks risk and identity decision-making
published measurement · Observed October 7, 2026 · Published May 23, 2023
May 2023 funding report: Ballerine founded 2022, $5M seed, Apache 2.0 at the time, backend plus hosted deployment, named alternatives Persona, Alloy, and manual review.
- Ballerine Documentation
official · Observed October 7, 2026
Official documentation landing page, which redirects to a sign-in gate; confirms docs exist but are access-restricted. Observed October 2026.