We're looking for beta testers.

Guide

Concepts

Glossary of organization roles, monitors, Edge, tokens, alerts, and retention.

Short definitions for Orbimon terms. Each section links to the guide or API page with full detail.

Organization, members and roles

An organization is your team account. Every monitor, member, token, and audit event belongs to one organization. Owners, admins, and members share dashboards; owners and admins manage settings.

ActionOwnerAdminMember
Add, remove, or change member rolesYesYesNo
Create or revoke service tokensYesYesNo
Create a monitorYesYesYes
Delete a monitorYesYesNo
Rotate a monitor tokenYesYesYes, if you own the monitor
Change Starlink alerts settingsYesYesNo
View or export the audit logYesYesNo
Delete the organizationYesNoNo

See Organization and Organizations API.

Monitor

A monitor is one Starlink connection at a site. You name it in the app, link an Orbimon Edge with a monitor token, and view charts and alerts for that link only.

See Monitors and data and Monitors API.

Orbimon Edge

Orbimon Edge is software on a Raspberry Pi 4 or Raspberry Pi 5 on your local network. It reads the Starlink dish over the LAN, sends telemetry to Orbimon, and serves a local dashboard at http://orbimon-edge.local after setup. The image is generic; you tie it to a monitor with the monitor token.

See Install Orbimon Edge and Edge API.

Tokens

Orbimon uses three API token types:

TokenPrefixScope
Monitor tokenomb_mon_One monitor only; used by the Edge for ingest
User tokenomb_user_Personal access at your organization role
Service tokenomb_svc_Organization automation with read and optional write

Owners and admins create service tokens on the Organization page. Each user creates their own user token under Settings, then Account.

See Organization and API overview.

Upload interval

The upload interval is how often the Orbimon Edge sends a batch of readings to Orbimon. Edge still samples about once per second; the upload interval is the batch cadence. On Billing, each monitor lists its upload interval.

Orbimon reuses monitor data until the next upload can arrive, so charts and API responses are at most about one upload interval old, and refreshing faster does not show newer readings.

See Upload interval and Monitors and data.

Outages, micro-outages and Edge offline

A Starlink outage is a dish disconnect that lasts longer than your Starlink outage alert threshold. An Edge offline alert means Orbimon has not received ingest from the Edge within your Edge offline threshold. Micro-outages are shorter Starlink drops below your outage threshold; they can appear on the timeline and in the daily digest without a real-time outage alert.

Minimum outage alert thresholds depend on each monitor's upload interval. Orbimon uses one outage duration for both Starlink silence and missing Edge uploads: at least 1.5× that monitor's upload interval (rounded up). Stored thresholds below that floor are not valid after you slow the upload interval.

See Starlink alerts and Alerts API.

Starlink alerts cover long Starlink outages, Edge offline, and an optional daily digest. Profiles bundle settings and optional dedicated email or webhook channels; you assign a profile per monitor and override individual monitors when needed.

Real-time alerts can use email and webhook. The digest is email only. Orbimon sends the digest at 07:00 UTC each day for the previous UTC calendar day, including micro-outages below your outage threshold plus dish restarts and firmware updates when enabled.

See Starlink alerts.

Audit log

The audit log records successful changes to your organization (membership, tokens, alerts, monitor tokens, and more). Failed attempts are not stored. Owners and admins can filter events and export a CSV.

See Organization and Audit log API.

Retention and offline buffering

Orbimon keeps telemetry at several resolutions:

DataRetention
Per-second samples30 days
1 minute rollups90 days
Hourly rollups365 days
Daily rollupsKept indefinitely
Dish events and speed tests365 days
Obstruction maps180 days

If the Edge loses internet, it buffers readings locally and uploads when the link returns. Orbimon Edge holds about 7 days of compressed data on the SD card before the oldest buffered points are dropped.

Where your data is stored

Orbimon stores your data in the European Union, in Germany. Every reading is also copied to a fallback region, also in Germany. If the main region has trouble, Orbimon keeps serving your data from the fallback region and says so on status.orbimon.com. Retention is the same in both regions.

See Monitors and data and Install Orbimon Edge.