Skip to main content
Utexo provides two node runtimes for different integration models: RGB Node for watch-only, on-chain RGB operations and RGB Lightning Node (RLN) for RGB-enabled Lightning channels and payments. An RLN can be self-hosted or operated through Utexo Cloud.
Utexo Cloud is a managed control plane for RGB Lightning Node instances. It is a deployment and operations model, not a separate node implementation.

Node types

RGB Node

RGB Node is a standalone REST service for applications that need on-chain RGB functionality without embedding the full RGB protocol stack. It manages watch-only wallets and never holds private keys. Clients identify a wallet with vanilla and colored xPubs plus the BIP32 master fingerprint. Operations that require a Bitcoin transaction use a begin/sign/end PSBT flow: the node constructs an unsigned PSBT, the client signs it, and the node finalizes the operation. RGB Node is best suited to operator-controlled backends such as exchange, settlement, and custody infrastructure. Wallet applications should normally integrate through the Utexo SDK.

RGB Lightning Node

RGB Lightning Node is an RGB-enabled Lightning daemon built on LDK. It combines Lightning peer and channel management with RGB asset issuance, on-chain transfers, invoices, and payments. Use RLN when an application needs channel-based RGB payments or direct control over Lightning node operations. The same node runtime can be deployed on infrastructure you manage or provisioned through Utexo Cloud.

RGB Lightning Node deployment models

Self-hosted

With a self-hosted RLN, your team installs and operates the node and its supporting infrastructure. You control the runtime configuration, authentication, data storage, network exposure, upgrades, and recovery procedures. This model provides the greatest infrastructure control but also places operational and security responsibility on the node operator.

Utexo Cloud

Utexo Cloud provides a managed control plane for provisioning and operating RLN instances. Applications can manage node lifecycle operations through the dashboard or Cloud API and connect to the running node API separately. Cloud management credentials authenticate requests to the control plane. Access to the RLN runtime is a separate connection and authentication concern.

How the components relate

The RGB Node API and RGB Lightning Node API operate on their respective node runtimes. The Cloud API manages hosted RLN instances; it is not a replacement for the RLN runtime API.

Choosing a node

Most applications don’t need to run a node. If you’re building a wallet or client application, integrate through the Utexo SDK — it wraps the same RGB functionality without requiring you to operate infrastructure. Choose a node runtime below only if you’re operating backend infrastructure directly. Choose RGB Node when you need:
  • On-chain RGB issuance, balances, invoices, and transfers
  • A watch-only service with external client-side signing
  • Integration into an operator-controlled backend
  • No Lightning channel or payment functionality
Choose RGB Lightning Node when you need:
  • RGB-enabled Lightning channels and payments
  • Lightning peer, channel, invoice, and payment management
  • Both on-chain and Lightning operations through one node
  • A self-hosted or managed deployment option
Choose self-hosted RLN when your team needs direct infrastructure control and can operate the Bitcoin, indexer, transport, networking, storage, and security layers. Choose Utexo Cloud when you want Utexo to provide the RLN provisioning and lifecycle-management layer while your application integrates with the node and control-plane APIs.

Signing and trust boundaries

  • RGB Node is watch-only and never signs transactions. Its xPub and master-fingerprint headers select a wallet; they do not authenticate or authorize the caller.
  • RGB Lightning Node maintains security-sensitive Lightning state. Remote external-signer support exists, but deployment-specific compatibility and production readiness must be validated.
  • Self-hosted operators are responsible for node authentication, TLS or private networking, data protection, backups, and dependency security.
  • Utexo Cloud introduces a separate control-plane trust boundary. Cloud API tokens and node-runtime access credentials serve different purposes and should be handled independently.

Shared external dependencies

Depending on the node and deployment model, the runtime may require:
  • A Bitcoin node or Bitcoin RPC endpoint
  • An Electrum or Esplora-compatible indexer
  • RGB proxy or transport endpoints for consignment exchange
  • Persistent storage for wallet or channel state
  • Network access to Lightning peers for RLN
Managed deployments may abstract some infrastructure responsibilities, but they do not change the underlying node protocol model.

Next steps

  • Read RGB Node → General Overview for the watch-only architecture and intended integrations.
  • Use RGB Node → RGB Node API for endpoints, wallet identification, configuration, and PSBT workflows.
  • Read RGB Lightning Node → Self-Hosted RGB Lightning Node to operate an RLN on your own infrastructure.
  • Use RGB Lightning Node → RGB Lightning Node API for the runtime REST endpoints.
  • Use Utexo Cloud → Node Management and Cloud API for managed RLN lifecycle operations.