Alby

• Name: Alby
• URL: https://getalby.com/
• Category: Bitcoin Lightning wallet infrastructure / wallet-connectivity ecosystem / self-custodial node control plane / developer payments tooling
• Tags: bitcoin-ecosystem nostr-ecosystem
• Summary: Alby is the main Bitcoin wallet-connectivity stack here, not just a browser wallet. Its product surface spans Alby Hub, browser and mobile clients, Nostr Wallet Connect, Bitcoin Connect, WebLN tooling, and developer SDKs. What matters here is app-to-wallet session control and permissioning: Alby sits in the layer that decides how outside apps reach a wallet and what they are allowed to do once connected. Keep this note on that reusable product surface; the named operator boundary around Alby Account, Alby Cloud, OAuth, webhooks, relay policy, and support now lives in alby.
• What it does:
  • Operates Alby Hub, a self-custodial Lightning wallet and node-control surface that can run self-hosted or via Alby Cloud and stay online for wallet-linked receiving flows
  • Lets users connect web, desktop, and mobile apps to their wallet while keeping control over keys, with configurable app permissions and recurring budget limits
  • Provides a browser extension for Lightning, Nostr, Liquid, and onchain interactions plus a separate Alby Go mobile wallet experience
  • Exposes developer tooling including a developer guide, sandbox, NWC Wallet API, Lightning Tools, Bitcoin Connect, JavaScript SDKs, and open-source repos for wallet and app integration
  • Participates heavily in the Nostr Wallet Connect ecosystem, which the companion protocol site frames as an open protocol for connecting Lightning wallets to apps
  • Publishes open-source software for Hub, browser extension, SDKs, Bitcoin Connect, agent skills, and other wallet/payment components
• Key claims:
  • The official homepage positions Alby as “all you need to use bitcoin as everyday money online, in apps and in person,” explicitly spanning both consumer and developer use cases
  • The homepage and Hub README jointly emphasize that Alby Hub is self-custodial and can be run in the cloud or self-hosted while remaining connectable to external apps
  • The developer guide shows that Alby is not just a wallet UI: it offers sandboxed testing, browser APIs, wallet APIs, Lightning tooling, and agent-oriented skills for building Bitcoin payment flows
  • The public GitHub organization frames Alby around multiple interoperable products—Hub, browser extension, Bitcoin Connect, SDKs, Alby Go, and agent skills—rather than a single wallet app
  • The NWC site describes Nostr Wallet Connect as an open protocol for connecting Lightning wallets to apps, which helps explain why Alby should be cataloged as connectivity infrastructure and not merely as a branded wallet front end
  • Across the homepage, docs, and repos, Alby repeatedly leans on open protocols and interoperability language, especially around WebLN, NWC, and app-connected wallet flows
• Whitepaper: No canonical Alby whitepaper or litepaper surfaced in this pass. The clearest current sources of truth are the official site, developer guide, public GitHub organization, Alby Hub README, and companion NWC protocol materials; see ../whitepapers/alby-primary-sources-2026-04-28.md.
• Sources:
  • https://getalby.com/
  • https://guides.getalby.com/developer-guide/
  • https://github.com/getAlby
  • https://raw.githubusercontent.com/getAlby/hub/master/README.md
  • https://nwc.dev/

Internal linkages

• Company / operator boundary for account auth, cloud hosting, OAuth, webhook, relay, and support workflow: alby.
• Open wallet-connect rails Alby both uses and helps normalize: nostr-wallet-connect and webln.
• Strong app-facing comparison when the question is local wallet session control versus a self-custodial server wallet API: phoenixd.

Protocol / company boundary

• Keep this note on the product and protocol-adjacent stack: Alby Hub, the Browser Extension, Alby Go, NWC-heavy app connectivity, Bitcoin Connect, WebLN tooling, and the permission model exposed to outside apps.
• Use alby for the named-operator layer around Alby Account, Alby Cloud, OAuth client issuance, webhook delivery, relay policy, support workflow, and linked-dashboard visibility.
• That split matters because how does Alby make wallet sessions work? and which company operates the easiest hosted identity and developer shell around those sessions? are related but not identical questions.

Control surface

• The useful question is not whether Alby is a browser wallet, mobile wallet, or hub product.

• At the product layer it is who gets to open wallet sessions, what permissions and budgets they get, and whether the user can move the control plane back to self-hosted infrastructure without losing app connectivity.

• Account eligibility, cloud terms, OAuth admission, webhook delivery, relay rate limits, and dashboard visibility now point upward to alby because those are operator-boundary questions rather than pure protocol or wallet-design questions.

• That is why this note belongs in wallet-connectivity infrastructure, not in generic wallet-product sprawl.

• Last reviewed: 2026-08-07 UTC