Gateway
Access → policy → translation → forwarding
One edge.
A clearer picture.
Packet processing, subscriber identity and network operations in one product family. Your infrastructure stays yours. Your team gets a connected way to think about it.
Three planes. Clear responsibilities.
RADIUS & network control
Identity → service intent → access & routing decisions
Manager
Configuration → diagnostics → integrations → operations
A platform conversation, end to end.
Access & subscribers
PPPoE and IPoE access, circuit identity, VLAN/QinQ attachment and subscriber lifecycle form the broadband edge discussion.
Addressing & translation
IPv4 pools, CGNAT allocation, IPv6 addressing and prefix delegation belong in the same service design.
Identity & policy
Integrated or external RADIUS, service profiles, accounting, speed policy and suspension behaviour connect identity with service intent.
Routing & forwarding
IPv4/IPv6 forwarding and BGP/OSPF integration connect subscriber access to your upstream network.
Operations & recovery
Configuration review, backups, update planning, diagnostics and defined failure boundaries make recovery part of the design.
Automation & integration
Versioned API boundaries, billing-system integration and event-driven workflows reduce repetitive administration.
DESIGNED WITH BOUNDARIESGive the packet path
Give the packet path
its own lane.
The architectural principle is simple: the web interface belongs outside the forwarding path. Data, control and management each have a defined responsibility.
Software on your infrastructure
Plan around your own servers, network and operational requirements. Hardware and deployment profiles are part of the technical review.
Standards-based foundations
The architecture combines an independently authored C++ packet engine, DPDK I/O, FreeRADIUS integration and FRRouting integration.
A fit for your topology
Review hardware, access protocols, routes, logging, resource limits and recovery expectations before selecting a deployment.
Install. Operate. Recover. Repeat.
Installation & compatibility
Define the Linux appliance, server, NIC, firmware and virtualisation profile. Include interface roles, management access, time synchronisation, certificates and a first-subscriber health check.
Security & access
Review administrator roles, MFA/SSO requirements, scoped API credentials, audit access and customer-controlled support access. Keep privileged diagnostics bounded and sensitive data out of routine logs.
Backups & updates
Include signed release artifacts, compatibility preflight, configuration backup, update order and a recovery path. Review image, database and state-schema compatibility together.
Resilience by data class
Configuration replication, NAT allocations, subscriber sessions and routing convergence have different recovery needs. Specify fencing, failover headroom and restoration expectations.
Licensing & support
Ask about local entitlements, offline operation, renewal, hardware replacement and service behaviour during vendor-service outages. Define support hours and escalation scope in the commercial proposal.
Documentation & diagnostics
Keep setup, troubleshooting and recovery guidance aligned with the installed version. Review offline recovery, diagnostic bundles, event retention and integration contracts as part of onboarding.