Breez

• Name: Breez
• URL: https://breez.technology/
• Category: Bitcoin payments-infrastructure company / embedded-wallet and SDK operator / app-embedded Lightning-and-stable-balance control-plane vendor
• Tags: bitcoin-ecosystem
• Summary: Breez belongs in companies/ because the practical control surface is not just an SDK for adding bitcoin. The company operates the app-facing packaging around passkey onboarding, sync, liquidity and swap paths, API-key issuance, reference-app distribution, and signer / partner composition. The useful question is who chooses what developers and downstream end users inherit by default when they embed Breez’s stack into wallets, neobanks, remittance apps, and consumer apps. That authority sits with the Breez operator boundary more cleanly than with a neutral protocol label.
• What it does:
  • Operates the Breez SDK family for adding non-custodial Bitcoin and stablecoin flows to third-party apps and services
  • Packages multiple implementation paths including Breez SDK - Spark and Breez SDK - Liquid, while explicitly steering new builders toward Spark and existing Liquid partners toward migration
  • Provides app-facing features such as passkey login, multi-device and multi-app sync, stable-balance UX, contacts, integrated on-ramps, and optional external-signer paths including Turnkey integration
  • Requires API-key issuance and maintains the hosted coordination surfaces around onboarding, support, and production access for downstream integrators
  • Publishes Glow as a reference app and white-labelable showcase so partners can fork, rebrand, and ship Breez-shaped wallet UX instead of starting from a neutral baseline
  • Maintains public repositories and documentation that shape how developers adopt the stack across mobile, web, backend, and WebAssembly environments
• Key claims:
  • The homepage frames Breez as bringing bitcoin in every app and repeatedly sells value transfer as an embeddable product feature rather than a standalone wallet brand
  • The SDK landing page says Breez is the simplest way to add instant, non-custodial bitcoin and stablecoins to any app or service, which is analytically useful because it centers the company as the packaging and distribution layer
  • The Spark docs describe an end-to-end solution with passkey login, stable balance, sync service, automatic claims, external signers, Turnkey integration, and a required API key; that means the real operator surface is broader than a code library alone
  • The Liquid docs explicitly tell new partners to build with Spark and recommend that existing Liquid partners migrate ASAP, which is a clear example of company-level steering over which rail and product path downstream teams inherit
  • The Glow page describes a reference app that developers can explore, fork, white-label, and ship, which means Breez can shape downstream wallet UX and defaults indirectly through reference distribution as well as through APIs and SDKs
  • The public GitHub organization reinforces that Breez is not only a consumer app surface: the source-of-truth stack includes Spark SDK, Liquid SDK, Glow, and related developer materials for partner integration
• Whitepaper: No canonical standalone company whitepaper surfaced in this pass. The strongest primary materials were Breez’s homepage, SDK landing page, Spark docs, Liquid docs, Glow page, and the public GitHub organization; the broader source bundle remains ../whitepapers/breez-primary-sources-2026-04-25.md.
• Sources:
  • https://breez.technology/
  • https://breez.technology/sdk/
  • https://breez.technology/glow/
  • https://breez.technology/case-studies/
  • https://sdk-doc-spark.breez.technology/
  • https://sdk-doc-liquid.breez.technology/
  • https://github.com/breez

Internal linkages

• Keep the project / company split explicit: breez is the product-family note for the SDK surface, while this note is the operator / entity boundary.
• Closest comparison set: acinq, lightspark, and turnkey.
• Useful downstream/control-surface comparison: phoenixd for API-first Lightning server packaging and lightning-dev-kit for a less vertically integrated app-embedded Bitcoin stack.

Protocol / company boundary

• The Breez SDK is a real product surface, so projects/breez.md still does useful work.
• But the operator questions do not end at SDK features: Breez decides which implementation path is recommended, what migration path partners follow, how passkey and sync workflow behave, what hosted or gated surfaces sit behind API-key issuance, and how reference-app UX gets normalized for downstream teams.
• That is why Breez also deserves a company note. The practical control question is who packages the integration surface and steers the app-facing defaults around Bitcoin and stablecoin flows, not only which underlying rail the SDK touches.

Control surface

• Practical leverage sits in API-key issuance, docs and migration guidance, Spark-versus-Liquid steering, passkey and sync workflow, external-signer composition, on-ramp and liquidity partner selection, reference-app distribution, and the app-facing defaults developers inherit.

• Even when end users hold keys, many important choices can remain company-shaped: how onboarding works, which assets and rails get first-class treatment, how balances sync across apps and devices, what support and recovery paths exist, and what UX downstream teams copy from Glow.

• Treat Breez as an operator-managed wallet-and-payments packaging layer, not merely as a neutral SDK drop-in.

• Last reviewed: 2026-08-05 UTC