Features
Resellers
A reseller opens accounts for its own customers, orders servers for them and pays for them. What the customer sees, how a customer leaves, and who is invoiced afterwards.
On this page
What a reseller does
A reseller opens a customer account, orders servers on the customer's behalf and pays for them. The server belongs to the customer; the subscription belongs to the reseller and is invoiced to the reseller at the reseller's discount. The rule is: whoever can manage the server pays for it.
What the customer sees
A card under My account → Profile tells the customer who manages the account: the reseller's name and contact address, what the reseller can do and what it cannot. The customer is informed once, on first using the panel. What the reseller does appears in the list under My account → Activity: server operations, orders, the opening of the account, and console, schedule, tag, disk, image, name and lock actions. A reseller merely viewing the servers is not in the list.
Leaving a reseller
| Way | Who | Where |
|---|---|---|
| The customer leaves | The customer | My account → Profile → "Leave the reseller" |
| One customer is removed | Staff with the users.manage permission | Administration → Users → the reseller's summary → "Remove from reseller" |
| The reseller status is removed | Staff with the users.manage permission | All customers leave together |
In all three cases the same things happen in a single database transaction:
- Running subscriptions pass to the customer and start clean: a payment suspension is lifted, a cancellation at period end saved by the reseller is removed, and auto-renewal is switched on. The reseller's arrears do not become the customer's debt.
- Renewal invoices issued to the reseller for those servers and not paid at all are cancelled; the first unpaid period is invoiced to the customer with its own due date.
- The reseller's other open invoices (the first invoice of a server that was built, a resize or disk difference, partly paid ones) stay with the reseller, and staff have to look at them.
- The reseller's open consoles are closed, and the SSH key it added to the account when ordering is removed from the account. The key inside running servers is not touched; the notification sent to the customer says so.
The price after leaving
Servers whose subscription passes to the customer are invoiced at the list price from the next invoice on, provided the list price can be established exactly. Nothing is asked for the current period. The customer sees the new monthly amounts before leaving, in the "Leave the reseller" confirmation.
The panel stores one price per server and does not store the discount that was applied. The list price is therefore calculated from today's catalog, and it is accepted only if taking the reseller's current discount off it gives the server's price to the last cent. If it does not (the catalog or the discount has changed, staff set the price by hand, the server is in a virtual datacenter or is not monthly), the price stays as it is and the server is listed for staff. Correcting the price is then a job for staff.
Disabling a reseller is not removing it
A reseller that is disabled (not removed) can no longer act on its customers' servers, but the customers remain its customers and the subscriptions remain its subscriptions, and it goes on paying. To end that, remove the reseller status or remove the customers one by one.
Known gaps
- If leaving coincides with an order the reseller places at that very moment, that order can end up outside the separation.
- A server whose list price cannot be established exactly is invoiced at the reseller's discounted price until staff correct it.
- Staff signed in on behalf of a customer cannot take the account away from its reseller; that decision belongs to the account's owner.
- The new amounts in the leave confirmation and the price warning staff see have no end-to-end test; the rules behind them are covered by integration tests.
Source: docs/billing.md, "Bayiler: kim öder" (Turkish).
Install command
curl -fsSL https://lightningvm.app/install.sh | sudo shUbuntu 22.04 / 24.04 / 26.04. Requirements and options
