We're looking for beta testers.

Compare

Orbimon vs the Starlink Enterprise API

The Starlink Enterprise API is how the largest Starlink customers manage accounts, terminals and telemetry in code. It's capable, but the API itself is raw programmatic access—you integrate it without a Starlink-built UI—and most installers and small fleets can't qualify. Starlink's operational dashboard is a separate product many Business and Enterprise customers already have; Orbimon sits beside it with longer history, shareable read-only views, and several independent client accounts without collecting their Starlink logins. Here's how it compares with Orbimon, and why we see the two working together.

Feature comparison

FeatureStarlink Enterprise APIOrbimon
Who gets accessEnterprise accounts; some Authorized Resellers and larger Business customers by asking their account managerAny business running lots of dishes, no Enterprise account needed
Requires a Starlink Business or Enterprise accountYes (Enterprise; some larger Business via account manager)
Several Starlink accounts or clients in one dashboardYou build it
Extra hardware neededYes, a small device next to the router
What you getHTTPS endpoints and streamed telemetry (you build the interface)Operational dashboards, fleet map, email and webhook alerts, and history
Data retentionData Usage API: about six billing cycles of consumption. Telemetry API: ~15s aggregates with ~8h stream retention unless you store it yourselfUp to 30 days of charts in the dashboard; hourly summaries and events for 365 days; daily summaries kept indefinitely
Request limitsRate limited per accountNot something you manage
Alerts by email and webhooksYou build itEmail or signed webhook, Alert profiles you assign per monitor
Fleet mapYou build itYes, fleet map by status
Read-only live view for customers (no Orbimon login)You build itYes, public share links for one dish or a fleet
Team members and rolesService accounts you manageYes, members and roles
Audit logYou build itYes (exportable for owners and admins)
Data access for your own toolsYes (the API itself)API tokens and signed webhooks
Offline buffering (store and forward)N/A (direct from Starlink)Yes, the device stores readings and uploads when the link is back
Service managementNo, read only. Never changes dish, plan or billing
Engineering effortStorage, dashboards and alerting are yours to build and maintainNone to get started
How data is collectedDirectly from StarlinkToday a small device next to the router; a direct connection to the Enterprise API is on the way
CostIncluded with qualifying accounts (you build tooling)Free while in beta

About the Starlink Enterprise API

It lets qualifying customers manage their accounts, terminals and service programmatically, and stream telemetry. The API has no first-party UI—you integrate it in your own systems. Buying hardware labeled Enterprise is not the same as an Enterprise account: Starlink describes Enterprise customers as large business customers with a minimum annual Starlink recurring spend of US$1M, and those accounts can include an Enterprise Dashboard alongside the API. Many Business customers use Starlink's fleet dashboard too; Business Priority pages advertise that dashboard with no published kit or seat minimum (marketing lines about fleet scale are not a minimum fleet size). Using the API means creating a service account with the right permissions and looking after its keys. Requests are rate limited. The Data Usage API keeps about six billing cycles of consumption history; the Telemetry API streams roughly 15-second aggregates with about eight hours of stream retention unless you store the data yourself—so long-term operational records need your own storage.

About Orbimon

Orbimon is the layer many teams would otherwise have to build: live status for every dish, charts with outages marked, latency, packet loss, speeds and obstructions, email and webhook alerts, and an API of its own. It complements Starlink's own dashboard when you want longer history in one place, read-only links for stakeholders, or several client Starlink accounts in one Orbimon org without collecting their Starlink logins. We're working on connecting Orbimon directly to the Enterprise API, so customers who have it can skip the device. That integration is on the way and isn't available yet.

Picking between them

Rely on the Enterprise API for programmatic access if you qualify and have developers to build and operate the integrations, dashboards, and retention you need on top of the API.

Go with Orbimon if you don't have Enterprise API access, or you'd rather not build operational monitoring from scratch. Once our Enterprise API connection ships, you'll be able to use both together—including alongside Starlink's dashboard when your account has it.

FAQ

Do I need Starlink Enterprise to use Orbimon?

No. Orbimon works today without it, using the device on site.

I already have Enterprise API access. Is Orbimon still useful?

Often yes: even with Starlink's dashboard, Orbimon can add longer history, shareable views, email and webhook alerts in one place, and independence from Starlink for your ops data. The direct API connection is still in progress, so for now you'd use the device.

Does Orbimon store data longer than the API keeps it?

Yes. Daily summaries stay indefinitely and hourly summaries for a year.

Does Orbimon have an API of its own?

Yes. Create API tokens and pull the data into your own tools.

Skip the build

No Enterprise account, no engineering project. Join the beta and see your dishes in Orbimon.

See also: all comparisons

Orbimon isn't affiliated with Starlink or SpaceX. Starlink® is a trademark of Space Exploration Technologies Corp.