Starlink + Cellular Failover in a Portable Case
No single internet path is reliable on its own. Cellular towers overload during disasters; satellite dishes get obstructed by terrain or tree cover. NetCrate's failover architecture treats that as the normal condition to design around, not an edge case to hope doesn't happen.
How the failover actually works
Three carriers running at once
T-Mobile, Verizon, and AT&T SIMs are all active simultaneously, not on standby. The system routes traffic across whichever carrier path is healthiest in real time.
Starlink as a parallel path
When configured, Starlink operates alongside the cellular paths rather than as a manual fallback you have to switch to — it's part of the same failover pool.
Automatic, not manual
Field staff don't toggle between connections. The unit handles path selection on its own, which matters when the person on shift isn't a network technician.
Validated under controlled testing
Failover behavior is part of Nexaer's documented field-test process, not just a spec sheet claim. See field test results for the test plan.
Why diversify across both satellite and cellular
Satellite-only and cellular-only solutions each fail under different, predictable conditions:
| Approach | Where it breaks down |
|---|---|
| Cellular only (single carrier) | Fails when local towers are damaged, overloaded, or that one carrier has poor coverage in the area — exactly the condition during many disasters. |
| Starlink only | Fails when sky visibility is obstructed by terrain, tree cover, or a hasty indoor/covered setup, and offers no backup path during an outage or hardware issue. |
| Cellular + Starlink (NetCrate) | Each path covers the other's weak point — cellular handles obstructed sky, Starlink handles damaged or saturated cellular infrastructure. |
Common questions about failover
Need a configuration recommendation?
Tell Nexaer how your team plans to deploy NetCrate and we'll recommend a self-managed, managed, or evaluation configuration.