LNbits

• Name: LNbits
• URL: https://lnbits.com/
• Category: Lightning wallet/accounts middleware / modular bitcoin-payments platform / extension-based merchant and automation control plane
• Tags: bitcoin-ecosystem
• Summary: LNbits is the wallet/accounts middleware layer that sits above many Lightning backends and lets operators keep the higher-level app surface while swapping the funding rail underneath. The real thing here is per-wallet isolation, API keys, and extension-governed workflow policy; the wallet UI is incidental.
• What it does:
  • Provides a wallet/accounts layer on top of many Lightning or bitcoin payment backends, letting operators switch funding sources without changing the higher-level LNbits app surface
  • Creates isolated wallets and per-wallet API keys so apps and services do not need direct exposure to a node’s full balance
  • Exposes an HTTP API for payments, wallets, accounting, and extension-driven workflows used by merchants, kiosks, apps, and automation systems
  • Supports a large extension ecosystem that adds features like point-of-sale flows, online checkout, donation buttons, Nostr zaps, subscriptions, vouchers, and other application-specific payment logic
  • Offers both self-hosted deployment and a managed-hosting path (myLNbits) for operators who do not want to run their own infrastructure
  • Maintains a broad open-source footprint through the lnbits GitHub org, including the main server, extension repos, examples, point-of-sale tools, docs, and extension manifests
• Key claims:
  • The homepage calls LNbits “the world’s most powerful suite of bitcoin tools” and “a modular payments platform — a wallet, app store, and automation engine in one”
  • The main docs describe LNbits as a free and open-source Lightning wallet/accounts system that can serve as an account system, extension platform, API layer, LNURL fallback wallet, and instant demo wallet
  • The docs home emphasizes 60+ extensions, 20+ wallet backends, MIT licensing, and a full REST API, which strongly suggests control-plane infrastructure rather than a single end-user wallet app
  • The backend-wallet docs stress that operators can switch funding sources without changing extensions, apps, users, API keys, or deployment setup; supported backends include node software and third-party services such as LND, Core Lightning, Alby, Boltz, Breez, Spark, Strike, OpenNode, ZBD, and others
  • The extension-install docs show that LNbits treats extensions as installable manifest-driven packages with versioning, release metadata, dependency handling, and explicit trust warnings for admins
  • The main repo README positions LNbits as a lightweight Python server on top of a Lightning funding source with isolated wallets, a clean API, and an extension system for rapidly shipping features without locking into a single node implementation
  • The docs repo describes itself as “Docs for Humans + Agents,” explicitly mentioning extension pages, LLM integration, llms.txt, and Skill-oriented material, which is an unusually strong signal that LNbits is evolving toward machine-readable and agent-friendly operational documentation
• Whitepaper: No canonical standalone LNbits whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site, docs, llms.txt, backend-wallet and extension docs, plus the open-source repo and docs repo; see ../whitepapers/lnbits-primary-sources-2026-04-29.md.
• Sources:
  • https://lnbits.com/
  • https://docs.lnbits.com/
  • https://docs.lnbits.com/llms.txt
  • https://docs.lnbits.org/guide/wallets.html
  • https://docs.lnbits.org/guide/extension-install.html
  • https://github.com/lnbits/lnbits
  • https://github.com/lnbits
  • https://github.com/lnbits/docs

Internal linkages

• Merchant/operator anchor when the stack wants a broader self-hosted payments shell: btcpay-server
• Wallet-connectivity anchor when app-session control matters more than backend abstraction: alby
• Self-custodial backend contrast when the question is app-facing daemon versus plugin marketplace: phoenixd

Control surface

• Authority sits in backend selection, admin approval of extensions and manifests, per-wallet API-key boundaries, and whether the deployment runs self-hosted or through myLNbits.

• Read it as accounts middleware with a plugin economy, not as a single wallet product.

• Last reviewed: 2026-06-06 UTC