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

OpenBank’s lion and lioness explore together, with their little bot beside them.

OpenBank Labs

The kernel behind
better banks.

Shared banking logic, built once and tested across the platform. From money and calendars to credit math and payment messages.

Step inside Labs →

OpenBank Labs illustration: a lioness scientist and bot beside the shared banking kernel.

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 PLATFORM

Go behind the screen. ↗

Explore the domains, services and contracts that make it work.

03 / THE AGENTS

Meet 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.

Bank as Code

The bank explains itself.

A running service exposes its own API contract, version and health. Its documentation travels with its release, so teams can inspect what is deployed and trace it back to the code.

See docs-as-service in the source →

01 / SERVICESelf-describing services

Live endpoints report the deployed version, API contract and health.

02 / DOCUMENTATIONDocumentation as Code

Service-owned docs ship with the release; generated decisions and runbooks are checked for drift.

03 / GOVERNANCECompliance as Code

Each service declares ownership, lineage and retention. CI cross-checks claims that the code can verify.

04 / EVIDENCEReady to examine

Link a change to its contract, tests and operational signals, giving reviewers a path from a claim to its evidence.

The public catalog is a code-derived snapshot, not a live deployment report. Running-service endpoints and operational views show current state.

01 / INSIDE THE BANK

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 RELATIONSHIP

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

03 / PRODUCT STUDIO

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

04 / AI-NATIVE · MCP-NATIVE

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.

Actual OpenBank app screenshot: CZK account with three currencies, Send, Request, Cards, Savings, payday forecast and the bot assistant. — Actual app screenshot · sandbox data
The app evolves; this is a recorded view.

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 is from the app itself, with its real controls and visual language.

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.

Accounts & ledger ↗ Payments & settlement ↗ Identity & onboarding ↗ Cards & disputes ↗ Lending & credit risk ↗ Treasury & wealth ↗ Financial crime & audit ↗ Regulatory reporting ↗ Customer engagement ↗ Open banking ↗ Products & pricing ↗ Operations & AI ↗

Explore every area and module →

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 agent control room ↗ Read the charters ↗

The OpenBank agent crew, the same original robot illustration used in the admin portal. — Original OpenBank agent artwork · roles and permissions live in code.

Open the actual product

See the work.
Follow the evidence.

Actual OpenBank admin interface: Agent Control Room, agent collaboration and links to reviewed roles. — Admin portal capture supplied in the OpenBank presentation. Recorded demonstration view; not a live status feed.

Governance & evidence ↗ FinOps ↗ Continuity ↗ Architecture ↗

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.

Start contributing ↗ Let’s talk →

The Open Bank Foundation remains a proposal, not an incorporated organization.

Share the common core. Keep your customer experience your own.

A bank you can look inside.

The kernel behindbetter banks.

One open core.A whole bank to explore.

Banking, in your hands. ↗

Go behind the screen. ↗

Meet the crew. ↗

One bank.Every connection counts.

The bank explains itself.

From a customer needto the whole bank.

See the person.Understand the context.

Ideas becomereal products.

Banking context,ready for AI.

Your money.Your way in.