Pricing · published, on purpose
The price is on the page.
Netavo publishes its pricing — a position we believe
is unique in this market.* One annual subscription per instance, banded by concurrent subscribers.
Every feature in every band; no bandwidth tiers, no core counts, no feature add-ons.
Eval≤50 subscribers
Free · forever
- Every feature, no time limit
- Community support
- For labs and evaluation
Download now
≤1ksubscribers
£—/year
- Every feature included
- Support included
- HA standby instance discounted
Start eval
≤5k · ≤25ksubscribers · two bands
£— / £—/year
- Every feature included
- Support included
- Multi-year prepay available
Start eval
∞unlimited subscribers
£—/year
- Every feature included
- Support included
- Talk to us about fleets
Start eval
includedCGNAT · IPFIX · LI-readiness · web UI
includedfull BGP/IS-IS/MPLS L3VPN routing
includedevery future feature — no add-on SKUs, ever
includedair-gapped licensing (offline signed files)
A subscriber is a concurrent session, and dual-stack counts
once. That is the entire licence. Run any server, any interface speed, any core
count, at any throughput. When you grow past a band, you move up a band —
nothing else about your hardware or traffic affects the price.
Why subscription-only? A perpetual licence from a small vendor is a promise
about the future with no income behind it. An annual subscription keeps us
accountable each year, and keeps every deployment on supported, patched
code.
Standby/HA instances are heavily discounted. Multi-year prepay exists for
capex budgets. Prices change only at renewal — never mid-term.
root@bng1:~# bng-cli show licensing telemetry
band ≤25k sessions
lease expires 2026-08-30 (renews daily)
reports session high-water · version · hw inventory
never sent subscriber identity · traffic · flows
telemetry mode full (set licensing.telemetry minimal to reduce)
What happens if the licence expires or we go over-band?
The control plane enters an administrative freeze: configuration commits, upgrades and
onboarding changes are refused. The data plane keeps forwarding, unaffected — subscribers see no
change in service. Enforcement acts on the operator's console, and is architecturally incapable of
touching traffic. We consider licence mechanisms that degrade forwarding to be an unacceptable design, and
built ours so that it cannot.
What if the box can't reach your licensing server?
Leases run ~45 days and renew daily, so it takes ~45 consecutive days of failed contact
before anything trips. A weekend outage, a firewall change, our server being down — none of it matters.
Air-gapped networks skip phone-home entirely with offline signed licence files (first-class, longer expiry).
What exactly do you see when it phones home?
Aggregate operational data: session high-water marks, band, software version, data-plane health,
hardware inventory. Never subscriber identity, addresses, or traffic. Run show licensing telemetry
to see the exact payload before it's sent, and set telemetry to minimal to send only the entitlement basics.
What counts as one instance?
One running data plane. An HA standby is a second instance at a heavy discount. Lab/eval boxes
under 50 subscribers are free.
What if we briefly burst over our band?
Nothing breaks. Enforcement is deliberately slow: telemetry drives a true-up conversation, not a
lockout. Sustained growth means moving up a band at the price on this page.
You're a small vendor. What if Netavo disappears?
A fair question of any vendor our size. Concrete continuity commitments, including escrow
terms, are being finalised with our design partners and will be published on this page.
Begin with the free evaluation tier.