Can I run more than one billing system on the same cluster?

Yes. The RADIUS interceptor supports multiple realms on one cluster, so different partners or brands can keep their own RADIUS and billing while sharing the same BNG infrastructure. Sessions are tagged per realm and partners see only their own subscribers.

GridM BNG · RADIUS AAA + CoA

Your billing stays. Your BNG gets smarter.

GridM BNG speaks standards RADIUS to the FreeRADIUS, billing or CRM stack you already run, and adds a built-in interceptor for multi-realm wholesale, carrier attributes and live policy, so AAA becomes a capability, not a constraint.

Request a demo All capabilities

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

What ships in the box

RADIUS authentication, authorization and accounting (RFC 2865/2866)
Change of Authorization, CoA, for live plan changes and mass disconnects (RFC 5176)
Multiple RADIUS realms on one cluster for wholesale and partner billing
Interim accounting tuned for billing accuracy
Works with FreeRADIUS and any RFC-compliant RADIUS or ISP CRM
Local fallback policy when RADIUS is unreachable

Drop-in interop

RFC 2865/2866 against any compliant server, with interim accounting tuned for billing accuracy and a local fallback policy for RADIUS outages. Migrations reuse your existing users, plans and workflows.

CoA operators actually use

Change a plan live, apply a quota action, disconnect one session or every session matching a filter, from the console or the API. RFC 5176, wired into daily operations.

A multi-realm interceptor

Run multiple billing realms on one cluster for wholesale and partner models. Inject Operator-Name (RFC 5580), strip realms, rewrite Framed-IP, and preview the whole config as YAML before you apply it.

Reference

RADIUS AAA + CoA: the spec card

AAA and policy

AAA: RADIUS auth, authorization, accounting (RFC 2865/2866)
Dynamic policy: CoA (RFC 5176): plan change, disconnect, quota
Billing interop: FreeRADIUS and RFC-compliant RADIUS/CRM stacks

FAQ

RADIUS AAA + CoA, in detail

Yes. GridM BNG is standards-based RADIUS (RFC 2865/2866) with CoA (RFC 5176), so it drops into existing FreeRADIUS and RFC-compliant billing or ISP CRM stacks. Plans, quotas and disconnects keep working the way your OSS already expects.

Explore the rest of the platform

Session termination CGNAT + IPv6 QoS + plan enforcement Line-rate data plane High availability Observability Central web console Security & compliance

See radius aaa + coa 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