Starlink Management Platforms: What to Look For

By Paul Sutherland Founder, Liquidbinary Ltd 25th October 2026

A Starlink management platform is software that runs many Starlink accounts, service lines and terminals from one place. The Starlink dashboard manages one account at a time. A platform brings every account together, keeps their records in step and makes changes through Starlink’s Enterprise API. What a platform can do depends on where its data comes from. That is the first thing to check.

This guide sets out the kinds of platform, where each one gets its data, and the questions to ask before you choose. Every statement about Starlink’s API comes from Starlink’s public documentation.

A platform does four jobs:

  • Inventory. Every account, service line and terminal, in one searchable list.
  • Changes. Service line activation, plan changes, data blocks and priority data, made through Starlink’s API.
  • Usage and billing. Usage per service line against each billing cycle, with overage and invoices.
  • Monitoring. Whether each terminal is online, and how it is performing.

The first three run the accounts. The fourth decides whether the platform also sees the terminals.

Where does the data come from?

There are two sources, and they answer different questions:

  • The Starlink account, through the Enterprise API. Accounts, service lines, data plans, usage and invoices. The API also carries some terminal telemetry, as a summary aggregated over fifteen seconds (telemetry API). Changes to service lines and data reach Starlink only through this source.
  • Direct from the terminal, through its own local API, the one the Starlink app reads. Latency, drop rate, obstruction, alignment, power draw and outages, live, every second. The terminal’s own readings come only from this source. Starlink Aviation terminals serve no local API, so their readings come from the account alone.

A platform built on one source answers only that source’s questions. The Enterprise API vs direct telemetry guide compares the two in detail.

Why does a platform need both sources?

A fault can sit on either side of a terminal. The account shows whether the service line is active, which data block it is on and how much data it has used. The terminal shows whether it is obstructed, aligned and powered, and when each outage began and ended. With both on one screen, a support team finds the cause of a fault without switching tools.

Platforms built on the Enterprise API alone see the fifteen-second summary. Nexus Telemetry Enterprise reads each terminal direct and live, and integrates it with the Starlink account.

Which accounts can use one?

Starlink’s developer documentation states that the API “is available to all Enterprise accounts”. Its support centre extends API access to “Starlink Authorized Resellers, Enterprise or larger Business Customers”. Platforms built on the API serve those accounts.

Accounts without API access are managed through the Starlink dashboard and the Starlink app. Terminal monitoring works on any account, because it reads the terminal rather than the account.

What kinds of platform are there?

Tools sold for Starlink management fall into four kinds:

  1. Provider portals. A reseller’s own portal, included with the service it sells. It covers the accounts that provider holds.
  2. Network management tools. Router and network management products that list Starlink terminals beside the rest of the network.
  3. Management platforms on the Enterprise API. Software that connects to your Starlink accounts through service accounts and manages them.
  4. Terminal monitoring. Software that reads each terminal directly, for performance and outages.

An organisation that runs its own estate needs the third and the fourth together.

What should you check before you choose?

Ask these questions of any platform, bought or built:

  1. Does it cover every account? That includes the managed accounts beneath a manager account, in one view (managed accounts explained).
  2. Does it keep its own store? Starlink advises syncing data into your own database on a schedule. A platform that calls the API on every page view spends the limit of 250 requests a minute per account (rate limits in practice).
  3. Does it keep history? The API returns usage for the current billing cycle and up to six previous cycles. Older usage exists only where a platform stored it as it arrived.
  4. How does it hold your credentials? Starlink requires providers to keep service account secrets in a key management system (API access management). Ask where the secret is held and who can read it.
  5. Can you end its access? Access through a service account ends when you delete its secret or disable the service account in the Starlink dashboard (service accounts and permissions).
  6. Does each change cite the API? Every action is traceable to the endpoint it calls and the permission it needs.
  7. Are clients kept apart? For providers, one customer never sees another customer’s service lines.
  8. Does it read the terminal directly? The API’s terminal telemetry is a fifteen-second summary. Live, second-by-second readings come only direct from the terminal.

Build or buy?

The Enterprise API is a set of endpoints, not a tool. Building on it means four pieces of work:

  • Service account secrets held in a key management system.
  • A sync that stays within the rate limits.
  • A store for history beyond six billing cycles.
  • Transfers assembled from several calls, because “the Starlink APIs do not include a native transfer process” (service lines guide).

A team that already runs integrations can take this on. A platform delivers the same result without the build.

How does Nexus Telemetry Enterprise approach this?

Nexus Telemetry Enterprise is a Starlink management platform, built on Starlink’s public API. Each customer runs on a dedicated server.

  • It connects every account through its service account, or the whole tree through a manager account, and keeps its own store on a schedule, as Starlink recommends.
  • It manages service lines, data blocks and priority data through Starlink’s API, with each action traced to Starlink’s public documentation.
  • Each team, region or client has its own view and its own sign-in, showing only its own service lines.

Access stays in your hands: deleting the secret or disabling the service account in the Starlink dashboard ends it at once.

Where a site needs the terminal’s own detail, Nexus Telemetry Fleet reads each terminal directly, through a collector at each site. It is a separate product and works on its own.

Where do you start?

List your Starlink accounts. In the Starlink dashboard, check each one for a Service Accounts section under Settings. Where it appears, the API is available and a platform built on it can manage that account. Then put the eight questions above to each option, including building your own.

Starlink Enterprise management, across every account

Nexus Telemetry Enterprise reads your Starlink accounts through Starlink's Enterprise API. Service lines, usage, telemetry and incidents, with nothing to install.

Try the live demo