Myriota is useful for comparing proprietary satellite IoT with standardized NB-IoT NTN. Its UltraLite and HyperPulse services use different orbital and radio architectures, so the note treats them separately rather than calling both one LEO constellation.
Reviewed October 30, 2026. Dates distinguish operating services, launch announcements and future plans. Published capacity figures describe their stated configuration; they are not guaranteed performance for every terminal.
Contents
- Executive Summary
- UltraLite and HyperPulse Are Different Networks
- RF Details, Expansion and Application Design
- Reference
Executive Summary
The table separates the service, orbit and technical distinctions used throughout this note.
Topic | Summary |
|---|---|
UltraLite | Proprietary LEO satellite IoT |
HyperPulse | GEO / Viasat, Release 17 NB-IoT NTN |
Traffic | Small telemetry messages and device commands |
2026 expansion | Four additional UltraLite satellites announced July 9 |
UltraLite and HyperPulse Are Different Networks
Myriota serves low-power IoT through two distinct network designs. UltraLite uses LEO satellites and a proprietary radio system. HyperPulse uses GEO infrastructure and standardized NB-IoT NTN, so one orbit description cannot cover both services.
UltraLite for small, delay-tolerant reports
UltraLite targets low data volumes and long unattended operation. Its developer comparison identifies proprietary LEO access, with different VHF/UHF service variants. The device and service variant determine which radio configuration is relevant. [1]
A stationary tank sensor may prefer low energy use over immediate delivery. It can timestamp a reading and wait for a useful transmission opportunity. That is a reasonable design only when the application tolerates the resulting message age; it is unsuitable for a tight real-time control loop without another communication path.
HyperPulse and Release 17 NB-IoT NTN
HyperPulse uses Viasat GEO satellites and 3GPP Release 17 NB-IoT NTN. The January 2026 network overview identifies two-way messages up to 250 bytes and a delivery-latency description of up to 30 minutes. This is IoT messaging, not NR broadband. [2]
Figure 1. Rows compare functional roles or dated states. Boxes are explanatory and are not a measured traffic trace.
The overview also describes coordination with a beam schedule. GEO visibility therefore does not imply continuous immediate transmission by every terminal. A stationary satellite and a scheduled service can coexist: the radio resource available to a particular area can vary over time.
Using a cellular-capable chipset does not make every firmware revision compatible with the service. The published overview names the nRF9151 revision A1A as an initial compatible module. Product selection must include approved hardware, software and network provisioning, not simply the semiconductor family name. [2]
RF Details, Expansion and Application Design
The Myriota comparison is most useful when spectrum and application behavior are considered together. A different radio service can change the antenna, power budget, message timing and hardware support even if the application payload stays unchanged.
Documented service variants
The developer network comparison separates two UltraLite spectrum variants and identifies HyperPulse with band n255. These are service-specific descriptions; a terminal should not be configured by combining the ranges into one assumed universal radio. [1]
Service | Uplink | Downlink |
|---|---|---|
UltraLite Service 1 | 160.975–161.475 MHz | 400.15–401 MHz |
UltraLite Service 2 | 399.9–400.05 MHz | 400.15–401 MHz |
HyperPulse | n255 service configuration | n255 service configuration |
The table does not assert permission to transmit throughout each band in every country. It identifies the documented network choices. Device certification, service provisioning and local authorization remain separate from the radio's tuning capability.
Constellation growth and delivery checks
Myriota announced four additional UltraLite satellites on July 9, 2026. This is a dated expansion milestone, not the total current fleet. The same announcement distinguishes UltraLite LEO service from HyperPulse's hybrid cellular and GEO offering. [3]
An application should measure end-to-end delivery at the required percentile, not only compare median latency. Record sampling time and arrival time, and decide how to handle stale data. Commands also need application-level confirmation when a missed action has operational consequences. Network receipt alone does not confirm that an actuator executed a command.
Battery life depends on sensor sampling, GNSS use, radio attempts and sleep behavior. A small daily payload may still cost substantial energy if the device repeatedly searches under poor sky visibility. Test the complete installation and reporting policy rather than copying a headline lifetime from another use case.
Reference
Primary sources used for this note are listed below. Any limited source review is identified explicitly; general engineering explanations and illustrative calculations are not vendor performance measurements.
[1] Myriota Networks : Developer comparison, including service-specific RF ranges. Reviewed October 30, 2026.
[2] HyperPulse Network Overview : January 19, 2026; NB-IoT NTN, payload, scheduling and delivery description.
[3] Myriota constellation expansion : July 9, 2026 operator announcement.