We build our banking infrastructure in the open: open-source libraries and source-available platforms. Read the code, audit the design, and see how we work.
Banks adopt infrastructure they can trust. Publishing our code lets a prospective customer's engineers see exactly how money moves and how balances reconcile before they sign anything. It is also how good infrastructure earns its place: out in the open, where anyone can check the work.
Every line that handles a balance is open to inspection.
Reusable Rust libraries, not a black box.
The same code that ran a Bitcoin wallet for millions.
Two models, both public. Our libraries are released under standard open-source licenses (Apache 2.0, MPL 2.0, MIT), and you can use them freely. Our product platforms, including Lana, are source-available under the Business Source License (BSL 1.1): read, modify, and run them for non-production use today, and each release converts to Apache 2.0 four years after it ships. Production use is licensed commercially.
The products and services financial institutions deploy. The license chip on each card shows the exact terms.
A Bitcoin-backed lending platform that runs the full loan lifecycle, from origination through real-time loan-to-value monitoring, margin calls, and liquidation. Double-entry accounting and institutional governance controls are built in.
Wallet infrastructure for services that move on-chain Bitcoin at scale. It handles UTXO management, transaction batching, fee estimation, and signing behind a clean API, and serves as the payments backbone of the stack.
A double-entry accounting ledger built for high-throughput financial applications. Strongly typed and SQL-backed, it is designed so balances always reconcile, which makes it the bookkeeping core beneath lending and payments.
Lower-level Rust libraries we extracted from production and maintain as standalone open source.
A framework for persisting event-sourced entities in PostgreSQL. Brings event sourcing to a familiar relational database without giving up SQL queries or transactional guarantees.
A durable background job runner backed by PostgreSQL. It schedules and retries asynchronous work like settlement, monitoring, and reporting, with the same transactional safety as the rest of the system.
Outbox and inbox patterns implemented in Rust. It makes message passing between services reliable and exactly-once, solving a problem that every event-driven system eventually runs into.
Projects that established our track record running real Bitcoin and Lightning systems in production.
The Lightning-native Bitcoin wallet Galoy built and scaled to hundreds of thousands of users, including a country-wide deployment. Much of the infrastructure on this page was proven here first.
Keeps a Bitcoin balance stable in dollar terms using a derivatives hedging strategy settled over Lightning. A self-contained engine for dollar-denominated accounts on a Bitcoin rail.
A library implementing proof-of-liabilities, so a custodian can prove what it owes its customers without exposing individual balances. Transparency primitives for Bitcoin custody.
If you are looking at these repos before a conversation with us, here is what they show about how we build:
We are a remote-first team of builders developing banking software for the Bitcoin Age. The code on this page is what we actually run. Read it, audit it, and build on the open-source pieces. If you like what you read, we would like to hear from you.
Forty-plus repositories, from production platforms to the small libraries that hold them together.