Designed for the pilot, not yet shipping

Here is what using
PaaSat actually looks like.

No installer, no dish to point, no site visit. PaaSat is designed to disappear into a machine you already operate or are already building, and to keep it reporting when towers end and GPS can't be trusted.

This page walks through what happens between building a compatible chip into a machine and seeing its data land in your systems. It reflects the design we're building toward for the European pilot described on our status page, not a shipped product.

See the walkthrough Register interest
For machine builders and operators

Five things happen. You do two of them.

Step 01 · Get a device

Start with a standard satellite IoT chip

You either use hardware with a compatible module built in, or add one of the certified modules to a machine you're already building. Nothing here is PaaSat-proprietary.

  • MediaTek MT6825, Qualcomm 9205S or 212S, Quectel BG95-S5, Murata Type 1SC-NTN, Nordic nRF9151, or any 3GPP Release 17 satellite IoT module
  • Building something new? Our developer kit gives you a reference board to start from
  • The same chip works on any compliant network, not only through us
CHIP RELEASE 17 SATELLITE IOT MODULE
Step 02 · Activate once

Register the device against your account

You enter the device's ID once, the same way you'd activate a SIM. That's the entire setup. There's no aligning a dish, no signal-strength dance on a rooftop, no engineer visit.

  • One activation code, tied to one device
  • Works the same for one machine or ten thousand
  • No fixed address required: the machine can move, roam and cross borders
DEVICE ID: PS-4471 ACTIVATED
Step 03 · It connects on its own

Cellular where there's a tower, satellite where there isn't

The same module uses the cellular network when it can and switches to satellite when it can't. You do nothing. If no satellite is overhead, the device holds its data and sends it on the next pass.

  • Runs over partner satellite networks that follow the same open standard, more than one where available
  • No pointing, and no clear-sky requirement the way a dish needs
  • Built for messages, telemetry, position and alerts, not video
DEVICE SATELLITE CELL TOWER GROUND STATION INTERNET
Step 04 · Keeps working under interference · in R&D

Designed to keep reporting when GPS is jammed

Satellite IoT devices use GPS to find the satellite. When GPS is jammed or spoofed, as happens daily around the Baltic, our resilience layer is being designed to keep the link up using other timing and position sources, and to tell you when a reported position can't be trusted.

  • Every position carries a trust flag: confirmed, estimated or suspect
  • Alerts when a device appears to be under jamming or spoofing
  • This is early-stage work. We'll publish test results, not promises
GPS JAMMED SATELLITE DEVICE LINK: UP · POSITION: ESTIMATED
Step 05 · See what is happening

Data lands in your dashboard or your own systems

From your side, it looks like any other device feed. There's a dashboard for a quick look, and an ordinary API if you want the data flowing straight into your own systems, hosted in the EU.

  • Position with its trust flag, status, and any payload the device sends
  • Alerts when a device hasn't reported in longer than expected
  • Which network carried each message: cellular or satellite
DEVICE FEED · EU-HOSTED
What you can do

Everything the link actually carries.

Once a device is activated, this is the full range of what moves across it. Nothing here needs more bandwidth than a narrow chip-scale antenna can deliver.

Send data up

  • Position and movement. Location fixes, each with a trust flag, for anything that roams: drones, vehicles, vessels, rolling stock.
  • Sensor readings. Pipeline pressure, substation status, water levels, power output, on a schedule you set.
  • Condition alerts. Tampering, intrusion, outages, a geofence breach, a low battery.
  • Emergency and SOS. A distress signal from a field crew, a patrol or a vessel outside all other coverage.
  • Check-ins. Proof of life for a lone worker, a patrol or an uncrewed system beyond range.
  • Buffered logs. A device offline for hours sends its backlog in one burst on the next pass.

Send commands down

  • Control commands. Arm or disarm a sensor, switch a valve or relay, trigger an out-of-cycle report.
  • Configuration changes. Adjust a reporting interval or threshold remotely instead of sending someone to the device.

Not full firmware updates, and not real-time control of a drone. The link is narrow by design, so downlink is for commands and configuration, not megabytes of code or live steering.

Fleet and asset operations

  • Fleet tracking. Vehicles, trailers and rolling stock crossing forests, borders and open water.
  • Interference mapping. Where and when your devices met GPS jamming or spoofing, across your fleet.
  • Maintenance scheduling. Usage logs from unattended assets tell you when a visit is due.
Set expectations right

What this is not.

We'd rather you know the shape of the service before you commit a machine to it.

Not broadband

It carries messages, telemetry, position and small payloads well. It doesn't stream video or replace an internet connection.

Not instant everywhere

Between satellite passes, a device holds its data and sends it on the next one. How long that gap is depends on the partner networks available where your machines operate.

Not proven under jamming yet

Keeping the link alive under GPS interference is our core R&D. Until we publish test results, treat it as a design goal, not a feature.

Not hardware we sell you

You bring or build a machine with a standard chip. We provide the developer kit, the connectivity and the platform that gets its data moving.

Next

Tell us what you would connect

The European pilot starts with real machines in real coverage gaps and GPS-interference zones. If this walkthrough matches something you're building or operating, we want to hear about it before we lock the design.

Register interest See project status