.tf→
origindelivery
Infrastructure as Code
Give the environment a blueprint.
Explore the example
This website’s infrastructure is defined in code: its origin, delivery layer and access controls.Open the blueprint ↗
Open source. Open possibilities.
A bank you can
look inside.
Explore the app. Understand the platform.
Help build the shared banking core.
Public sandbox · Reference implementation
Bank as Code
Built for AI.
Made for people.
A shared banking foundation for an AI future. Explicit rules, reviewable changes and traceable evidence, with people in control.
Rules people and AI can read.
Changes people can challenge.
Evidence auditors can examine.
The power is in the connections
Follow a change.
See the whole story.
A banking decision travels through products, systems and teams. Bank as Code makes those connections part of the design.
CHANGE JOURNEY / INTERACTIVE CONCEPT
01 / DEFINE
One intention.
A product rule becomes explicit.
02 / EXPLORE
Visible impact.
Scenarios reveal consequences.
03 / REVIEW
Human judgement.
People examine the change.
04 / TRACE
A connected record.
Decisions stay with their context.
Start with a clearly defined product change.For AI to work with. For people to govern.
Eight disciplines. One direction.
The bank is the system.
Code connects the pieces.
Explore the project through working examples and the experiences we’re building next.
docs↔version
Documentation as Code
Keep the explanation with the software.
Explore the example
Services can publish bundled documentation with their version and source revision. A shared reference for people and AI.Explore Docs as Service ↗
rule→check
Compliance as Code
Connect a requirement to its evidence.
Explore the example
Governance checks challenge service declarations against implementation. The foundation for a connected evidence trail.Examine the checks ↗
2.50%→€
Product as Code
Make the terms executable.
Explore the example
Our savings sample expresses interest, bonus conditions and fees. An interpreter gives the definition behaviour.Read the product definition ↗
signal→case
AML as Code
Keep decisions in context.
Explore the example
The AML case model records decisions and requires a reason for blocking. Relationship investigation extends the story.Explore the investigation design ↗
maker≠checker
Fraud as Code
Give every rule change a history.
Explore the example
Threshold proposals have versions and effective dates. The proposer cannot approve their own change.Inspect the approval tests ↗
agent→policy
AI as Code
Give AI a role and clear boundaries.
Explore the example
MCP tools pass through policy checks. Tests exercise permitted and denied calls, including their audit records.Explore tool access tests ↗
people↔AI
Bank as Code
Make the connections visible.
Explore the example
A product change connects definitions, simulations, controls and human review. This is the experience we’re building toward.Explore the open project ↗
Inside the idea
Less abstract.
More “show me”.
Three stories. Three ways to explore what Bank as Code can make possible.
PRODUCT AS CODE
One rate change.
One rate change.
A bigger story.
From a product definition to a customer outcome.
Explore the product story ↗CONTROLS & EVIDENCE
Show the rule.
Show the rule.
Follow the evidence.
Make a control understandable and its review traceable.
Explore the control story ↗AI AS CODE
More capability.
More capability.
Clear authority.
See how a tool request meets a policy boundary.
Explore the AI story ↗Choose your way in
One open core.
A whole bank to explore.
OpenBank is an open-source banking reference implementation: connected domains, a customer app, shared banking libraries, Product Studio and governed AI tools. Follow the architecture, the evidence and the experience from one place.
01 / THE APP
Banking, in your hands. ↗
See the real customer experience, then join the iPhone beta.
02 / THE PLATFORMGo behind the screen. ↗
Explore the domains, services and contracts that make it work.
03 / THE AGENTSMeet the crew. ↗
Clear roles, bounded tools and a human responsible for impact.
The bank as one system
One bank.
Every connection counts.
OpenBank is an open-source banking ecosystem for the work inside a bank and the relationships it serves outside. Explore the domains together, follow the evidence behind them and see how a shared core keeps the experience coherent.
01 / INSIDE THE BANKFrom a customer need
From a customer need
to the whole bank.
Identity, products, accounts, payments, risk and operations are separate domains with visible contracts. Follow how they work together instead of treating each service as an island.
Explore every banking domain →OpenBankone connected architecture
Identity & relationshipsProducts & pricingAccounts & paymentsRisk & complianceTreasury & wealthOperations & AI
openbank-libsShared rules & contracts
Test evidenceUnit · contract · journeys
ObservabilityTraces · metrics · liveness
The loop: shared rules → tests that exercise them → operational signals that show what actually happened.
02 / THE RELATIONSHIPSee the person.
See the person.
Understand the context.
A holistic bank view starts with identity: one person may act for companies, hold different products and eventually bring a wider wealth picture into view. Each connection needs a source, permission and purpose.
Explore the context-graph design →Customer 360 is shipped; person–company links are partial and the broader wealth view is planned.
Personverified identity
Companiesroles & mandates
Wealth viewplanned composition
Ideas become
real products.
Design specifications and contextual offers, review a versioned draft, then publish through maker-checker controls. The catalog keeps the approved terms clear and reproducible.
DefineComposeReviewPublish
Open Product Studio ↗
Operator sign-in required · explore the source
Banking context,
ready for AI.
A customer-facing copilot and governed MCP tools let AI work with banking context in the public sandbox. Access follows consent, policy and audit; payment actions remain proposals for human review.
Customer → CopilotBank team → Governed MCP
Explore the MCP source →
External MCP access beyond the sandbox is not yet enabled.
Home screen with the Lípa identity.
The customer app
Your money.
Your way in.
A familiar app with a curious little bot. Explore balances, currency pockets and everyday banking on the same open core.
Kotlin Multiplatform and Compose connect the iOS and Android experience. The screenshot shows the app running on an iPhone, with its real home screen and the Lípa identity.
iOS TestFlight beta
Take OpenBank for a spin.
Drop the Apple ID email your TestFlight uses and we'll send an invite. That's the only thing we ask for.
No account, no card, no tracking. Your email is used only to send the TestFlight invite, with your explicit consent, and deleted when the beta ends. What exactly we collect ↓
Inside the platform
There’s a whole bank
behind that balance.
Accounts are just the beginning. Follow payments, identity, credit, treasury, risk, customer relationships and the platform that connects them.
A repository inventory shows what is implemented in code, not what is running right now.
Meet the crew
Helpful by design.
Bounded by policy.
Our lions help you explore. Our bot helps you understand. Agent roles have their own tools, permissions and limits.
Inspect the charters, follow a proposal and see where a human takes over. A friendly face never stands in for approval authority.
Open the actual product
See the work.
Follow the evidence.
Open mind. Open source. Open bank.
The common core
should belong to everyone.
Build, test, challenge or contribute. Help turn a reference implementation into a shared foundation for better banking software.
The Open Bank Foundation remains a proposal, not an incorporated organization.
Share the common core. Keep your customer experience your own.