Plans & Billing
noBGP bills one flat plan price per organization, plus metered usage on three meters — active nodes, bandwidth, and storage. There are no per-seat charges: invite as many members as you like, on any plan including Free. Overage is metered, never silently blocked, and your spend cap bounds it — no surprise bills.
Plans
| Plan | Price (per org) | Included allowance | Overage |
|---|---|---|---|
| Free | $0 | 20 nodes · 10 GB bandwidth · 5 GB storage | none — hard caps |
| Pro | $25 / mo ($250 / yr) | 20 active nodes · 50 GB bandwidth · 50 GB storage | $1.50 / node · $0.12 / GB bandwidth · $0.05 / GB-month storage |
| Business | $99 / mo ($990 / yr) | 50 active nodes · 150 GB bandwidth · 200 GB storage | $1.00 / node · $0.10 / GB bandwidth · $0.03 / GB-month storage |
| Enterprise | Custom | Committed | Negotiated |
Annual billing is 10× the monthly price — about two months free. Allowances are flat per organization regardless of team size.
Checkout and payment management use Stripe-hosted pages, reachable from Account → Billing in the web app, which also shows live usage against each allowance.
The three meters
Active nodes
A node counts as active for a billing period once it has been online for 24 hours in total during that period. The time is cumulative, not consecutive, so disconnecting and reconnecting doesn't reset it — but a node you only check in with briefly never becomes billable, and nodes that stay offline all period cost nothing. A node is billed once, to the organization that owned the network it registered in — even if it later participates in other networks.
Bandwidth
All node traffic is counted, in both directions — traffic between your nodes, traffic through published services, and file-storage traffic. Two rules keep the count fair:
- Node-to-node traffic is billed on one side only (the connection initiator's organization by default), so a byte moving between two of your nodes is never charged twice.
- Service and storage traffic is billed at your node's end only — the far side (the internet, the storage backend) is not double-counted.
Every connection in noBGP is relayed through managed infrastructure — that's why it works through any NAT, CGNAT, or firewall, and it's also why bandwidth is metered honestly instead of hidden behind opaque rate limits.
Storage
Billed per GB-month on the maximum stored during the period. The peak is taken per place — each network's shared drive and each node's own storage area — and those peaks are then summed into one figure for the organization. A short-lived spike sets that place's peak for the period even if you delete the data the same day.
Node storage areas count too, from router 0.4.61 — before that release only the network shares did. An area follows the machine rather than a network, so it is billed to the organization that owns the node, alongside that organization's networks in the same pool and against the same allowance.
Deleting a network or a node stops its storage billing — and deprovisioning a node removes it from the directory, so it counts as deleting it here. The peak it reached while it existed still counts for the period it reached it in — that storage was genuinely used — but nothing new accrues from it afterwards. The bytes themselves are not deleted with it: a deleted node keeps its area and the people who owned it still reach it, unbilled, for 30 days. After that the files are queued for deletion and go about a week later (router 0.4.73); the same clock applies to a deleted network's shared drive.
A network you deleted mid-period still appears in that period's usage breakdown (router 0.4.73). It is billed for what it moved and stored while it existed — deleting something has never erased the usage it already incurred — but the breakdown used to leave deleted networks out, so the figure you could check was smaller than the figure you paid with nothing on screen to explain the difference. A network with no activity in the period is still not listed once it is deleted.
The spend cap
On paid plans you can set a monthly spend cap from the billing page. It bounds your metered overage — the flat plan base is the only charge you always pay. When your actual period-to-date spend reaches the cap:
- Bandwidth is throttled (see below) so the bill stops climbing, and
- Creation of new nodes, networks, and services is refused
until you raise the cap or the period rolls over. The cap triggers on actual spend, not projections — an early-month burst won't lock you out while real spend is still low. Alerts fire at 80% and 100% of the cap, and at 80/100% of each included allowance.
Throttling instead of disconnecting
Whenever bandwidth needs to be limited — Free plan over its 10 GB allowance, spend cap reached, or a lapsed payment — noBGP never disconnects your nodes. Instead each node is throttled to 1 Mbit/s, in both directions. DNS, shells, and dashboards keep working; full speed returns automatically once the trigger clears (usage period rolls, cap raised, or payment restored).
Free plan caps
The Free plan is genuinely free — hard caps instead of overage, so it can never produce a bill:
| Resource | Cap | At the cap |
|---|---|---|
| Nodes | 20 | creating more is refused |
| Bandwidth | 10 GB / period | throttled to 1 Mbit/s per node |
| Storage | 5 GB | counts against your allowance; uploads beyond it may be refused |
| Members | unlimited | — members are free on every plan |
The Free node cap counts the nodes that currently exist in the organization and is applied when you create one — it is not the 24-hour "active node" measure the paid plans meter.
Existing resources are never taken away: if you're over a cap when limits tighten, what you have keeps working — caps apply to creating more.
If a payment fails
Grace first: a failed charge alerts you with no degradation while it's retried. If the subscription lapses:
- Existing nodes stay online, throttled to 1 Mbit/s each
- No new usage charges accrue while lapsed
- Creating new resources is blocked
Everything restores automatically on payment — creation unblocks immediately, and the throttle lifts within a few minutes. No manual steps, no stuck states.