NGX View unifies distributed infrastructure with a private Layer 2 network fabric over Starlink and other transports. See every site. Connect every site. Operate as one.
Connect remote sites, branch offices and critical infrastructure into a single, private Layer 2 network over Starlink, LTE and other transports — with no changes to your existing network protocols.
Explore Private L2 FabricReal-time monitoring, alerting and performance analytics for your Starlink deployments. Detect issues early, reduce downtime and keep your network performing.
Explore Fleet ManagementPurpose-built for satellite and cellular transport with a focus on transparency, reliability and operational control.
From remote communities to enterprise sites, NGX View delivers secure, reliable connectivity where fibre doesn’t reach.
Tower backhaul for operators whose towers sit beyond fibre or microwave reach. Each tower’s VLANs land on your DC switch as if the tower were on-net.
Schools on LEO links routed through your central filtering, policy and usage records, so every school is monitored and reachable from one place.
Pit offices and site camps joined to the operations network over the link available on the day, with shaping that keeps voice and control traffic responsive.
Branches on Starlink join the same VLANs as sites on fixed transport. No per-site routing or VPN configuration.
NGX View enables secure, private connectivity for organizations that operate beyond the reach of traditional networks.
Switches, radios and CPE plug into the Edge appliance’s LAN port, exactly as they would into a patch cable.
Encrypts every Ethernet frame and shapes traffic to the capacity the link is delivering right now.
Starlink first. LTE, 5G and fixed links use the same adapter model. You hold the service plan.
Frames arrive unchanged on your switch trunk. Your BNG, DHCP, policy and Internet breakout do the rest.
| What it takes | Build it yourself | NGX View |
|---|---|---|
| Layer 2 to every site | Assemble, tune and maintain an encrypted overlay per site | Edge and Gateway ship ready; frames arrive unchanged |
| Shaping on variable links | Fixed rate caps that are wrong most of the time on LEO | Rate follows measured capacity in both directions; the queue stays in your equipment, not the dish |
| Visibility | A dish app per site, ping graphs and spreadsheets | One console for latency, loss, throughput, dish health and power at every site |
| Field work | Laptop and console cable at the tower | Commission and troubleshoot from a phone over Bluetooth |
| Skills | In-house tunnelling, routing and queue-management expertise | Your existing NOC team |
| Ownership | You own and maintain every line of code | You own the network, the hardware and the carrier plan; we maintain the software |
Talk to an engineer about your sites, underlays and data centre. We’ll map the fabric to your topology.
NGX View combines fleet management and private Layer 2 networking in one product for distributed Starlink deployments. You install it, you run it, and every site behaves as if it were on-net.
The NOC console. Every site on one map, a page per site, alerts, roles and remote access you grant.
The appliance at each site, plus a mobile app that talks to it over Bluetooth for commissioning and field service.
Runs in your data centre and terminates every site’s tunnel onto a trunk port on your DC switch.
Customer frames enter at the site and leave at your DC unchanged. Control watches both ends; it never sits in the data path.
This is a product you buy, install and operate — not a managed service. Your network stays yours.
Every capability is labelled with where it actually stands.
| Capability | Status | Notes |
|---|---|---|
| Private L2 fabric over Starlink | Beta | One underlay per site; 802.1Q trunk carried end to end |
| Adaptive shaping | Beta | Rate taken from measured capacity in both directions |
| Customer IPv4 inside the fabric | Beta | Underlay works behind carrier-grade NAT |
| Customer IPv6 inside the fabric | In development | Carried inside the tunnel; underlay stays IPv4 |
| Control (NOC console) | In development | Fleet map, site pages, alerts, wallboard |
| Edge mobile app | In development | Commissioning and troubleshooting over Bluetooth |
| LTE / 5G adapter | In development | Per-circuit cellular rules |
| Mobile operator backhaul | In lab | Cell-site backhaul over live LEO links |
| Multilink (bonded underlays) | Roadmap | Planned product tier |
| Additional LEO carriers | Roadmap | Same adapter model as Starlink |
Real-time monitoring, alerting and performance analytics for your Starlink deployments. Detect issues early, reduce downtime and keep your network performing.
Status, latency and throughput for the whole fleet, with the sites that need attention sorted to the top.
Link quality, dish health, power and the VLANs the site carries — in one place, without logging into the dish or the appliance.
LEO capacity moves all the time. The Edge measures what the link is delivering and sets its rate just below it, so queues build in your equipment where they’re managed — not in the dish.
Each alert names the site, the measurement that moved and when — so the first call goes to the right person.
Open alertsField teams pair with the Edge over Bluetooth, assign it to a site and check the link before they leave the tower. No laptop, no console cable.
Support can only reach a site when you grant it, for as long as you choose. Every grant is logged.
Grants expire automatically. This is a demo control.
Open the demo NOC with 126 illustrative sites, or ask us to load your own site list.
NGX View creates a private Layer 2 fabric over Starlink and other transport links, unifying your remote sites into a single network.
Starlink gets you a connection at the tower. NGX View makes that tower part of your network: your VLANs, your customers and your policies, carried privately over Starlink, LTE or fixed links.
An unshaped LEO link fills the dish’s buffer the moment it saturates, and latency climbs with it. The Edge keeps its rate just under the capacity it measures, so the queue is managed before traffic reaches the dish.
Shape of behaviour only. Published figures will come from side-by-side runs on live links.
| Service | Transparent Layer 2 between each site and your data centre |
|---|---|
| VLANs | 802.1Q trunk; several VLANs per site, e.g. 100200900 |
| Frame size | Full-size customer Ethernet frames, delivered unchanged |
| Inside the fabric | Customer IPv4 today; IPv6 in development |
| Underlay | IPv4, including behind carrier-grade NAT |
| Encryption | AES on every frame between Edge and Gateway |
Bring your VLAN plan and site list. We’ll show where the Edges and Gateway sit.
Engineered for variable satellite and cellular links with a focus on transparency, reliability and operational control.
An Edge at each site and a Gateway in your data centre. Between them, one encrypted tunnel per site carries Ethernet frames over whatever underlay the site has.
Nothing about a carrier is hard-coded. Each underlay — Starlink, cellular, fixed — is an adapter with its own parameters, so a new carrier is a new adapter, not a new product.
The Edge measures delivered throughput in both directions and sets its shaping rate just below what the link is delivering. Active queue management at the Edge then owns the queue.
| Service | Transparent Ethernet (Layer 2) between site and data centre |
|---|---|
| VLANs | 802.1Q trunk on Edge and Gateway; several VLANs per site |
| Frames | Full-size customer frames delivered unchanged |
| Customer IP | IPv4 (beta); IPv6 (in development) |
| Underlays | Starlink (beta); LTE / 5G (in development); fixed links; further LEO carriers (roadmap) |
| Underlay addressing | IPv4, including behind carrier-grade NAT |
| Encryption | AES, Edge to Gateway |
| Shaping | Adaptive, from measured capacity in both directions; active queue management at the Edge; ECN |
| Management | Control web console; Edge mobile app over Bluetooth |
| Edge hardware | ARM appliance |
| Gateway hardware | Your x86 or ARM server, or a supplied appliance |
| Sites per Gateway | 150 |
From remote communities to mobile operations, NGX View keeps your network connected, secure and visible.
Towers on Starlink send subscribers straight out of the dish’s public IP — outside your BNG, your policy and your brand.
Schools on raw Starlink go straight to the Internet: no central filtering, no usage records, and abuse notices land on the Starlink account.
Rural base stations are strapped to a dish. The LEO carrier is an opaque pipe, and the operator has no control of the backhaul dataplane.
Sites on Starlink need routers, VPN profiles and firewall rules before they can reach the corporate network.
Remote operations move faster than fibre. Each new camp needs connectivity that behaves like the main site network.
Clinics, offices and field units in remote areas end up on unmanaged Internet links with no central visibility.
Tell us your sites and underlays; we’ll tell you honestly whether the fabric is the right tool.
Reference designs show how the fabric is deployed in each setting. They describe topology, not customer results.
| Sites | Towers with 5–25 subscribers each |
|---|---|
| Underlay | Single Starlink terminal per tower |
| VLANs | Residential shared 100, enterprise 200, management 900 |
| At the DC | Gateway into the BNG trunk; IPoE provisioning and billing unchanged |
| Sites | Schools homing to one Gateway, growing in phases |
|---|---|
| Underlay | Starlink at each school |
| VLANs | Learners 110, staff 120, management 900 |
| At the DC | Central filtering, policy and usage records for ministry reporting |
| Sites | Temporary and semi-permanent sites that move with operations |
|---|---|
| Underlay | Starlink, with cellular where coverage exists |
| VLANs | Operations 300, voice 310, camp Wi-Fi 320 |
| At the DC | Same operations network as the main site |
| Sites | A few Starlink branches joining a dozen sites on native transport |
|---|---|
| Underlay | Starlink at the branches; existing transport elsewhere |
| VLANs | One corporate VLAN pushed to every branch |
| At the DC | Branches appear on the same LAN as the other sites |
One licence per site and one platform licence per Gateway. No per-subscriber or per-gigabyte fees.
No. You buy and run it. You own the network, the hardware and the carrier plans, and you restore uplinks and towers. We maintain the software and verify the fabric’s behaviour remotely when you ask.
No. You hold the Starlink (or other carrier) plan and are responsible for its terms. The fabric is transport software that runs over it.
Any location with an Edge appliance carrying traffic to your Gateway.
Documentation ships with the beta. The sizing tool works now.
Estimate busy-hour load at your Gateway from sites and subscribers.
—
Planning estimate only. Gateway capacity depends on hardware and is confirmed in testing.
Yes. The Edge connects outward to your Gateway, so the underlay can sit behind carrier-grade NAT.
No. The fabric carries Ethernet frames unchanged, including 802.1Q tags, so the site behaves as if it were patched into your DC switch.
From your BNG or DHCP server at the data centre, exactly as on-net.
The Edge measures the drop and lowers its rate straight away, so latency stays controlled while throughput follows the link.
Telemetry and measurement are kept small so they don’t materially draw on data allowances.
Only when you grant access, for as long as you choose. Every grant is logged.
NGX View is built by NGX Soft LLC for service providers who run their own networks, starting where LEO is the only practical link.
Every rate, every claim and every chart comes from a measurement on a live link.
Your addressing, your policy, your carrier plans, your access decisions. We provide the transport.
Ethernet, 802.1Q, IPv4 and IPv6. Nothing your team has to relearn.
Our first deployments are with operators across the SADC region, where LEO is often the fastest way to reach the next tower or school.
| Sales and demos | sales@ngxsoft.com |
|---|---|
| Support | support@ngxsoft.com |
| Company | NGX Soft LLC |
Tell us about your sites. An engineer replies within one business day.
Your request is ready as an email to sales@ngxsoft.com. Send it and an engineer will reply to within one business day.
| Status | Site | Region | Type | Underlay | Gateway | Latency | Loss | Down | Up | Uptime 30d |
|---|
Gateways terminate each site’s tunnel into the data-centre trunk. They do no routing or subscriber management.
Explore sample sites, links and alerts with generated data. No account or password is required. This console does not access a live customer network.
Open demo console Request a demo for your networkDocumentation ships to beta operators with each release candidate. Request access and we’ll send it with your demo.
Request access