The terminal just "went offline."
You learn about it from the customer. The battery was draining for six hours and the first signal you got was a dead link. Every minute after that is reactive.
A terminal is only as alive as the battery under it. Orbita Power brings the Tesla Powerwall and solar array at every remote site onto the same screen as connectivity — so a site that's about to go dark is a number on the dashboard, not a 2am phone call.
At a remote site, the terminal doesn't fail because Starlink failed. It fails because the Powerwall hit reserve at 3am, the grid never came back, and solar won't catch up until sunrise. Connectivity monitoring sees the symptom — an offline terminal — hours after the cause was a falling number you couldn't see.
You learn about it from the customer. The battery was draining for six hours and the first signal you got was a dead link. Every minute after that is reactive.
State of charge crossed the floor, the site islanded, autonomy dropped below eight hours — and an alert fired while the link was still up. You dispatch, or shed load, before anything goes dark.
Pulled from the Powerwall and site controller every few seconds, normalized into the same health model Orbita already uses for connectivity. Same colors. Same definition of "fine".
The headline number. How much usable energy is left, right now, as a percentage.
The floor you set to protect the terminal. We alert before the battery touches it — never after.
Generation from the site array in kilowatts — the only thing keeping an islanded site alive.
What the Starlink terminal and site gear actually draw — the demand side of the equation.
On-grid or islanded. The moment a site loses utility power and runs on battery alone, you know.
Hours of runtime left at the current draw, recomputed continuously. The number that tells you when to act.
Pack thermals, so a battery running hot in the desert sun surfaces before it derates.
Capacity retention and charge cycles over the pack's life — the slow signal for planned replacement.
Orbita Power reads each site's Powerwall the same way Orbita already reads its terminals — through the supported battery system's API — and folds energy into the fleet model you already operate.
Authorize the site's battery system once. Orbita pairs each Powerwall to the terminal it backs, so power and connectivity share one site identity.
Choose a backup reserve per site — the state of charge that keeps the terminal protected. Orbita watches the gap and warns before the battery reaches it.
Battery, solar and link sit in the same NOC. A power alert fires while the terminal is still online — so you dispatch, shed load, or reassure a customer ahead of the dark.
Fleet power overview — every site's state of charge, solar input, terminal load, grid status and projected autonomy, with a live power-flow read for any site you select. Dark, dense, calm until something needs you.
Added to any connectivity plan, per site with a linked battery. No new console, no separate login — it turns on inside the fleet you already run. Included free on Mobility Priority.
30-minute demo with a real operator. We'll show you the power surface, a site islanding live, and an autonomy alert firing before a terminal goes dark. Bring your fleet size and we'll price it.