Guide
Custodial vs non-custodial Lightning wallets
The single most important Lightning-wallet decision. Plain-language framing of what each means, when each is the right call, and the in-between options that now exist.
Affiliate disclosure. Some links on this page are partner links. LN Cash may earn a commission if you sign up. This does not change which tools we recommend — see our methodology and the full disclosure.
The first decision when picking a Lightning wallet is whether you want custodial (a provider holds your keys and therefore your sats) or non-custodial (your device holds the keys, and your sats live with them). Every other wallet feature is downstream of this.
What custodial means
A custodial Lightning wallet holds the keys to your sats on its servers. You log in, see a balance, send and receive — but the wallet provider is the entity that ultimately controls the funds. You are trusting them not to:
- Lose your sats (technical failure, hack)
- Restrict your access (regulatory pressure, account terms violation)
- Disappear (company shutdown, regional withdrawal)
The trade-off is convenience. Custodial wallets have the smoothest onboarding, the fastest send/receive UX, and the least liquidity headache. They can also be free, because the provider absorbs the operational cost of running Lightning infrastructure.
Typical custodial wallets: Wallet of Satoshi, historical Alby (deprecated as of 2024), Cash App’s Bitcoin features, Strike consumer app.
What non-custodial means
A non-custodial wallet holds the keys on your device. The wallet software handles the Lightning protocol details, but you, technically, control the sats. The provider cannot freeze, lose, or restrict your funds — because they don’t have them.
The trade-off is responsibility. You have to:
- Back up the recovery phrase (and test it)
- Understand at least a little of what’s happening (channels, liquidity, on-chain fees)
- Pay the operational cost of running Lightning yourself — usually in the form of channel-open or service fees
Typical non-custodial wallets: Phoenix, Breez, Alby Hub (including Alby Cloud, where the keys stay on your device even with hosted node), Zeus, Muun.
The middle path
A few products blur the line in interesting ways:
- Alby Cloud hosts Alby Hub for you, but the keys stay on your device. The Lightning node runs in Alby’s infrastructure; the signing happens in your wallet. This is “self-custodial with managed hosting.”
- Breez SDK Greenlight runs a Core Lightning node in the cloud on the user’s behalf, with keys remaining on the user’s device. Similar shape: cloud node, local keys.
- Phoenix is fully self-custodial, but uses ACINQ’s Lightning Service Provider for inbound liquidity. The keys are yours; the LSP is on the path.
These are all genuinely non-custodial. The “service in the loop” pattern reduces operational burden without re-introducing custody.
When custodial is fine
- Small balances (tip jar amounts).
- Validating that Lightning works for your use case before committing to operational overhead.
- A creator’s first Lightning Address while they decide whether they care about the protocol.
- An app or service where the company explicitly wants the convenience and is sized to absorb the trust cost.
When non-custodial is required
- Any amount you’d be upset to lose to a provider shutdown or restriction.
- A merchant taking ongoing customer payments — you don’t want a third party able to pause your business.
- A creator with non-trivial regular tip volume.
- Anyone in a jurisdiction where custodial wallet availability has historically been unstable.
- Anyone who agrees with the “not your keys, not your coins” axiom of Bitcoin culture.
Recommended setup paths
- Creator, casual receiver, non-US: start with Wallet of Satoshi. Move to Phoenix or Alby once tips become regular.
- Creator, self-custody from day one: Alby Cloud for managed hosting, or Phoenix for pure-mobile.
- Merchant: skip personal wallets entirely. Use BTCPay Server or a hosted processor — see the processor comparison.
- Developer: Breez SDK for embedded self-custodial Lightning in apps; Alby for web-side.
Next step
- Lightning Address explained — the address layer is wallet-agnostic.
- Best self-custodial Lightning wallet — ranked picks.
- Best Lightning wallet for beginners — easier-first picks.
FAQ
Is a non-custodial wallet always better? +
Not always. For small amounts where convenience matters more than sovereignty, custodial is fine — you're trusting the provider the same way you trust a bank or a payment app. For amounts you'd be upset to lose, non-custodial is the right answer. The line is judgmental, not objective.
What if my non-custodial wallet provider disappears? +
Your funds are still recoverable as long as you have the seed phrase (and, for Lightning, can force-close channels on-chain to retrieve funds). This is exactly the case where non-custodial wallets prove their value. Custodial wallets in the same scenario can lose access entirely if the provider has retention issues.
Can I switch from custodial to non-custodial later? +
Yes. Common path: start custodial (Wallet of Satoshi or Alby Cloud) to validate Lightning works for your use case; migrate to a self-custodial wallet (Phoenix, Alby Hub, Breez) once balances or volume grow.