Setup Details
This document should provide a clear view of how Rails fits into various operational environments.
Node Permissions for Rails
The Rails platform requires specific permissions from a Lightning node in order to safely automate liquidity and channel management.
These permissions are intentionally scoped to limit operational access while enabling Amboss to perform essential functions on behalf of the user.
Rails avoids requesting sensitive or spend-related permissions, ensuring users maintain full control over their funds and onchain activity.
âś… Amboss does require:
- General view-only permissions
- Open and close channel permissions
- Set routing policy permissions
- Create invoice permissions
❌ Amboss does not require:
- Create onchain address permissions
- Pay to invoice or onchain address permissions
Intelligence API setup option requires no permissions.
Onboarding and Offboarding
To onboard to the Rails ecosystem:
- Set up or have a Lightning node running
- Connect the node to the Rails infrastructure
- Send onchain Bitcoin to the node
To offboard from the Rails ecosystem:
- Initiate the deactivation process
- Send onchain funds from the node to another wallet
Setup Options
Below is an overview of the three available Rails setup options. Each option offers a different balance of infrastructure control, automation responsibility, and integration effort, allowing teams to choose the model that best fits their operational requirements and desired level of involvement.
| Option | 1. Fully Managed | 2. Third Party Hosted | 3. Intelligence API |
|---|---|---|---|
| Infrastructure Responsibility | Amboss takes care of the complete infrastructure. | Client manages Lightning node infrastructure. | Client manages Lightning node infrastructure. |
| Automation Responsibility | Amboss handles everything. | Amboss handles liquidity automation. | Client manages automation via Amboss API. |
| Key Benefits | âś… Completely hands-off | âś… After node setup, almost hands-off | âś… No connection from Amboss to client node |
| Key Trade-offs | ❌ Opinionated setup | ❌ DevOps requirements | ❌ Highest integration lift |
* All setup options are self-custodial
1. Fully Managed
The Fully Managed setup is designed for teams that want a completely hands-off experience. Amboss operates the entire Lightning node infrastructure and manages all automation, allowing you to focus solely on your application. This option provides the fastest path to production with minimal operational overhead, though it comes with a more opinionated setup.
2. Third Party Hosted
In the Third Party Hosted setup, you maintain control over the Lightning node infrastructure while Amboss provides liquidity automation. This hybrid approach allows you to run your node in your preferred environment while still benefiting from automated channel management. It strikes a balance between operational control and reduced maintenance effort.
3. Intelligence API
The Intelligence API setup offers maximum flexibility and independence. You manage both your Lightning node infrastructure and your automation logic, using Amboss’s API for insights and guidance rather than direct management. This option requires the highest integration effort but provides complete control and no connectivity from Amboss to your node.
Rails API
The Rails API provides developers with direct programmatic access to operational data and insights related to their Lightning node setup within the Rails ecosystem. Built using GraphQL, the API enables efficient querying and integration into custom tooling, dashboards, or automation workflows, giving teams maximum flexibility in how they extend and interact with their node operations.
Amboss offers a GraphQL API for querying information related to a user’s Rails node setup.