Designed for the pilot, not yet shipping

Here is what using
PaaSat actually looks like.

No installer, no dish to point, no site visit. A PaaSat connection is designed to disappear into a device you already own or are already building.

This page walks through the four things that happen between unboxing a device and seeing its data land in your dashboard. It reflects the design we are building toward for the pilot described on our status page, not a shipped product.

See the walkthrough Register interest
For device owners

Four things happen. That is the whole setup.

Step 01 · Get a device

Start with a device that already has the chip

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

  • MediaTek MT6825, Qualcomm 212S, Qualcomm 9205S, or any Rel-17 IoT-NTN module
  • The same chip works with any compliant network, not only ours
  • No dish, no external antenna to mount
CHIP R17 IOT-NTN MODULE
Step 02 · Activate once

Register the device against your account

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

  • One activation code, tied to one device
  • Works the same whether it is one device or ten thousand
  • No fixed address required, the device can move after activation
DEVICE ID: PS-4471 ACTIVATED
Step 03 · It connects on its own

The device finds a satellite by itself

Whenever a satellite passes overhead, the device's radio talks to it automatically. You do nothing. If the device is between passes, it holds its data and sends it on the next one.

  • No pointing, no clear-sky requirement the way a dish needs
  • Traffic lands at a ground station, then reaches the open internet
  • Built for messages, telemetry and position, not video streaming
DEVICE SATELLITE GROUND STATION INTERNET
Step 04 · See what is happening

Data lands in your dashboard or your own systems

From your side, it should look like any other device feed. There is a dashboard for a quick look, and an ordinary API if you want the data flowing straight into your own systems.

  • Position, status and any payload the device sends
  • Alerts when a device has not reported in longer than expected
  • Same feed whether you are watching one device or thousands
DEVICE FEED
What you can do

Everything the network actually carries.

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

Send data up

  • Position and movement. Periodic location fixes for anything that roams: bikes, trailers, containers, boats, livestock.
  • Sensor readings. Soil moisture, tank levels, water quality, solar output, borehole flow, on a schedule you set.
  • Condition alerts. A cold-chain excursion, a broken container seal, a geofence breach, a low battery.
  • Emergency and SOS. A distress signal from a field researcher, a maritime crew, or a reporter outside all other coverage.
  • Check-ins. Proof of life for a lone worker or patrol, or a gig worker signaling availability outside cellular range.
  • Buffered logs. A device offline for hours or days sends its backlog in one burst on the next pass.

Send commands down

  • Control commands. Open or close an irrigation valve, arm or disarm a sensor, 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. The link is narrow by design, so downlink is for commands and configuration, not shipping megabytes of new code over the air.

Fleet and asset operations

  • Fleet tracking. Couriers and trailers that spend most of a route outside tower range.
  • Custody handoffs. Container seal status as goods move through a supply chain.
  • Maintenance scheduling. Usage logs from unattended solar or pump installations tell you when to visit.
Set expectations right

What this is not.

We would rather you know the shape of the service before you commit a device to it.

Not broadband

It carries messages, telemetry, position and small payloads well. It does not stream video or replace a home internet connection.

Not instant everywhere

Between satellite passes, a device holds its data and sends it on the next one. Early in the constellation's build-out, that gap can run from minutes to longer, and shrinks as more satellites join.

Not a device we sell you

PaaSat is the network, not the hardware. You bring or build a device with a compatible chip, and we get its data moving.

Next

Tell us what you would connect

The pilot starts with real devices from real coverage gaps. If this walkthrough matches something you are building or operating, we want to hear about it before we lock the design.

Register interest See project status