MANAGE TP-LINK ROUTERS REMOTELY ACROSS YOUR STARLINK FLEET
Your TP-Link routers sit behind Starlink dishes in places you cannot drive to. Starfleet Hub puts the routers, the terminals, and the business behind them in one console: configuration templates, live telemetry, remote actions, data pools, and reseller billing.
BUILT FOR THE WAN SIDE OF EVERY SITE
Omada manages the network inside a site. A Starlink reseller has to manage the network between sites, and the business that bills for it.
Plenty of Starlink installations put a TP-Link router behind the dish. Then the installer leaves, and the router sits behind carrier-grade NAT on a mine site, a vessel, or a farm, with no public IP address and no way in. Every configuration change becomes a phone call, a site visit, or a guess.
Starfleet Hub reaches those routers without any of that. Managed routers connect outbound to the platform over an encrypted tunnel, so no public IP, no inbound firewall rules, and no per-site VPN administration are required at any site. From there, TP-Link fleet management looks the way it should: define configuration once, push it to one router or the whole fleet, and watch telemetry come back continuously.
And because the router is only one part of the site, the same portal manages the Starlink terminal beside it: the service line, the plan, the data pool it draws from, and the invoice the customer receives.
ONE CONSOLE FOR THE ROUTER, THE DISH, AND THE BILL
Configuration Templates
Define router configuration once and push it to a single TP-Link device or the whole fleet, with per-device overrides where a site needs them.
Remote Access Behind CGNAT
Routers dial out to the platform over an encrypted tunnel. Sites need no public IP, no inbound firewall rules, and no per-site VPN administration.
Router Telemetry
Interface throughput, health, and status collected continuously and charted in the portal, next to the dish telemetry for the same site.
Remote Actions and Speed Tests
Reboot, push configuration, run diagnostics, and start a live speed test from the portal, with every command queued, executed, and audited.
Fleet Map and Alerts
Every device on an interactive world map, with clustering that stays legible at scale and offline, obstruction, throttle, and overage alerts ranked by severity.
The Business Layer
Starlink service-line management, hierarchical data pools, reseller billing, and white-label portals on the same platform, so the router fleet and the revenue live together.
RouterFleet manages TP-Link, MikroTik, Peplink, and Teltonika routers alongside the Starlink router through one interface. Optional module, available on request.
OMADA RUNS THE SITE. STARFLEET HUB RUNS THE FLEET.
Omada is TP-Link's software-defined networking platform for SMB sites, with three controller options: a software controller, the OC200 hardware controller, or a cloud-based controller licensed per device with a limited free tier. It manages access points, switches, and gateways for retail, hospitality, and office networks, and it does that job well. It has no Starlink awareness and no data-pool or customer-billing constructs, because it was never meant to run a satellite WAN fleet or a reseller business. The honest comparison looks like this.
| Capability | Omada controller (LAN operations) | Starfleet Hub (WAN + fleet + business layer) |
|---|---|---|
| TP-Link LAN management | Yes, in depth. SDN control of Omada access points, switches, and gateways within a site. | Router fleet management: templates, telemetry, remote actions, and speed tests for TP-Link routers at the WAN edge. |
| Starlink terminals and service lines | No Starlink awareness. | Activate, pause, resume, change plans, apply top-ups, and run dish diagnostics per service line. |
| Mixed router vendors | Omada hardware only. | TP-Link, MikroTik, Peplink, and Teltonika beside the Starlink router, in one console. |
| Data pools and overage control | No data-pool constructs. | Hierarchical pools with automatic throttling and self-service top-ups. |
| Customer billing and white-label | No customer-billing constructs. | Invoices, payments, credit notes, multi-currency billing, and white-label portals. |
| Remote access behind CGNAT | Managed through a local or cloud controller built for site LANs. | Routers connect outbound over an encrypted tunnel. No public IP or inbound firewall rules at any site. |
The two are complementary where that is the honest answer. Keep Omada on the access points and switches inside a site if it already runs them. Put Starfleet Hub over the routers at the satellite edge, the Starlink service lines, and the reseller business across every site. See the full platform on the features page, read how data pools protect margin, or book a demo.
TP-LINK FLEET QUESTIONS, ANSWERED
Can I manage TP-Link routers and Starlink together?
Yes. Starfleet Hub manages TP-Link routers and the Starlink terminals behind them from one portal. You see router telemetry and dish telemetry for the same site, push configuration templates to the routers, run dish diagnostics, and manage each service line, its plan, and its data from the same console.
Does Starfleet Hub replace Omada?
No, they do different jobs. Omada is TP-Link's SDN platform for the site LAN: access points, switches, and gateways for offices, retail, and hospitality. Starfleet Hub runs the WAN fleet and the reseller business: routers at the satellite edge, Starlink service lines, data pools, and customer billing. Many operators keep Omada inside the site and put Starfleet Hub over the fleet.
Can I manage TP-Link routers installed behind Starlink CGNAT?
Yes. Managed routers connect outbound to the platform over an encrypted tunnel, so carrier-grade NAT does not block management. No public IP, no inbound firewall rules, and no per-site VPN administration are required at any site.
Can I mix TP-Link with MikroTik, Peplink, and Teltonika in one fleet?
Yes. RouterFleet manages TP-Link, MikroTik, Peplink, and Teltonika routers alongside the Starlink router through one interface, and new vendors are added through the same adapter model. Configuration templates, telemetry, and remote actions work the same way across vendors. Optional module, available on request.
Is there an API?
Yes. Starfleet Hub publishes a versioned REST API as an OpenAPI 3.1 contract with OAuth 2.0 client-credentials authentication. It exposes service lines, terminals, telemetry, usage, alerts, and pool capacity, and it supports lifecycle operations such as activation, plan change, pause, resume, and top-ups.
All product names, logos, and brands are property of their respective owners. TP-Link, Omada, Starlink, MikroTik, Peplink, and Teltonika are trademarks of their respective holders, and Starfleet Hub is not affiliated with or endorsed by them.
