Peplink Management

PEPLINK FLEET MANAGEMENT BEYOND THE HARDWARE

InControl2 watches your Peplink hardware. Starfleet Hub runs the Starlink business behind it: service lines, data pools, overage, and white-label billing, with Peplink, MikroTik, Teltonika, and TP-Link routers in the same console.

BOOK DEMO

THE LAYER INCONTROL2 WAS NOT BUILT FOR

Credit where it is due: InControl2 is a capable tool for the job it was designed to do.

InControl2 is Peplink's own cloud management platform: zero-touch provisioning, SpeedFusion SD-WAN provisioning, GPS fleet maps, alerts, and a mobile app. Peplink is a Starlink Authorized Technology Partner, so InControl2 also surfaces Starlink terminal telemetry such as throughput, latency, and obstruction, shows terminals on the map, and can reboot or stow the dish remotely.

Two boundaries define it. First, InControl2 manages Peplink hardware exclusively, so a MikroTik, Teltonika, or TP-Link router in the same fleet needs a second tool. Second, it monitors the Starlink terminal rather than administering the Starlink service. Service-line and account administration, plan changes, data pools, overage handling, customer billing, and white-label reseller portals sit outside its scope.

That second boundary is where a reseller's margin lives. InControl2 monitors the hardware. Starfleet Hub runs the Starlink business behind it: accounts, pools, overage, and white-label billing, across mixed router fleets. If you run Peplink hardware for your own network, InControl2 may be all you need. If you sell connectivity to customers, you need the layer above it.

ONE CONSOLE FOR THE FLEET AND THE BUSINESS

Starfleet Hub is the management layer through which operators order, activate, monitor, and bill Starlink services for their end customers.

Mixed Router Fleets

RouterFleet manages Peplink, MikroTik, Teltonika, and TP-Link routers beside the Starlink router through one interface, with new vendors added through the same adapter model. Configuration templates push to one device or the whole fleet, live speed tests run from the portal, and every remote command is queued, executed, and audited. Optional module, available on request.

Remote Access Behind CGNAT

Managed routers connect outbound to the platform over an encrypted tunnel. Sites behind Starlink carrier-grade NAT need no public IP, no inbound firewall rules, and no per-site VPN administration. Router telemetry, interface throughput, and health are collected continuously and charted in the portal, next to the dish telemetry for the same site.

The Starlink Business Layer

Order, activate, pause, swap, and retire Starlink service lines from the same portal. Hierarchical data pools allocate wholesale capacity down your distribution hierarchy with automatic throttling at exhaustion, and reseller billing turns usage into branded invoices in more than 30 currencies, with a documented REST API for your own systems.

The full platform picture is on the features page, and the pool model has its own deep dive on the data pools page. If your fleet is 100 kits or 20,000, book a walkthrough and bring your hardware list.

INCONTROL2 AND STARFLEET HUB, SIDE BY SIDE

Not a takedown. The two tools solve different problems, and many fleets run both.

InControl2 details reflect Peplink's own published materials. For the vendor's tool, trust the vendor's documentation.

PEPLINK AND STARLINK QUESTIONS, ANSWERED

Is Starfleet Hub a replacement for InControl2?

It depends on what you need. Deep SpeedFusion configuration stays in InControl2, and many Peplink shops keep it for exactly that. Starfleet Hub adds the layers InControl2 does not cover: mixed-vendor router fleets, plus the Starlink business side from service lines and data pools to customer billing and white-label portals. Most teams run both.

Can I manage Peplink and Starlink together?

Yes. Starfleet Hub manages Peplink routers and the Starlink terminals they sit behind from one console. Router telemetry, configuration templates, and remote reboot sit next to dish telemetry, service-line status, data usage, and alerts, so one screen answers how a site is really performing. Multi-vendor router management is an optional module, available on request.

Can I keep using InControl2 alongside Starfleet Hub?

Yes. Starfleet Hub does not require any change to your InControl2 setup. A common pattern is to keep InControl2 for SpeedFusion provisioning and deep Peplink configuration, and to use Starfleet Hub for cross-vendor fleet visibility, Starlink service-line administration, data pools, and customer billing.

Does Starfleet Hub support mixed Peplink and MikroTik fleets?

Yes. RouterFleet manages MikroTik, Peplink, Teltonika, and TP-Link routers through one interface, with new vendors added through the same adapter model. Managed routers connect outbound to the platform over an encrypted tunnel, so sites behind CGNAT need no public IP and no inbound firewall rules. RouterFleet is an optional module, available on request.

Can I bill my customers for Starlink data through the platform?

Yes. Starfleet Hub includes reseller billing: pricing, subscriptions, invoices, payments, credit notes, and dunning, in more than 30 currencies. Data pools meter what every customer consumes, automatic throttling holds your contract ceiling, and self-service top-ups turn overage into revenue instead of a dispute. Invoices carry your brand, not ours.