Node market: subscribing and supplying
Subscribe to supplier nodes in your console and add them to line groups like your own; ban lists reach them, per-node traffic is shown. Sell your nodes too.
What it solves
Without a data centre, or without enough nodes, subscribe to other suppliers' nodes on the node market; with spare nodes, sell them there. Subscribed nodes work like your own:
- Clear offers: each offer says whether it is a single node or "N nodes · combination", shows country or region flags from the node IPs, and keeps the supplier's claims apart from the platform's measurements.
- In your line groups: under Line groups → DNS settings, pick subscribed nodes from "Unassigned IPs" and add them in bulk. Every site in the group joins scheduling and its configuration reaches the supplier automatically; no per-site binding. Pages show "supplier · node name", never the node IP.
- Ban lists delivered: a site's ban list goes through the node market to the supplier's nodes, expiries and releases included, and the ban list shows whether each ban is active there.
- Per-node traffic: pick a subscribed node in real-time monitoring to see this control plane's sites on that node: bandwidth, traffic, requests and status codes.
- Access logs: for sites served by subscribed nodes, query the access log from the supplier on demand.
- Defense capabilities: the subscribed nodes page lists what the supplier declares, what the platform verified, and whether your site rules took effect on those nodes.
Turning it on
The node market runs inside the control plane. The commercial edition can use it straight away; the community edition registers a free installation identity once first (control-api community-register on the control plane server).
Subscribers:
- Open Node market → Browse and buy, filter by region, line and billing model, and open Details to check nodes, limits, what happens at a limit and the service commitments.
- Top up with that supplier under My supplier balances, then buy (direct settlement: the money goes straight to the supplier's own merchant account). See node subscribers.
- After buying, Nodes → Subscribed nodes lists the supply groups; add the nodes under Line groups → DNS settings.
Suppliers apply for the supplier role, prepare nodes, create an offer and list it: see node suppliers.
Main settings
| Where | What you can do |
|---|---|
| Browse and buy | Filter offers, check nodes, regions, limits, claims and measurements, top up and buy |
| Subscribed nodes | Per supply group: subscriptions, usage, expiry, node health (own probe and market verdict), defense capabilities; disable a supply locally |
| Line groups → DNS settings | Add subscribed nodes to a group, set primary/backup, enable or disable |
| Ban list | Each ban's state on subscribed nodes: active, delivering, refused |
| Real-time monitoring | Pick a subscribed node to see this control plane's sites on it |
| My listings (suppliers) | Build offers from nodes; billing model (daily bundle, per GB, 95th percentile…), limits and actions at a limit |
Typical uses
- A new platform with no data centre: subscribe to two suppliers, put both in one line group and let smart scheduling pick by latency.
- Own nodes first, subscribed nodes as a safety net: put the subscribed nodes in the backup line group and let the fallback chain switch.
- A site under attack: add the IPs to its ban list and the subscribed nodes enforce it without asking the supplier.
Limits and notes
- Subscribed-node traffic covers this control plane's sites and arrives about 5 minutes late; connections, load and disk belong to the supplier's whole machine and are not shown.
- Supplier access logs cover at most 24 hours per query and 30 queries per site per minute; nothing is stored locally.
- When your own probe and the market disagree, the market's verdict decides whether DNS points at the node; your probe is shown and alerts.
- When the market pauses a supply group (limit, prepaid funds used up or an operator action), sites move to the backup supply or your own nodes; disabling a supply locally only changes your DNS, the subscription and billing continue.
- The current community release includes subscribing and supplying, but not yet subscribed nodes in line groups, per-node traffic, ban list delivery, or offer combinations and flags.