Lightning Network & Layer 2

Alby Wallet Review: Lightning for the Browser

A dark-screen laptop with blank keycaps sits in front of a small networked personal server on a grey desk.

Alby Wallet bridges the gap between Lightning Network payments and the web browser — a connection that no other wallet handles as seamlessly. Starting as a browser extension for one-click Lightning payments, Alby has evolved into Alby Hub: a self-custodial Lightning node that connects to web applications through Nostr Wallet Connect (NWC). If you use Nostr, tip content creators, or want to pay for web services with bitcoin, Alby is the wallet designed specifically for that workflow.

This review covers Alby Hub’s architecture, its NWC integration, deployment options, fee structure, and how it compares to mobile-first Lightning wallets in 2026.

Alby Hub Specifications

SpecificationDetail
DeveloperAlby Inc.
Lightning BackendLDK (default), also supports LND, Core Lightning (CLN), Phoenixd, Cashu
Custody ModelSelf-custodial (the experimental Cashu backend is custodial: a mint holds your bitcoin)
PlatformsDesktop app (Windows, macOS, Linux), home servers (Umbrel, Start9), rented cloud servers
Browser ExtensionChrome, Firefox, Edge, Brave
NWC SupportFull Nostr Wallet Connect (NIP-47)
Channel ManagementLSP-assisted or manual
Mobile AccessAlby Go app (iOS, Android) or other NWC apps
Invoice SupportBOLT 11, BOLT 12 offers (receive only, beta; LDK and CLN backends), LNURL, Lightning Addresses, Keysend
BackupBuilt-in LDK node: 12-word recovery phrase + channel backup; other backends are backed up their own way
LicenseOpen source

From Extension to Hub: Alby’s Evolution

Alby started in 2021 as a browser extension that let users pay Lightning invoices on websites with a single click — similar to how a password manager auto-fills login forms, Alby auto-fills Lightning payments. The extension connected to external Lightning backends (your own node, LNbits, or Alby’s custodial wallet service).

In 2024-2025, Alby phased out its custodial shared wallet and launched Alby Hub — a self-custodial LDK-based Lightning node that users can run on their own hardware, on a cloud server, or, at the time, on Alby’s own hosted service, Alby Cloud. The browser extension still exists, and Alby now recommends pairing it with your own Alby Hub, though it can still connect to other wallets and nodes, such as LND, Core Lightning or LNbits. Alby Go, Alby’s phone app, connects to your Hub through NWC and works with other NWC wallets too.

This transition moved Alby from a custodial convenience layer to genuine self-custody — a significant philosophical and technical shift.

Before: by default, the Alby browser extension used Alby's shared wallet, where Alby held the keys and your balance; that service ended on 4 January 2025. Now: the browser extension, Alby Go on your phone and Nostr apps all connect through NWC to your own Alby Hub, a Lightning node where you hold the keys. Apps can only send it requests.
From an account at Alby to a node of your own. Alby’s shared wallet was custodial and closed on 4 January 2025. Alby Hub keeps the keys on your node, and every app, including Alby’s own, connects to it through NWC.

Nostr Wallet Connect (NWC): The Killer Feature

Alby’s most significant contribution to the Lightning ecosystem is Nostr Wallet Connect (NWC), an open protocol written up as NIP-47 in the Nostr specifications. NWC lets an application ask your wallet for payments through the Nostr protocol; the app never holds your keys or your funds.

Here is how it works in practice:

  1. You run Alby Hub (your Lightning node)
  2. You create an NWC connection for a specific app (e.g., a Nostr client like Damus)
  3. You choose what the app may do: by default it gets full access, including your balance and payment history, and a monthly budget you can change or switch off
  4. When you want to zap a post on Nostr, the app sends a payment request to your Alby Hub via NWC
  5. If the payment fits the budget, your Alby Hub pays it from your self-custodial balance without asking you
How Nostr Wallet Connect works. Once: your Alby Hub creates a connection for one app, with a secret for that app (not your keys) and a budget, for example 10,000 sats a month; you scan its QR code or paste it into the app. Each payment: the app sends an encrypted request, say pay 3,000 sats, to a Nostr relay, which passes it on but can't read it. Your Hub checks the budget and, if the payment fits, pays it over the Lightning network. The budget now has 3,000 sats spent and 7,000 left; a request for more than what's left is refused, and deleting the connection makes its secret stop working.
An app connected through NWC can ask, but only your Hub can pay. Each app gets its own secret, never your keys, and by default a monthly budget. Whoever holds that secret can spend up to the budget without asking you, so keep it private. Its requests travel encrypted through a Nostr relay, by default one run by Alby, and your Hub refuses anything over the budget.

