What is Managed Node Infrastructure?
Managed node infrastructure is a service where a specialist provider deploys and operates Lightning nodes on behalf of a customer. The provider handles setup, monitoring, upgrades and channel work. The customer uses the node without building an in-house operations team.
What a managed service usually covers
- Provisioning. Deploying the node software and connecting it to the Bitcoin network.
- Monitoring. Watching uptime, channel health, peer connections and fees.
- Channel and liquidity management. Opening, closing and rebalancing channels so payments succeed. See channel rebalancing.
- Upgrades and security. Applying software updates and protocol changes.
Customers of such services include exchanges, payment providers, wallets and treasuries that want Lightning without running the operations themselves.
The key question: who holds the keys?
"Managed" describes who does the work. It does not say who controls the money. There are two models:
- Custodial managed nodes. The provider holds the keys. You carry counterparty risk on the provider.
- Non-custodial managed nodes. You hold the keys and funds. The provider acts through limited permissions that you grant, and you can revoke them.
Other trade-offs apply to both: dependence on the provider's uptime, limits on customisation, service cost, and the effort of migrating channels and peers to another operator.
How Amboss handles managed nodes
Amboss uses the non-custodial model, with different setups for its two products.
Rails. Rails is a yield service for people who hold Bitcoin or stablecoins. The Rails page says Amboss facilitates the establishment and deployment of your Lightning node. It describes "automated node generation", and its guidance says Rails automates node generation, channel management and liquidity deployment using AI. Your funds stay in your own self-hosted Lightning node, and Rails never takes custody. An Amboss launch post says Amboss runs node operations with strictly limited permissions: receive Lightning, open channels and close channels.
Rails FAQ points that matter for a managed model:
- Lightning channels have timelocks that can restrict withdrawals for around two weeks, and longer in rare cases.
- Early withdrawal is discouraged because it can disrupt liquidity commitments.
- The initial deposit is 1 BTC or more.
- The Rails page says it does not lend your funds and has no rehypothecation risk.
Amboss Payments. In the terms of service, an Amboss Payments Node is a node that the customer operates and controls, either hosted on a cloud provider the customer selects or an external node. The customer gives Amboss scoped API credentials. Amboss can then open and close channels, create invoices, adjust routing fees and view balances and activity. The node, not Amboss, initiates channel transactions from its own wallet, and Amboss does not hold or sign for your keys. See Amboss Payments.
For both products, you remain responsible for backing up your keys. The terms state Amboss cannot recover them if you lose them. Learn more about self-custody.