Cowrie Research

alby

5 min read

Alby Inc.

  • Name: Alby Inc.
  • URL: https://getalby.com/
  • Category: Bitcoin wallet-connectivity operator / self-custody cloud-hosting company / developer payments middleware company
  • Tags: bitcoin-ecosystem nostr-ecosystem
  • Summary: Alby clears the bar for a company note because the useful question is no longer only what wallet-connectivity stack exists? but which named operator runs the account system, cloud-hosted Hub path, OAuth client issuance, webhook dashboard, NWC relay, lightning-address identity shell, and support workflow around that stack? The product note remains useful for Alby Hub, browser-extension, NWC, Bitcoin Connect, and WebLN framing; this note is for the operating boundary that packages those pieces into a hosted account-and-developer surface.
  • What it does:
    • Operates the getalby.com account layer that links users’ self-custodial Alby Hub instances to lightning addresses, notifications, reports, browser-extension association, and dashboard visibility
    • Offers Alby Cloud as a first-party hosted environment for Alby Hub while keeping the product story centered on self-custody rather than pure custodial walleting
    • Runs developer-facing OAuth, API-client, token, and webhook infrastructure through getalby.com and api.getalby.com
    • Operates a professionally managed Nostr Wallet Connect relay and offers dedicated relay setup for partners that need stronger guarantees than the public unauthenticated relay path
    • Packages Lightning-channel distribution with third-party LSPs, while explicitly saying in the terms that Alby acts as a distributor rather than as the LSP itself
    • Maintains the legal, privacy, support, and service-eligibility perimeter around Alby Account, Alby Cloud, Alby API, the Browser Extension, Alby Hub, and Alby Go
  • Key claims:
    • The terms of service identify the operator as Alby Inc., incorporated in the USA with a registered office in Dover, Delaware, and explicitly enumerate Alby Account, Alby Cloud, Alby API, and lightning-channel distribution as services while listing the Browser Extension, Alby Hub, and Alby Go as products
    • The homepage markets self-custody in the cloud, app permissions, spending budgets, and direct browser access to Hub, which makes the company note useful because the first-party operating shell matters separately from the open-source wallet software
    • The Hub FAQ says linking an Alby Account makes that account the wallet interface for Alby Hub and adds lightning-address handling, notifications and reports, browser-extension association, developer APIs, and quicker support
    • The same FAQ says Alby cannot see transactions that go directly through the user’s node using NWC connections with Hub, but if the Alby Account is linked then transactions become visible on the dashboard at getalby.com; that is a clean statement of where the operator boundary reappears in a nominally self-custodial stack
    • The OAuth documentation shows developers create API clients on getalby.com and rely on Alby-operated authorization and token endpoints, which means Alby controls a real admission and credential-issuance layer rather than just publishing sample code
    • The webhook docs say developers create webhook endpoints in Alby’s dashboard and receive invoice events through Alby’s API infrastructure, including first-party handling of endpoint secrets and delivery workflow
    • The NWC relay docs say Alby offers a professionally operated relay specialized on NWC events, rate-limits the public relay, and will provision dedicated relay service for partners, which makes the company boundary useful for reasoning about reliability, metadata exposure, and admission policy
    • The privacy policy names Alby Inc. as controller for communication data, transaction data, and lightning-node authentication data, reinforcing that the entity boundary matters for observability, retention, and service-provider composition
  • Whitepaper: No classic Alby company whitepaper is the relevant artifact here. The strongest primary materials for this pass were the homepage, terms, privacy policy, Hub/account-linking FAQ, and the developer OAuth / webhook / NWC-relay docs collected in ../whitepapers/alby-company-primary-sources-2026-08-07.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep alby focused on the reusable product and protocol-adjacent stack: Alby Hub, the Browser Extension, Alby Go, NWC-heavy app connectivity, Bitcoin Connect, WebLN, and the app-permission model.
  • Keep this note focused on Alby Inc. as the operator that runs the account shell, cloud-hosted Hub path, OAuth and webhook infrastructure, relay policy, support path, and linked-dashboard visibility around that stack.
  • That split matters because how does Alby make wallet sessions and app permissions work? and which company controls the hosted identity, API, relay, and policy shell around those sessions? are related but not identical questions.

Control surface

  • Practical leverage sits in account eligibility, lightning-address issuance, Alby Cloud uptime and terms, OAuth client registration, webhook delivery, NWC relay rate limits, dashboard visibility when accounts are linked, and the choice to package channel-distribution and developer tooling into one first-party shell.

  • Alby is especially important because it offers a self-custody story while still controlling several of the easiest default hosted rails around identity, notifications, app connectivity, and developer integration.

  • Read Alby Inc. as the company-run operating shell around a broader wallet-connectivity stack, not as a neutral protocol primitive or just a browser-wallet publisher.

  • Last reviewed: 2026-08-07 UTC

Graph View

Backlinks