How do changes reach every node in the cluster?

You edit configuration once in the console and apply it to the whole cluster. A preview shows the effect (and the generated config) before anything goes live, changes land on all nodes together, and the audit log keeps a full record. There is no config file to copy from box to box.

Can my CRM or portal integrate with it?

Yes. Subscriber mappings, plans and CoA actions are all available through the REST API, and most ISP CRMs integrate through RADIUS alone with no code. For customer portals, scoped API tokens expose the realtime bandwidth API so your app can show live per-subscriber usage.

GridM BNG · Central web console

One console. Every node. No CLI.

GridM BNG has no command line to learn and no boxes to log into one by one. Everything, from sessions and plans to CGNAT pools and DDoS policy, is managed from a single web console that spans the whole cluster, in real time. A REST API connects your billing and CRM when you need it.

Request a demo All capabilities

Illustration mirrors the shipping GridM BNG console. Identifiers are fictional.

What ships in the box

One web console manages every node in the cluster, centrally and in real time
Light and dark modes, role-based access (admin, operator, partner, LEA) and a full audit log
Preview a configuration change, then apply it cluster-wide in a click
A REST API mirrors the console for your billing and CRM
Scoped API tokens, shown once and stored hashed, expose the realtime bandwidth API
Multi-tenant partner consoles scoped to their own VLANs and subscribers

Manage the cluster, not the boxes

Pick a cluster and every node is right there. Sessions, VLANs, pools, QoS, CGNAT and security policy are all edited in one place and applied everywhere at once, with light and dark modes for day and night shifts.

Preview, then apply cluster-wide

Change a policy and preview exactly what will happen, including the generated config, before it goes live. Apply lands on every node together, and the audit log records who changed what, when and from where.

An API when you want one

A REST API mirrors the console, so your billing can provision subscribers and your portal can show live usage. Scoped API tokens, shown once and stored hashed, give each integration exactly the access it needs.

Reference

Central web console: the spec card

Operations

Management: One central web console (light/dark), cluster-wide, real-time
Analytics: Built in: live graphs, 30-day flow history, IPDR, faults, DDoS
Integration: REST API + scoped tokens for billing, CRM and portals
Access control: Roles: admin, operator, partner (VLAN-scoped), LEA; audit log
Deployment: Bare metal, VM, containers, Kubernetes; on-prem or edge

FAQ

Central web console, in detail

No. GridM BNG is managed entirely from its web console, centrally and cluster-wide. There is no per-node CLI to memorize and no logging into boxes one at a time. A REST API is available for billing and portal integration, but day-to-day operations happen in the UI.

Explore the rest of the platform

Session termination RADIUS AAA + CoA CGNAT + IPv6 QoS + plan enforcement Line-rate data plane High availability Observability Security & compliance

See central web console on live traffic

Book a live demo with a network engineer. We will walk your topology, size the hardware and show real sessions terminating on the console, not slides.

Request a demo Talk to sales

Runs on your hardware · One plan, every feature · Migrate in slices