The breakthrough: every connected app pays from the same wallet without a wallet app running on each device, as long as your Hub is online. NWC works across platforms — web apps can connect to your hub, mobile apps can connect to your hub, even other desktop applications. The one-click wallet connection flow makes linking a new app as simple as a QR code scan.

NWC has been adopted beyond Alby itself. Other wallets and services now implement the protocol, creating an open standard for wallet-app communication.

Deployment Options

Self-Hosted on Your Hardware

Run Alby Hub on your own computer with the desktop app (Windows, macOS or Linux), or on a home server (Alby describes its Raspberry Pi install as experimental). Full sovereignty — you control the hardware, the node, and the network connection. The machine must stay on and online for your Hub to receive payments, and a server install needs basic Linux administration skills.

Self-Hosted on a VPS

Deploy Alby Hub on a cloud VPS (a virtual private server you rent by the month). Alby’s site has install guides for providers such as DigitalOcean, which has a one-click install, and Hetzner. You hold the keys and control the software, but the hosting company runs the machine your keys live on, and you pay it every month. A middle ground between convenience and sovereignty.

Alby Hub can also run on existing node platforms like Umbrel and Start9 as an application, integrating with your broader Bitcoin node setup.

Three places to run Alby Hub. Your own computer, with the desktop app for Windows, macOS or Linux: you run the machine, and the Hub can receive only while the computer is on. A home server such as Umbrel, Start9 or another small always-on computer: you run the machine and it is online all the time. A rented cloud server, set up with Alby's install guides for DigitalOcean, Hetzner and other providers: the hosting company runs the machine your keys live on, it is online all the time, and it comes with a monthly bill. You hold the keys in all three.
Your Hub can receive only while it is online. A computer that sleeps misses payments, so an always-on home server or a rented server suits it better. On a rented server the keys are still yours, but the hosting company runs the machine they live on.

Alby Cloud

Alby Cloud was the easiest option: Alby ran your Hub on its own servers for a monthly fee; the keys were yours, but they lived on a machine Alby ran. As of November 2026 it no longer appears among the plans on Alby’s pricing page, which lists the free Hub and an optional Pro subscription, and the cloud option on Alby’s site is a set of install guides, some with a one-click button, for a server you rent. Alby’s guides still explain how to move an existing hosted Hub to your own machine.

Fee Structure

  • Alby Hub software: Free and open source
  • Alby Pro (optional): $3.90 a month as of November 2026, for extras such as a custom Lightning address and encrypted remote backups that restore your channels without closing them, once Dynamic Channels Backup is on in Settings → Backup
  • Lightning payments: Standard network routing fees only — no Alby markup on transactions
  • Channel management: On-chain fees for opening/closing channels. LSP fees if using managed liquidity
  • Browser extension: Free

The only thing Alby itself charges for is the optional Pro subscription. On your own hardware nothing else recurs beyond network fees; a rented server adds its provider’s monthly bill.

The Browser Extension Experience

Alby’s browser extension remains its most visible product. Once installed and connected to your Alby Hub, it enables:

  • One-click payments on any website that supports Lightning (LNURL, Lightning Address, or BOLT 11 invoices)
  • Nostr zaps — tip posts directly from your feed with a single click
  • Website authentication — log into services using Lightning (LNURL-auth)
  • Budget controls — set a spending budget for each website, so a site can’t spend beyond it without asking you first

The extension is available for Chrome, Firefox, Edge, and Brave. Websites talk to it through WebLN, a standard way for a web page to ask your Lightning wallet to pay.

Paying a website with the Alby extension. The website asks for a payment through WebLN. The extension, in your browser, checks it and passes it on through NWC to your Alby Hub (directly, or by way of your Alby account, which your Hub also connects to through NWC), and your Hub pays the site's wallet over Lightning. If you have set no budget for that site, the extension shows you the payment and waits for your OK. If the payment fits the budget you set for that site, the first time you paid it, it goes through in one click, with no pop-up to confirm.
The extension stands between a website and your Hub. By default it asks you to confirm every payment. Give a site a budget and its payments go through in one click while they fit. The extension reaches your Hub through NWC, directly or by way of your Alby account.

Pros and Cons

Pros

  • Best browser-native Lightning payment experience — nothing else comes close for web payments
  • Nostr Wallet Connect (NWC) enables seamless app-wallet communication across platforms
  • Multiple deployment options, from a one-click cloud install to fully self-hosted
  • Multiple Lightning backend support (LDK, LND, CLN, Phoenixd, Cashu)
  • Per-app budgets and permissions let you cap what each connected app can spend and see
  • Open source
  • Contributed NWC as an open standard benefiting the broader ecosystem

