STARLINK SD-WAN WITHOUT THE LOCK-IN
Single-stack SD-WAN vendors answer resilience with their box at every site and their cloud in the middle. Starfleet Hub gives you three ways to build the WAN — Layer 2 through Starlink, the FleetMesh encrypted overlay, or the SD-WAN you already run — and manages the routers, service lines, data pools, and billing around whichever you choose.
THE WAN, THREE WAYS
No single stack fits mines, vessels, farms, and branch offices at the same time. Pick the transport per deployment. The management stays in one place.
Layer 2 Through Starlink
Take Layer 2 transport straight through the Starlink network for service delivery, keeping your own routing and addressing end to end with no overlay stack to operate at the edge. The platform runs the service lines, data pools, and billing on top.
FleetMesh
An encrypted site-to-site overlay that runs on your existing Starlink links, with an optional per-customer hub that gives the whole fleet one fixed egress IP. Defined, monitored, and changed from the console, with no on-site VPN configuration. Optional module, available on request.
Your SD-WAN
Keep SpeedFusion bonding or whichever SD-WAN you already trust. Starfleet Hub manages the routers underneath it — configuration templates, telemetry, remote actions — across the same mixed Starlink, MikroTik, Peplink, Teltonika, and TP-Link estate.
ONE MESH. ONE EGRESS IP.
FleetMesh joins a customer's sites into a private, encrypted overlay on top of their Starlink links — and solves the carrier-grade NAT problem for every system that needs a stable source address.
Encrypted Overlay
Sites join a private mesh over their existing Starlink links. Traffic between sites never rides the open internet unprotected.
Fixed Egress IP
An optional per-customer hub gives the whole fleet a single fixed public egress address — the answer to Starlink's carrier-grade NAT for firewalls, allow-lists, and legacy systems.
Tenant Isolation
Every customer's mesh is its own network, with its own keys and its own address space. No traffic crosses tenants.
Run From the Console
The mesh is defined, monitored, and changed from Starfleet Hub. Nobody configures VPNs on site.
BONDING LIVES AT THE EDGE. MANAGEMENT LIVES HERE.
Multi-WAN bonding and failover are edge functions: the router at the site decides how to split, steer, and recover traffic across Starlink, cellular, and wired links. Peplink does this with SpeedFusion. MikroTik and Teltonika ship their own multi-WAN and failover tooling. Those are good tools, and Starfleet Hub does not replace them.
What the platform adds is the fleet layer those tools stop at: the bonding-capable routers managed as one estate — configuration templates, live telemetry, speed tests, and audited remote actions across vendors — beside the Starlink service lines, data pools, and customer billing that the network exists to serve.
Bonding, SD-WAN, and mesh are where the platform is investing next. The overlay, the router estate, and what comes after them grow under the same console, not as another stack beside it.
SINGLE-STACK SD-WAN, COMPARED
Kognitive's Konnect answers resilience with one stack: their soft-router at every site, bonded into their hubs. It is a coherent answer. Here is how a composable one differs.
| Capability | Konnect (single stack) | Starfleet Hub (composable) |
|---|---|---|
| The edge | Konnect soft-router at every site: KonnectOS or KonnectOpen, or the KonnectAgent on third-party hardware. | The routers you already run: Starlink plus MikroTik, Peplink, Teltonika, and TP-Link, managed through RouterFleet. |
| Bandwidth bonding | Native: multi-path VPN bonding across Starlink, 5G, and wired links, including multiple Starlinks. | Delivered by the edge you choose — SpeedFusion on managed Peplink, vendor multi-WAN tooling, or your own SD-WAN — not reimplemented in the platform. |
| Fixed IP | KonnectHub provides fixed IPs and regional internet drop-off. | FleetMesh's per-customer hub gives the whole fleet one fixed egress IP. |
| Site-to-site networking | VPN routing through Kognitive hubs. | FleetMesh: a private encrypted overlay per customer, defined and monitored from the console. |
| Starlink business layer | A separate product: Orbit, for pooled data, subscriptions, usage, and billing. | Native: service lines, hierarchical data pools, automated billing, and white-label portals in the same platform. |
| What you commit to | One stack end to end: edge, hubs, and cloud. | A management plane. Transport and SD-WAN stay swappable per deployment. |
Konnect and Orbit details reflect Kognitive Networks' published materials as of August 2026. For their tools, trust their documentation.
SD-WAN AND BONDING QUESTIONS, ANSWERED
Can Starfleet Hub bond multiple Starlink dishes?
Bonding is delivered by the edge, not by the platform. Run SpeedFusion on a managed Peplink to bond Starlink with cellular and wired links, use your router vendor's multi-WAN tooling, or bring your own SD-WAN. Starfleet Hub manages the routers, the service lines behind them, and the data pools and billing on top. Bonding and mesh are an active area of platform investment.
Does Starlink give you a static IP?
Standard Starlink service sits behind carrier-grade NAT, so there is no stable public address for firewalls and allow-lists to trust. FleetMesh solves this at the fleet level: an optional per-customer hub gives all of a customer's sites one fixed public egress IP.
What is Layer 2 through Starlink?
Providers can deliver services over Layer 2 transport through the Starlink network, keeping their own routing and addressing end to end with no overlay stack at the edge. Starfleet Hub runs the commercial layer on top: service lines, data pools, usage, and billing. Talk to us about whether Layer 2 fits your deployment.
Can I keep the SD-WAN I already run?
Yes. Bring your own SD-WAN and nothing about it changes. The platform manages the routers underneath, with configuration templates, telemetry, and audited remote actions, and runs the Starlink business around it. Multi-vendor router management is an optional module, available on request.
Is FleetMesh included in the platform?
FleetMesh is an optional module, available on request. Each customer's mesh is a separate encrypted network with its own keys and address space, and the fixed egress IP hub is provisioned per customer.
All product names, logos, and brands are property of their respective owners. Kognitive Networks, Konnect, Orbit, Peplink, SpeedFusion, Starlink, MikroTik, Teltonika, and TP-Link are trademarks of their respective holders, and Starfleet Hub is not affiliated with or endorsed by them.
