PaaSat keeps Europe's critical machines connected when the towers end and GPS can't be trusted. Standard satellite IoT chips, any compliant satellite network, one secure European platform.
No dish. No install. No dead zones. Built in Estonia, where GPS jamming is a daily fact of life, not a scenario on a slide.
The machines that keep Europe running are often exactly where the network is weakest, and where GPS is under attack.
A pipeline sensor, a border drone, a buoy in the Baltic or a repair crew's tracker loses its link the moment it leaves tower range. Satellite IoT fixes that, with one catch: today's satellite IoT devices use GPS to find the satellite. Jam or spoof GPS, and the satellite link can fail too.
Cellular coverage is planned around people, not around pipelines, forests, borders and open water. Critical assets go silent exactly where they're hardest to reach.
Of aircraft over Estonia, Finland and Kaliningrad report GPS interference on a given day. Jamming blocks the signal; spoofing fakes it. Experts advise critical infrastructure to plan for periods without reliable satellite navigation.
Source: ERR News, May 2026
Moving from a dish to a chip doesn't simply shrink the hardware. It changes what the link can carry, and therefore what the service is for. We'd rather be straight about that than sell you a number we can't hit.
A parabolic antenna concentrates a satellite signal roughly 3,000× more than a chip-scale antenna can. That gain is what makes broadband possible.
A chip antenna has almost no gain, so the link is narrow by design. It carries what critical machines actually need, and it lives inside the machine.
So we don't quote peak speeds. If you need live video from a drone, you need a different link. If you need ten thousand machines that report in when towers and GPS are gone, that's us.
We don't make chips, and we aren't starting by launching satellites. We build the layers that make standard satellite IoT dependable for machines that can't afford to go dark.
3GPP Release 17 made satellite IoT part of normal cellular technology. Modules from MediaTek, Qualcomm, Quectel, Murata and Nordic already support it, so device makers keep their chips, software and supply chain.
Our R&D focus: keeping the satellite link working when GPS is jammed or spoofed, using other sources of timing and position, and flagging location data that can't be trusted. This is early-stage work, and we'll say so until it's proven.
Cellular where there's a tower, satellite where there isn't, across more than one satellite operator. Because the standard is open, your hardware is never locked to us or to any single network.
Device management, failover rules and data delivery from one EU-hosted platform, reaching your systems through an ordinary API. From your side it looks like any other device feed, one that keeps reporting when others stop.
| Option | What the device needs | Works beyond towers | Built for | Trade-off for critical machines |
|---|---|---|---|---|
| Traditional broadband | Router or SIM | No | Homes, offices, towns | Stops at the last tower |
| Satellite dish (e.g. Starlink) | Dish terminal and power | Yes | Broadband and video | Too big, power-hungry and costly for sensors |
| Direct-to-cell for phones | Phone SIM | Yes | Phones first | Not designed or priced for machines |
| Legacy satellite IoT | Proprietary modem | Yes | Niche tracking | Locked to one vendor; costly modules |
| Standard satellite IoT networks | Standard chip | Yes | Phones, cars, global enterprise | Relies on GPS; not built around jamming |
| PaaSat | Standard chip | Yes | Critical machines | Small data only, by design |
Each of these works where coverage is thin, and each matters most on the day something else has failed.
Pipelines, power lines, substations, water pumps. Remote assets that need to report faults even when local networks are down.
Border sensors, perimeter monitors and field units that must keep reporting under jamming.
Uncrewed systems that fly, drive or dive beyond cellular range and still need to check in.
Vessels, buoys and offshore equipment across the Baltic and beyond, where towers simply don't reach.
Fleets, trailers and rolling stock crossing forests and borders, where routes have gaps and position must be trusted.
Equipment and crews that keep reporting during storms, outages and crises, when terrestrial networks are the first thing to fail.
The Baltic region is where connectivity and GPS failures meet every day. If it works here, it works anywhere.
We're starting with European hardware makers and operators of critical assets, testing in the conditions that make this problem real. Estonia's engineering talent and its focus on resilience and defence make it the natural place to build.
Europe is where we prove it. Once it's proven, the same standard and the same platform can serve machines anywhere that coverage ends.
Satellite companies are unusually prone to describing plans as products. This page is the antidote. It's dated, it's specific, and it includes the parts that aren't finished.
Last updated 9 November 2026. If something on this list stops being true, it changes here first.
If you've designed against 3GPP Release 17 satellite IoT, you've already done the hard part.
Certification is portable: a device certified for Release 17 satellite IoT works on any compliant network. That means no lock-in to us, and no bespoke integration work to try us. We think that's the only honest way to ask a hardware team to bet on a new provider.
Modules we're targeting for compatibility:
The developer kit comes first, then device APIs and a sandbox. If you're building hardware that has to keep working beyond coverage or under jamming, tell us what it is. That shapes what we build first.
There's nothing to buy yet, and we'd rather not pretend otherwise. But if you build or operate machines that lose signal, or lose GPS, we want to hear about them. That decides what we build first.