Cons

  • No Lightning node on your phone — Alby Go, Alby’s mobile app, is a remote control for your Hub through NWC
  • Installing it on a server takes some Linux skills; the desktop app does not
  • Your Hub must stay online to receive payments, so you need an always-on machine or a rented server with a monthly bill
  • LDK-based node is less mature than LND or CLN for advanced routing scenarios
  • Initial channel setup requires opening at least one channel (manually or via LSP)
  • Primarily optimized for small to medium payments — not designed for large-value Lightning transactions

Alby vs Other Lightning Wallets

FeatureAlby HubPhoenixZeus
Primary platformWeb/DesktopMobileMobile
Browser extensionYes (best in class)NoNo
NWC supportFull (NWC pioneer)NoYes (NWC service)
Nostr integrationDeep (zaps, auth, profiles)NoYes (via NWC)
Mobile experienceAlby Go app, a remote for your HubExcellentExcellent
Channel managementManual or LSPAutomated (splicing)Manual or LSP
Self-hostingSupportedN/AEmbedded node
Best forWeb payments, NostrEveryday mobileNode operators

Verdict

Alby is not trying to be the best mobile Lightning wallet. It is the best Lightning wallet for the web. If your Lightning usage centers on Nostr interactions, tipping content creators, paying for web services, or building applications that integrate Lightning payments — Alby Hub with the browser extension provides a workflow that no mobile wallet can replicate.

The NWC protocol is Alby’s lasting contribution. By creating an open standard for wallet-app communication, Alby has made Lightning wallets composable — any app can request payments from any NWC-compatible wallet, creating a pluggable payment layer for the internet.

For daily mobile spending, Phoenix remains the better choice. For running your own node from a phone, Zeus excels. But for connecting Lightning to the web ecosystem — Alby is unmatched.

Frequently Asked Questions

Is Alby Wallet custodial or non-custodial?

With its built-in node, the default, Alby Hub is self-custodial: your keys are generated and stored on the machine that runs it. If that machine is a server you rent, the hosting company runs it, so you also trust it with the machine your keys live on. If you connect Hub to your own LND, Core Lightning or Phoenixd node instead, the keys stay on that node; the experimental Cashu backend is custodial, because a mint holds your bitcoin. Alby’s former custodial shared wallet closed on 4 January 2025.

Do I need a Nostr account to use Alby?

No. Alby Hub functions as a standard Lightning wallet without any Nostr involvement. However, the browser extension and NWC features are specifically designed to integrate with Nostr, so the best Alby experience includes Nostr usage.

Can I use Alby on my phone?

Yes, with Alby Go, Alby’s app for iOS and Android. It is a remote control: it connects to your Alby Hub through NWC, and the payments come from your Hub, which must be online. Other NWC-compatible apps, such as some Nostr clients, work the same way.

What happens if Alby the company shuts down?

If you self-host your Alby Hub, it keeps running: the software is open source and runs on your machine. Some of its defaults use Alby’s services, such as the Nostr relay that carries your app connections, the server it reads the blockchain from and, if you connected an Alby account, your Alby Lightning address and the copy of your channel backup. You would switch to another relay and blockchain server, give each app a new connection link, because the old links name Alby’s relay, and keep copies of the backup file your Hub saves on its own disk. If your Hub uses Alby Pro’s remote backups, it keeps its node data on Alby’s servers rather than on your disk, so it would not run without Alby, and you would recover with your 12 words and that file. With the built-in node, your 12 words recover your on-chain balance in Alby Hub or another Bitcoin wallet; the money in your channels also needs the channel backup. The NWC protocol is an open standard and would continue to function independently of Alby the company.

If the machine running your Alby Hub dies, you need two things. Your 12 words, written once on paper or metal, bring back your on-chain balance in Alby Hub or another Bitcoin wallet. The channel backup, kept in your Alby account or in a file you copy after each new channel, brings back the money in your channels: each channel partner is asked to close its channel, and your share returns on-chain once it does, usually within 14 days; a partner that is offline must come back online first. With Alby Pro, at $3.90 a month, and Dynamic Channels Backup switched on before the machine died, the words and your Alby account bring back everything and the channels stay open.
Your 12 words alone don’t bring back the money in your channels. That also needs the channel backup. This is how Alby Hub’s built-in node works; the Pro price is as listed by Alby in November 2026.
Part of our free Bitcoin course: This topic is covered in depth in Lightning Wallets Compared from the Lightning Network & Bitcoin Nodes course.

Related Articles

Filed under: Lightning Network & Layer 2
← Back to All Articles