Let's say you're deploying a fleet of water-level tank monitors across a giant ranch. Most of the tanks sit within reach of a cell tower, and cellular connectivity handles them just fine. But three of them are on the far side of a ridge where no cell tower reaches, and of course those are the tanks nobody wants to drive out to check!
You could certainly design a different product around satellite (NTN) for those three remote sites. Or, and hear me out, you could add a satellite radio to your existing product and let that one design cover every tank on the property.
While this option is far more practical and cost-effective than it was a few years ago, it certainly isn't free. Satellite data is not nearly as cheap as cellular data, you're capped as to how large each message can be, NTN connectivity can take minutes instead of seconds, and it costs several times more in battery life per sync. Whether it's worth all of these considerations comes down to where your devices live and what they need to send.
Table of Contents
- When Is Satellite Worth Adding to a Cellular Device?
- How Satellite IoT Differs from Cellular
- What Satellite Costs in Battery Life
- Three Ways to Add Satellite with Blues
- Setting Up Satellite Fallback on Notecard
When Is Satellite Worth Adding to a Cellular Device?
Let's start with the tl;dr: keep cellular or WiFi as your primary transport, but
add satellite as a fallback when two things are true:
- The device has to keep reporting from places with no terrestrial coverage, either because it's permanently installed there (e.g. a remote tank, a pipeline valve) or because it passes through there (e.g. a moving trailer, a shipping container).
- The messages it sends are small and delivery does not have to be instantaneous. For instance, a tank level, an alarm, a GPS fix, or a battery voltage reading fits just fine. However, a photo, a video, or a massive log file likely won't.
If either one is false, satellite adds cost and battery drain for very little
gain.
If your deployed device only loses cellular coverage for short stretches, Blues Notecard has ample onboard flash storage and will queue its data and send it once a network comes back, which may be all you need.
| If your device... | Then | Why |
|---|---|---|
| Stays within reach of cellular or WiFi | Skip satellite | Notecard queues JSON-based Notes through short outages and syncs when the network returns. |
| Sits or travels beyond any tower, and sends small readings | Cellular or WiFi first, satellite fallback | Terrestrial networks carry most syncs cheaply, and satellite fills the gaps. |
| Must raise an alarm even when terrestrial networks are down | Satellite fallback for a condensed alert | A small message over satellite is more important than silence. |
| Sends images, logs, or firmware | Cellular or WiFi only | Satellite packet sizes are relatively small, and Notecard's binary APIs don't work over NTN. |
| Needs a fast command round trip from the cloud | Cellular or WiFi only | A satellite sync can take minutes, and every inbound check costs data. |
How Satellite IoT Differs from Cellular
When we talk about satellite connectivity in the IoT, what we really mean is non-terrestrial network (NTN) connectivity, where the device talks to a satellite instead of a cell tower. Our guide to satellite IoT covers the fundamentals, if you're curious. Blues supports two satellite networks, and they differ in where they reach and what they need from the sky.
Skylo runs 3GPP Release 17 NB-IoT over geostationary satellites, so the same modem that speaks cellular can reach its satellites. Skylo satellites are stationary relative to the ground, which means your device antenna needs a clear view roughly toward the equator (i.e. south in the northern hemisphere, north in the southern). Skylo's coverage map lists 41 countries on five continents, and Skylo notes that its coverage isn't complete or uniform (note this was last verified in November 2026, and this will change!).
Iridium is a low Earth orbit constellation about 780 km up in space whose satellites, per Iridium, "cover the entire earth". They move across the sky, so the antenna just needs an open view of the sky in several directions instead of one.
| Skylo | Iridium | |
|---|---|---|
| Orbit | Geostationary | Low Earth orbit (about 780 km) |
| Coverage | 41 countries on five continents | The entire planet, including oceans and poles |
| Sky view | Clear view toward the equator | Open sky in several directions |
| Minimum billable packet | 50 bytes | 10 bytes |
| Maximum packet | 256 bytes | 10,000 bytes up, 340 bytes down |
| Time allowed per connect attempt | Up to 900 seconds | Up to 300 seconds |
| Blues hardware | Notecard for Skylo, or Starnote for Skylo with a paired Notecard | Starnote for Iridium with a paired Notecard |
Is Satellite IoT as Reliable as Cellular?
While satellite is more reliable at reaching a device in the middle of nowhere, the delivery of each individual message is not guaranteed!
Over cellular or WiFi, a Notecard "sync" is a two-way session with Blues Notehub. Over satellite, delivery works more like UDP than TCP: Notehub receives the packets that make it through, and nothing comes back to tell Notecard whether one arrived. Notecard retries when it can't reach a satellite at all, but a packet lost after it's sent is lost in the ether (see our doc on Planning for Data Loss).
Truth be told, it's slower, too! Your mileage may vary, but in our power usage tests a satellite sync took anywhere from 45 to 151 seconds.
What Satellite Costs in Battery Life
That aforementioned power usage estimates guide has satellite power usage measurements for Notecard for Skylo (NOTE-NBGLWX). It syncs over LTE-M or Skylo on the same system-on-module, which makes for a clean comparison between the two networks.
| Notecard for Skylo Power Test | LTE-M | Skylo NTN |
|---|---|---|
| Create and sync one Note | 0.516 mAh | 3.869 mAh |
| Idle for one hour with the modem off | 0.0266 mAh | 0.0267 mAh |
12 hours in minimum mode | 12.23 mAh (syncs every 30 min) | 45.52 mAh (syncs every 60 min) |
A single satellite sync with Notecard for Skylo used about 7.5 times the charge of an LTE-M sync. The satellite figure covers a fixed 15-minute window, since the satellite radio can stay on after a sync, but idle draw is relatively low so the extra minutes add very little.
Idle current is the same on either network (and in line with other Notecards), so the difference lives in the syncs themselves. At four syncs a day, that works out to roughly 2.7 mAh a day on LTE-M and 16 mAh a day on satellite, so a week on satellite costs about as much battery as six weeks on LTE-M. (Which is another good reason to keep cellular as your primary radio anywhere it's available!)
That 16 mAh figure covers successful satellite syncs and idle time only. With
the cell-ntn setup below, a device out of coverage also spends charge on the
cellular attempts that fail before it falls back, and on each retry after that.
We haven't measured those, so measure them on your own hardware before you size
a battery for a site with no coverage.
Three Ways to Add Satellite with Blues
All three options for NTN connectivity with Blues use the same Notecard API and send data through Blues Notehub, so your host firmware doesn't need to know (or care) which network carried the Note. Each device bundles 10 KB of prepaid satellite data, with no subscription or monthly fee.
Notecard for Skylo: One Module for New Designs

Blues Notecard for Skylo puts LTE-M, NB-IoT, and GPRS cellular, Skylo satellite, and 2.4 GHz WiFi on a single M.2 module, with 500 MB of cellular data included. With no second board to mount and no second link to route, it's the simplest choice for a new design deployed in Skylo's covered countries. Meet Notecard for Skylo has a full introduction if you're curious, and you can always order one from the Blues store.
Starnote for Skylo: Skylo for an Existing Notecard
Starnote for Skylo with u.FL connectors (left) and onboard antennas (right)
Blues Starnote for Skylo is a companion board that pairs Skylo with an existing Notecard Cellular or Notecard Cell+WiFi device. Notecard for Skylo's cellular radio only covers LTE-M, NB-IoT, and GPRS, so Starnote for Skylo is how you put Skylo behind an LTE Cat-1 or Cat-1 bis Notecard you already ship. Notecarrier XS has a dedicated slot for it, and on other Notecarriers it can connect by a cable to its 6-pin JST connector. It comes with either onboard antennas or u.FL connectors for the included external ones. The Starnote Quickstart walks through setup, and it sells on its own in the Blues store.
Starnote for Iridium: Pole-to-Pole Coverage

Blues Starnote for Iridium is also a companion board that pairs Iridium with a Notecard Cellular or Notecard Cell+WiFi on a Notecarrier XI. Choose it over Starnote for Skylo when your devices go to sea, are deployed near the poles, or frankly anywhere else Skylo doesn't cover! Pole-to-Pole: Introducing Starnote for Iridium provides more details, and the Starnote for Iridium Starter Kit has everything you need to prototype.
Still deciding between the two networks? Choosing Between Skylo and Iridium compares them side by side.
Setting Up Satellite Fallback on Notecard
Whichever hardware you pick, setup in your device firmware comes down to the same five steps.
Consult Satellite Best Practices as you start developing your firmware. This guide goes deeper on every step and covers what this blog post glosses over!
1. Set the Radio Transport Order
The card.transport API tells Notecard which networks to use, and in what order:
{
"req": "card.transport",
"method": "cell-ntn"
}cell-ntn works on Notecard for Skylo and on a Notecard Cellular paired with
either Starnote. If your Notecard has WiFi, wifi-cell-ntn tries WiFi, then
cellular, then satellite.
Notecard falls back to satellite after two failed cellular attempts (or one WiFi
and two cellular failures with wifi-cell-ntn). It retries cellular at the next
sync after the window set by the seconds argument has passed (an hour by
default), or sooner if a successful satellite connection clears cellular's
failure state. Note that every retry is another cellular connection attempt, so
a device that lives mostly out of coverage may deserve a longer window, though a
successful satellite sync can still trigger a retry before it ends. Be sure to
consult our guide on
Connection Retry and Fallback Behaviors
to review the full "retry" algorithm.
2. Define a Satellite Template and a Cellular Template
Every Note sent over satellite needs a
template with
"format":"compact" and a port from 1 to 100. Compact templates optimize for
size and drop metadata such as the creation timestamp and location (you can add
them back with fields like _time if needed):
{
"req": "note.template",
"file": "tank-ntn.qo",
"format": "compact",
"port": 10,
"delete": true,
"body": {
"level": 14.1,
"seq": 14
}
}The body values are type hints, so level is a 4-byte float and seq is a
4-byte integer (think of it as a sequence number your cloud app can use to spot
a lost packet).
Notecard can't know which network its next sync will use, so don't make your
host firmware guess. Define a second, richer template for cellular and WiFi,
with no format or port defined:
{
"req": "note.template",
"file": "tank.qo",
"delete": true,
"body": {
"level": 14.1,
"temp": 14.1,
"pump_amps": 14.1,
"battery_v": 14.1,
"seq": 14
}
}To put this into practice, your host can add a full reading to tank.qo every
15 minutes, and a compact one to tank-ntn.qo every hour, and "delete":true
on both templates does the work for you.
Before a satellite sync, Notecard clears the queued tank.qo Notes. Before a
cellular or WiFi sync, it clears the queued tank-ntn.qo Notes. It's a bit to
wrap your head around, but our doc on
Defining NTN vs non-NTN Templates
covers these combinations.
Every time you create or change a template, Notecard has to sync once over cellular or WiFi before it can use that template over satellite, so be sure to do that during provisioning (e.g. before the device leaves its cellular coverage zone). Notes in a Notefile without a template will never be delivered over satellite.
3. Keep Every Satellite Note Inside One Packet
The packet maximums
in the table above include a few
bytes of framing, so a Skylo packet carries slightly less than 256 bytes of your
data. A trace log can show you the real
limit for your device, as bytes used out of bytes available (17/254 in this
example), and logs ntn: IGNORING note that is too large for packet when it
drops one:
S07:00.65 ntn: moved 9-byte note (port 55) into packet (17/254)Small Notes can help you in other ways too. When several are queued at sync time, Notecard packs as many as will fit into each packet, which spreads Skylo's 50-byte minimum across all of them.
4. Sync Less Often over Satellite
Two
reserved environment variables,
_sync_outbound_mins_ntn and _sync_inbound_mins_ntn, allow you to override
the hub.set syncing cadence only while Notecard is on satellite. With
outbound set to 60 and _sync_outbound_mins_ntn set to 240, the device
syncs hourly over cellular and every four hours over satellite, with no firmware
change. In our tank example, that also means four hourly readings can share
one packet.
Be sure to set inbound syncs over satellite to a long interval as well. Each inbound check uses about 50 bytes, even when nothing is waiting in Notehub.
5. Test the Cell to NTN Fallback Before You Ship
You don't have to wait for a real outage to watch the fallback work. The following card.io request tells Notecard to treat cellular and WiFi as already failed, so every sync goes over satellite:
{
"req": "card.io",
"mode": "+fallback"
}This setting persists across restarts, so while it's handy when testing on the
bench, it's potentially expensive if it ships. Send "mode":"-fallback" as part
of your provisioning process.
Develop and Test Without Satellite Coverage documents additional ways to test NTN connectivity.
Summary
In summary, you're going to want to add satellite connectivity when a device must keep reporting from beyond the reach of any cell tower (and its messages can be small and a few minutes late!). Everywhere else, cellular or WiFi does the job for a fraction of the battery and data.
To see the whole pattern in working code, the Off-Grid Livestock Water Tank Monitor accelerator is a complete open source build on Notecard for Skylo, with the firmware, wiring, and Notehub setup for cellular with satellite fallback. The Untethered Trailer and Chassis Fleet Tracker does the same with Starnote for Iridium. Start from whichever one matches your hardware and swap in your own sensors.
Happy hacking! 💙
Frequently Asked Questions
When should an IoT device use satellite instead of cellular?
Almost always alongside cellular, not instead of it. Add satellite when the device has to report from places with no cellular or WiFi coverage, and when its messages are small and can wait a few minutes. Keep cellular or WiFi as the primary transport: on Blues Notecard for Skylo, a satellite sync measured about 7.5 times the charge of an LTE-M sync, and every satellite packet is billed. Blues documents NTN-only mode as a testing mode, and satellite templates need one cellular or WiFi sync before the device can use them.
Is satellite IoT connectivity reliable compared to cellular?
Satellite reaches places cellular can't, but each message is less certain. On Blues hardware, satellite delivery works more like UDP than TCP: Notehub receives the packets that arrive, nothing confirms delivery back to the device, and a lost packet isn't re-sent. The antenna also needs a clear view of the sky, and a satellite sync can take minutes. Design for occasional loss with sequence numbers and readings that stand on their own.
Is satellite backup an option for critical IoT devices?
Yes, for small, critical messages such as alarms and heartbeats, when the
alternative is silence. Configure cellular or WiFi first and satellite last (for
example, card.transport with cell-ntn), send a compact satellite-only
version of the alert, and repeat important state in later messages, because
satellite delivery isn't acknowledged. Don't rely on satellite for large data,
firmware updates, or commands that need a fast round trip.
How large can a satellite IoT message be?
On Skylo, each packet is billed at a minimum of 50 bytes and can be at most 256 bytes. On Iridium, the minimum is 10 bytes, and the maximum is 10,000 bytes to the satellite and 340 bytes from it. Those maximums include a few bytes of framing. On Blues Notecard, a Note larger than one packet is dropped without being sent and without an error, so keep satellite templates small.
How much satellite data comes with Blues hardware?
Notecard for Skylo, Starnote for Skylo, and Starnote for Iridium each include 10 KB of satellite uplink and downlink data, with no subscription or monthly fee. Additional data is billed per byte, at the rates listed in each product's datasheet. At Skylo's 50-byte minimum, 10 KB covers about 200 minimum-size packets.

