Voltage

• Name: Voltage
• URL: https://voltage.cloud/
• Category: hosted Bitcoin-and-Lightning infrastructure company / managed node operator / payments-operations platform company
• Tags: bitcoin-ecosystem
• Summary: Voltage belongs as an entity note, not a protocol note. The useful cut is the named company operating a hosted Bitcoin and Lightning control plane: node provisioning, team access, lifecycle APIs, payment and channel APIs, bundled admin tools, security and backup workflow, and default add-ons like tapd. The practical leverage is not the phrase global money infrastructure; it is that a vendor-run account boundary controls how businesses deploy nodes, expose APIs, manage credentials, and inherit Lightning-plus-Taproot-Assets operations.
• What it does:
  • Hosts Bitcoin and Lightning node infrastructure behind a company-run dashboard with organization and team access controls
  • Exposes a Voltage API for node lifecycle operations such as creating, starting, stopping, updating, and listing nodes owned by an organization
  • Separates company-side node-management APIs from node-side payment and channel APIs, making Voltage part of both the admin and transaction workflow
  • Bundles operator tooling such as Thunderhub, Lightning Terminal, LNBits, BTCPay Server, LNCLI connectivity, backups, and related integration guidance into the hosted platform
  • Automatically runs the Taproot Assets Daemon (tapd) on all customer nodes and exposes it through the same managed node environment
  • Markets a broader payments-and-infrastructure surface around Bitcoin and USD movement, compliance posture, uptime, and operational visibility for financial platforms
• Key claims:
  • Voltage’s homepage markets the company as global money infrastructure, says it gives financial platforms the tools to send Bitcoin and USD instantly and globally, and emphasizes enterprise uptime plus compliance posture rather than only hobbyist node hosting
  • The API Resources docs make the company boundary unusually explicit by separating the Voltage API for node operations from the Node API for sending payments and opening channels
  • The Voltage API docs say all dashboard functionality can be accomplished with the API and that users can create nodes for their own customers directly from their own sites, which shows Voltage acting as a hosted operator layer, not just a dashboard wrapper
  • The docs index shows a substantial operational surface including webhooks, backups, node security, sandbox guidance, and API examples across both admin and node interfaces
  • The Taproot Assets docs say all Voltage nodes automatically run tapd, which makes asset support another managed default inside the Voltage-operated environment rather than a separately self-run service
• Whitepaper: No classic whitepaper or litepaper is the key artifact here. The strongest primary materials are Voltage’s homepage, docs index, API Resources page, Voltage API docs, Taproot Assets docs, and adjacent node-security / webhook documentation; see ../whitepapers/voltage-primary-sources-2026-04-25.md for the earlier source capture.
• Sources:
  • https://voltage.cloud/
  • https://docs.voltage.cloud/llms.txt
  • https://docs.voltage.cloud/api-resources
  • https://docs.voltage.cloud/voltage-api
  • https://docs.voltage.cloud/taproot-assets
  • https://docs.voltage.cloud/webhooks
  • https://docs.voltage.cloud/node-security-and-backups

Internal linkages

• Project-layer alias: voltage.
• Strongest hosted-self-custody contrast: greenlight.
• Strongest self-hosted packaged-backend contrast: phoenixd.

Protocol / company boundary

• There is no especially useful standalone Voltage protocol doing the analytical work.
• The underlying protocol surfaces are Bitcoin, Lightning, LND, and Taproot Assets; Voltage is the named company packaging those components into a hosted operating shell with account objects, API keys, default tooling, and uptime promises.
• That is why this note belongs in companies/: the important questions are who controls node provisioning, team access, lifecycle APIs, payment-surface packaging, backup workflow, and which defaults customers inherit when they do not self-host.

Control surface

• Practical authority sits in organization and team access, API-key issuance, node lifecycle APIs, hosted endpoint exposure, bundled admin tooling, backup workflow, webhook truth, tapd as a default service, and any business dependency on Voltage uptime or policy.

• Customers still hold meaningful agency through their own node use, channels, and application-layer policy, but they inherit a live operator boundary whenever deployment, credentials, availability, and recovery sit inside Voltage’s managed environment.

• Read Voltage as a company-run hosted Lightning and Bitcoin operations control plane, not as a neutral protocol primitive.

• Last reviewed: 2026-08-06 UTC