jiraska/open-bank-oss — explained in plain English
Analysis updated 2026-05-18
Study a full example of a modern retail bank's backend, including ledgers, payments, and compliance flows.
Try live sandbox API calls, like creating an account or sending a SEPA payment, against a hosted demo.
Explore the PSD2 open banking developer portal to see how third-party access APIs are exposed.
Use the project as a starting point for a licensed banking platform, since it is not itself licensed to operate as a bank.
| jiraska/open-bank-oss | 521xueweihan/hgdoll | areu01or00/hermes-agent-mobile-client | |
|---|---|---|---|
| Stars | 20 | 19 | 19 |
| Language | Kotlin | Kotlin | Kotlin |
| Setup difficulty | hard | hard | moderate |
| Complexity | 5/5 | 4/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Roughly 37 backend microservices with event-driven infrastructure, trying the hosted sandbox is far faster than running the full stack locally.
OpenBank is an open-source reference implementation of a retail banking platform, built to show how a modern bank's backend could actually be constructed. It is written mainly in Kotlin using the Quarkus framework for its roughly 37 backend microservices, paired with a Next.js frontend, and organized around event-driven, hexagonal architecture with a double-entry ledger for accounting. The project is explicit that it is not licensed to operate as a real bank and is not production-ready. It is meant to be a software platform that someone with an actual banking license and capital could deploy, and the name OpenBank is not affiliated with any existing bank or trademark holder. The project is in beta, with its first milestone complete and later milestones in progress. According to its own status table, core banking features like accounts, ledgers, balances, and intra-bank payments are implemented, tested, and deployed to a live AWS sandbox. Features like SEPA and domestic payments, standing orders, cards, lending, fraud detection groundwork, and digital identity flows following EU standards are also deployed, though some pieces, like live connections to real interbank payment networks or a full credit bureau integration, are still missing or stubbed out. There is also an AI copilot service and a separate policy-gated AI agent interface for internal operations tooling. The sandbox environment at open-bank.tech lets anyone try live API calls, such as creating an account, checking a balance, or sending a SEPA payment, all protected behind bearer token authentication and rate limiting, alongside an admin backoffice and a developer portal for exploring the PSD2 open banking APIs. The platform code itself is released under the Apache 2.0 license, while the AI agent-related services use a dual AGPL-3.0 plus commercial license, meaning the agent code is free to use under strict open-source terms or available under a separate paid license for those who need different terms.
An open-source reference implementation of a full retail banking backend, built with Kotlin microservices, event-driven design, and a live sandbox demo.
Mainly Kotlin. The stack also includes Kotlin, Quarkus, Next.js.
The main platform code is free to use for any purpose, including commercial use, under Apache 2.0, the AI agent services are under a stricter open-source license (AGPL-3.0) or available under a separate paid commercial license.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.