Galoy

• Name: Galoy
• URL: https://galoy.io/
• Category: Bitcoin-native banking infrastructure company / ledger-and-payments operator / institutional Bitcoin middleware
• Tags: bitcoin-ecosystem
• Summary: Galoy belongs as an entity note, not a protocol note. The useful question is who operates the bank-side Bitcoin stack that packages ledgering, transaction policy, wallet surfaces, and compliance integration into one company-run workflow. The practical leverage sits in Cala ledger design, Bria transaction control, Blink-facing product defaults, and the sidecar integration boundary that lets institutions add Bitcoin services without replacing the rest of their operating stack.
• What it does:
  • Sells modular banking infrastructure for institutions that want Bitcoin payments, custody-linked wallets, lending, exchange, or stablecoin-adjacent products without replacing the incumbent core system
  • Maintains Cala, a double-entry ledger system for complex financial records, transaction templates, multi-currency accounting, and API-driven banking workflows
  • Maintains Bria, a bitcoin payments hub focused on transaction batching, UTXO management, remote signing, and event-driven integration for distributed systems
  • Operates and packages Blink as the wallet, API, and merchant-facing surface for Bitcoin and Lightning payments, including hosted GraphQL access and self-host paths
  • Positions the full stack as compliance- and custodian-aware infrastructure that can sit beside existing bank systems rather than forcing a rip-and-replace migration
• Key claims:
  • The official site describes Galoy as building Bitcoin-native core banking infrastructure for regulated financial institutions and explicitly sells lending, payments, stablecoins, exchange, and wallet capabilities as one modular platform
  • The solutions and payments materials emphasize sidecar deployment next to incumbent bank cores and compliance systems, which is exactly why the company boundary matters more than a nominal product label
  • The GitHub organization ties the business story to real operating components such as Blink, Bria, and Cala rather than to a single marketing shell
  • Blink docs explicitly say the product is built on Galoy’s open-source bitcoin banking stack, making the wallet surface subordinate to a broader company-run banking architecture
  • The Bria and Cala repositories show production-oriented transaction batching, UTXO management, remote signing, event streaming, strong-consistency ledgering, and accounting primitives rather than a thin front-end product
• Whitepaper: No classic standalone company whitepaper is the key artifact here. The strongest primary materials remain the official site, solutions and use-case pages, Blink developer docs, the public GitHub organization, and the earlier source snapshot in ../whitepapers/galoy-primary-sources-2026-04-25.md.
• Sources:
  • https://galoy.io/
  • https://galoy.io/about
  • https://galoy.io/solutions
  • https://galoy.io/use-cases/bitcoin-payments
  • https://github.com/GaloyMoney
  • https://dev.blink.sv/
  • https://raw.githubusercontent.com/GaloyMoney/blink/main/README.md
  • https://raw.githubusercontent.com/GaloyMoney/bria/main/README.md
  • https://raw.githubusercontent.com/GaloyMoney/cala/main/README.md

Internal linkages

• Project-layer alias: galoy.
• Product surface that makes the stack concrete: blink.
• Merchant-stack contrast when the operator wants invoices and stores without Galoy’s broader bank-side middleware: btcpay-server.
• Useful adjacent operator reads: lightspark and coinbase.

Protocol / company boundary

• There is not a very useful standalone Galoy protocol boundary doing most of the analytical work.
• The components that matter — Blink, Bria, Cala, hosted APIs, and the bank-integration workflow — are packaged and operated as a company-run stack rather than as a neutral network with meaningfully independent governance.
• That is why this note belongs in companies/: the important questions are who controls ledger policy, transaction construction, wallet defaults, customer integration paths, and the compliance-aware operating shell wrapped around Bitcoin and Lightning services.

Control surface

• Practical authority sits in ledger configuration, account-policy design, transaction batching and UTXO policy through Bria, hosted API admission, Blink-facing wallet and merchant defaults, and the compliance and custody integration boundary offered to institutions.

• Even where parts of the stack are open source or self-hostable, Galoy still matters as the named operator and integrator that decides how the canonical packaged workflow is documented, supported, and sold.

• Read Galoy as a company-run Bitcoin banking control plane, not as a protocol and not as just another wallet brand.

• Last reviewed: 2026-08-05 UTC