Protected area
Network administration
The key stays in this tab’s memory only until you reload the page.
Not signed in
OPEN RADIO NETWORK. BUILT TOGETHER.
Infrastructure that keeps transmitting.
An open radio network for sensors, trackers and shared coverage.
THE NETWORK / LIVE
Map layer
Time range:
Time range
My devices
Map legend & measurements
PAUL reception, best signal:> −100 dBm−100…−110−110…−120< −120 · zoomed out as hexagons, number = receptions tracker was there, no PAUL reception (“Coverage” view only)
PAUL node density
obscured node position within its actual hexagon
GPSRTK node with its own GNSS receiver (GPS) or RTK station (RTK)
two-way node reception
Hexagons show reported data in the selected time range. Small cells are difficult to see at world scale — zoom in to inspect them. Blue dots in “Node hexagons” mark public node positions.
Loading coverage…
Loading radio evidence…
Mutual beacon receptions add mapping evidence at the participating node locations. The area between the nodes has not been fully measured. Based on available link records within the selected time range.
About this map & privacy
Coverage shows recorded radio reception. Gold cells show historical GPS visits; node hexagons show infrastructure, not guaranteed coverage. Last locations are approximate stored positions, not live tracking.
USE CASES
About the animation & timing
Slowed down to explain · not a live timing measurementA radio packet takes milliseconds to seconds, depending on settings. A location update also depends on getting a GPS fix, the reporting interval and processing.
T1000 documentation ↗
How soon will I see a new location?
PAUL has no measured fixed end-to-end delay yet. The T1000 defaults to a GPS search timeout of 60 seconds; the search may also end without a fix. Without radio reception, no new location reaches the app.T1000 documentation ↗
01 / 05
Connected together.
01 —
Run a gateway
Give your LoRa gateway a new role. Build coverage with people in your region.
Connect a gateway →02 —
Connect sensors
Bring environmental measurements and device data into your own network workspace.
My devices →03 —
Test your range
Explore recorded radio reception and share approximate tracker locations when you choose.
Explore the map →Transparent measurements
Every contact is traceable.
Technical details for anyone who wants to take a closer look.
| Node | Status | Version | Position | Radio contacts | Last seen | Actions |
|---|
| Sent | Sender | Sequence | Result | Received by |
|---|
| Received | Sender | Receiver | RSSI | SNR | Data rate |
|---|
My network
Your gateways, trackers and sensors in one place.
Already installed your gateway? Open My network, create an account or sign in, then link your gateway using its EUI and your PAUL invite. Manage names, locations, antennas, visibility, trackers and sensors in one place.
The PAUL principle
Radio range becomes a verifiable network.
PAUL doesn’t just check whether a node exists. It shows which devices really hear each other — and how stable those links are.
Broadcast identity
Each node regularly broadcasts a cryptographically signed LoRa beacon.
Record reception
Other nodes receive the signal and sign their witness report.
Keep infrastructure running
Existing gateways get a new job instead of being shut down.
Status · autumn 2026
Further than planned.
And still moving.
What was a plan not long ago now runs on the network: an encrypted messenger, remote updates, GNSS positions and trackers in your own account.
PAUL Messenger
Encrypted messages sent directly between gateways over LoRa, independent of LoRaWAN. Running on almost every node since version 1.0.1.
Remote updates
Nodes are updated centrally, with checks and automatic rollback. Pi-based gateways come with their own Wi-Fi hotspot.
GPS, RTK & trackers
Nodes with GNSS and RTK base stations. Pair a SenseCAP T1000 or Dragino LBT1 with your own network, including battery, temperature and light.
Mesh, sensors & new regions
Relay messages across several gateways, pair sensors directly and prepare PAUL for US915/AU915.
Community · Get involved
Bring your gateway into the PAUL Network.
The gateway platforms tested so far already run PAUL. Join us on Discord, tell us your device and get the right invite and installation path. Before installing, there is one required step for every gateway: prepare the packet forwarder.
Open Discord →
Community, installation help and new test locations.
Tell us your device model to receive the appropriate PAUL invite and instructions.
Set the UDP forwarding destinations. This step currently applies to every supported gateway.
Connect over SSH, obtain root access if needed and run the installation command for your device.
Link your gateway using its EUI and PAUL invite, then manage its location, antenna, trackers and sensors.
REQUIRED · EVERY GATEWAY
Before you install PAUL
Prepare the packet forwarder
The PAUL installer currently requires you to configure the forwarding destinations yourself. Set forwards_to manually before installation.
1
Open the Crankk dashboard
In your browser, open http://GATEWAY-IP:17080 . 17080 is the web interface port, not a password.
2
Open Setup Gateway
If prompted for a username and password and you have not configured credentials yourself, leave both fields empty and press Enter. On the first page, select Setup Gateway .
3
forwards_to replaceReplace the existing content with exactly these four destinations:
127.0.0.1:1700,127.0.0.1:1680,127.0.0.1:1701,89.58.0.27:1700
4
Save and wait for the restart
Save the settings. The gateway or forwarder will restart. Wait until the device is reachable before continuing.
Note: This does not open router ports. Three destinations point to
127.0.0.1 and stay local to the gateway. The fourth, 89.58.0.27:1700, sends radio packets to the PAUL server – the gateway only sends outbound.Tested on PAUL
Supported hardware
These platforms have been tested with PAUL. Use the instructions for your device and its existing packet forwarder.
Pi-based Crankk gatewaysRAK V2 / MNTD · SenseCAP M1 · Finestrasupported
Every Raspberry Pi based gateway running Crankk installs the same way: sign in over SSH as crankk, switch to root with sudo -i and run the PAUL installation command. These devices also get the PAUL Wi-Fi hotspot.
RAK V2 / MNTD with Crankksupported
On a RAK/MNTD system running Crankk, sign in as crankk .
ssh crankk@GATEWAY_IP
Then:
sudo -i
Your shell should now look similar to this:
root@raspberrypi:~#
Then run your individual PAUL installation command.
SenseCAP M1 with Crankksupported
On SenseCAP M1 running Crankk, sign in as crankk .
ssh crankk@GATEWAY_IP
Then:
sudo -i
Then run your individual PAUL installation command for the SenseCAP M1 profile.
Finestrasupported
The Finestra setup tested with PAUL is Raspberry Pi based. After connecting over SSH, install PAUL from a root shell as on other Pi based platforms.
Then run the PAUL installation command for Finestra.
Other Crankk gatewaysPanther X2 · Bobcat 300 / Linxdot · Browan MerryIoTsupported
Panther X2 with Crankksupported
On Panther X2, sign in as admin and switch to root.
ssh admin@GATEWAY_IP
Then:
sudo -i
Your shell should now look similar to this:
root@Panther-X2:~#
Then run your individual PAUL installation command.
Bobcat 300 / Linxdot with Crankksupported
Bobcat 300 and Linxdot use the same PAUL installation procedure. For the tested Crankk/Buildroot setup, sign in as crankk :
ssh crankk@GATEWAY_IP
This setup normally opens a root shell directly:
[root@crankk-XXXXXXXX ~]#
An additional sudo -i is normally not required here.
Then run the PAUL installation command generated for the Bobcat/Linxdot Buildroot profile.
Browan MerryIoTsupported
Prepare the tested Browan MerryIoT setup using its existing SSH access . Use the SSH credentials configured on your device, then switch to the root environment required for installation.
Then run the PAUL installation command for MerryIoT.
Raspberry Pi + SX1262 HAT (DIY)Raspberry Pi 3B · 4B · 5 · Zero 2 W · Compute Module 3/4/5Beta
A DIY build from a Raspberry Pi and a LoRa HAT with an SX1262. This path is still in beta: there is no Crankk dashboard, so we set it up together with you.
Tell us your Pi model and HAT on Discord to receive your invite and installation steps.
Other platformsClodPi Pro · SenseCAP M1 with Balenasupported
ClodPi Prosupported
ClodPi Pro is integrated with PAUL. Crankk is not required. Use the existing SSH access and the root environment configured for your device.
Before installing, check the existing packet forwarder and its local forwarding settings. The Crankk dashboard instructions above apply only to devices with that interface.
Use the individual PAUL installation command supplied for ClodPi Pro, taking the existing LoRaWAN services into account. Afterwards, check that the node appears online in PAUL and radio reports arrive.
SenseCAP M1 with Balenasupported
SenseCAP M1 without Crankk runs on Balena. PAUL is set up through the Balena fleet instead of SSH. Get in touch on Discord for this.
FreedomFi (x86)FreedomFi FFG-HL-4-64 · Ubuntu x86_64 · SX1302 USBBeta
For gateways in the USA (US915). The FreedomFi runs Ubuntu on an Intel processor (x86_64) and has an SX1302 concentrator on USB. There is no Crankk dashboard: PAUL ships its own x86 installer, which sets up the Semtech packet forwarder, the PAUL node and forwarding to ChirpStack.
You receive the invite and installation command for the device “FreedomFi (x86)” from us. You do not need to know the gateway EUI, the installer reads it from the chip. Sign in via SSH and run the command:
curl -fsSL https://node.paulnetwork.io/install-x86 | sudo bash -s -- --invite PAUL-XXXX-XXXX-XXXXAt the end the installer shows the gateway EUI. Use the EUI and the invite to add the gateway under “My network”.
Update an existing nodeOlder version, e.g. 0.5.x · one command · no new inviteno invite
If your node still runs an older version (for example 0.5.x), one command brings it up to date. No new invite is needed: keys, name and map position are kept, and future updates arrive automatically afterwards.
Sign in to the gateway via SSH (Pi-based Crankk gateways: as crankk, then sudo -i) and run:
curl -fsSL https://node.paulnetwork.io/install | sudo sh -s -- --updateBobcat 300 / Linxdot (you are already root there):
curl -fsSL https://node.paulnetwork.io/install | sh -s -- --updateThe script also checks the radio forwarding to PAUL and restarts the packet forwarder.
At the end it shows “Semtech UDP / gateway connection: PASS”. A few minutes later the dashboard shows the new version. Not for SenseCAP M1 with Balena or FreedomFi, which have their own paths.
Terms
Invite, SSH and “My network” are separate steps.
PAUL inviteA time-limited invitation to install and later link your gateway.
SSH / RootLocal access to your gateway. The username depends on the platform.
Packet ForwarderForwards radio packets to the required services: three local
127.0.0.1 destinations plus the PAUL server. All four currently need to be configured manually.My networkYour account area for gateways, location and antenna settings, trackers and sensors.
Keep invites and credentials private. If installation fails, save the terminal output and ask for help on Discord before retrying.
Community powered
What should your gateway make possible tomorrow?
A garden sensor. A tracker on the move. A new test location. Bring your use case and honest feedback. Together we can put existing hardware to work and build something useful.
COMMUNITY
RADIO
PILOT
RADIO
PILOT