Practical overview
When it fits
Use Hub when a Lightning wallet or node needs to be controlled by NWC-compatible applications, or when a self-hosted desktop, web or Docker-based control layer is needed.
Who it is for
- Bitcoin and Lightning users managing a self-hosted node or wallet
- Nostr application users who need an NWC-connected Lightning backend
- Developers building or testing Lightning services with documented local and Docker workflows
Documented uses
- Connect Damus, Amethyst or another NWC-compatible application to a Lightning node or wallet
- Operate a desktop Lightning control application on macOS, Windows or Linux
- Run the HTTP mode through Docker or a supported Linux or Mac environment
- Configure embedded or external Lightning backends
Requirements & limits
The repository is public and identifies the project as Apache-2.0 licensed. Documented platforms include macOS, Windows, Linux, Docker and web mode.
- NWC compatibility is required for connected applications to control Hub.
- The default Lightning backend is embedded LDK; LND, Phoenixd, Cashu and CLN are also listed as supported external backends.
- Desktop and HTTP modes have different documented platform paths.
- An always-online machine is described for connections to a Lightning address and receipt of online payments.
- Development requires Go, Node, npm and Yarn; Wails and platform-specific dependencies are needed for Wails development.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Hub for local HTTP development
Prepare and launch the HTTP mode locally from the repository.
Before you start
- Go, Node, npm and Yarn
- A copied .env configuration file
- Frontend files available for embedding
- A Lightning Polar setup with two LND nodes for the documented server setup
Steps
Copy .env.example to .env and edit the configuration.
Create a Lightning Polar setup with two LND nodes and enable the Polar LND section in .env.
Compile the frontend, or create frontend/dist/tmp so embeddable files are available.
Build the HTTP binary, place it with .env in a temporary directory, and run the binary.
Expected outcome
A locally launched HTTP-mode Hub process using the repository's documented setup path.
Guide limitations
- The instructions describe development and local execution, not a production deployment.
- The Polar LND setup is part of the documented server-development procedure.
- No successful execution or compatibility result is established by these instructions.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 3 October 2026
- Original website title
- getAlby/hub · Official homepage title · retained in its source language

