Lightning Terminal

Lightning Terminal is a browser-based interface for managing inbound and outbound liquidity on the Lightning Network.

  • Crypto Currency
Lightning Terminal is a browser-based interface for managing inbound and outbound liquidity on the Lightning Network. It visualises your channels and balances, performs submarine swaps via the Lightning Loop service, and runs the loopd, poold, and faraday daemons in a single binary. Designed for self-hosted node operators, it also includes a Pool UI for earning a return on Lightning capital by opening channels to users who need inbound liquidity.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
100last commit 9 days ago
Popular
56596 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
71no serious findings, 4 minor, CI, tests, OpenSSF Scorecard 6.3/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
596
Open issues
192
Last commit
2026-11-11
Latest release
v0.17.11
License
MIT
Activity
declining

Checked 5 days ago - source: GitHub (lightninglabs/lightning-terminal)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the SDK before running examples Run pip install lightning-sdk first, because the docs use Python imports like Studio and Job from that package. Without it, your script will fail before it can start any Studio or job. source
  • Set your Lightning account variables Use export in your terminal to set LIGHTNING_USER_ID and LIGHTNING_API_KEY (your account ID and secret key) before running the SDK. If these are missing, cloud jobs cannot be launched or managed. source
  • Pick a cloud provider and machine type When starting a Studio, choose a cloud provider and machine, such as AWS and Machine.L4, in the code. This matters because it decides which cloud and GPU hardware your session will run on. source
  • Taproot Assets backup (critical) Uninstalling Lightning Terminal permanently erases all application data, including Taproot Assets and Bitcoin funds. Before uninstalling or re-installing, back up the application's .tapd data folder to prevent permanent loss of assets. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I authenticate to the Lightning Terminal web interface?

Run litd with a UI password of at least 8 characters. In production, store the password as an environment variable to keep it out of command history.

How can I avoid self-signed certificate warnings when accessing Lightning Terminal remotely?

Configure the HTTP server to use a Let's Encrypt certificate. The project documentation includes Let's Encrypt configuration instructions for remote access.

Can Lightning Terminal be connected to a remote lnd instance?

Yes, Lightning Terminal can be configured to use a remote lnd instance. The README points to a dedicated remote LND configuration guide.

What changes are needed when upgrading from very old Lightning Terminal versions?

For v0.1.1-alpha or earlier, create a lit.conf file in the LiT directory. The default location depends on the operating system, such as ~/.lit/lit.conf on Linux.

How can I control which application logs are shown?

The debug setting is a namespace filter that selects which portions of the app to display logs for. Current namespaces include main, action, and grpc.

Answers sourced from github.com, github.com

Community

Collected 49 days ago - public community threads