Carrier pigeons for your sensors.
Considerably faster.
An open-source platform that provisions your devices, keeps their config and firmware current, and brings their readings home.
no signup · no hardware · AGPL-3.0
This is the whole dashboard
No modules to buy, no widgets to assemble. Every device shows up here the moment it checks in.
Fleet Overview
42 pigeons across 4 flocks
Fleet Health
Devices
Sorted by status · showing 4 of 42Flocks
View all →Alerts
Per-pigeon alerts aren't counted here — open a pigeon's own page to see those.
Manage alerts in a flock →The whole trip, three stops
Your device
Flash the Zephyr library. Registering the device mints its keypair and hands back a 69-byte token — the private half signs that token and is discarded, so only the public key is ever stored. From there it speaks CoAP over DTLS or plain HTTPS, whatever the modem can afford.
dashboard → Register Pigeon
✓ keypair minted, public key stored
✓ token issued (69 B) — shown once
The edge
Each device owns a small object on Cloudflare's network — its shadow, its permissions, its credentials. Nothing to provision, nothing to patch, close to wherever it wakes up.
You
The dashboard above: graphs, GPS tracks, firmware rollouts, remote logs and alerts by email. Or bypass it — the API the dashboard uses is the API you get.
GET /pigeons/0417/telemetry
200 · [{"key":"temp_c","value":"21.4",
"reported_at":"…"}, …]
Where it earns its keep
Examples, not case studies — we're in beta and we're not going to pretend otherwise.
Vehicle & asset tracking
Tracks drawn from plain GPS telemetry. Alerts when an asset moves — or stops reporting.
Irrigation & soil
Moisture per block, valves as config, a season of battery between visits.
Machine monitoring
Vibration trends, rate-of-change alarms, remote logs when something's off.
Water metering
Small payloads, sent reliably, with history in your own database if you prefer.
Smart parking
Bay occupancy served from the edge nearest each sensor — one object per device, however many there are.
Open, all of it
AGPL-3.0 across the edge router, the dashboard and the device library. No open core with the useful parts behind a sales call.
Browse the repos →Secure by shape
Per-device Ed25519 keys, encrypted transports only, and a token so small it costs nothing to send. One compromised device stays one compromised device.
Security model →Private by default
Send telemetry to your own endpoint and the history accumulates there, not here — we keep only the latest value per key. Dashboard identity is self-hosted, so your credentials don't visit a third party.
How data flows →The long view
Why This Platform
Open-source IoT today makes builders choose: assemble a pile of primitives yourself, or pay enterprise prices for the pre-assembled version. PidgeIoT's bet is that one coherent, AGPL-licensed product — identity, config, firmware, telemetry, and alerts designed together in a single codebase — wins the individual developers that the incumbents price out or wear down. Those developers become the small fleets, and the small fleets become the large ones.
Serverless economics, edge-native by default
The backend runs on Cloudflare Workers and Durable Objects — each device owns its own SQLite-backed object at the edge. No idle servers to pay for, no capacity planning: a fleet of five costs almost nothing to serve, and the same architecture serves a fleet of thousands without a re-platform.
Cryptographic identity per device
Every device authenticates with its own Ed25519 keypair and a 69-byte binary token — no shared secrets, no JWT overhead, and refreshing a token is revocation, because it overwrites the only key the old one could verify against. Dashboard identity is self-hosted Ory Kratos: user credentials never leave infrastructure we control.
Rust and WebAssembly, end to end
The edge router, this dashboard, and the wire types between them are one Rust workspace — the backend compiles to a Worker, the frontend to WebAssembly, and shared structs mean the two cannot drift apart. The protocol itself is the product surface: everything the dashboard does rides the same documented API a device or a script can use.
Next: a user-authored rule engine
PlannedDesigned, not yet built: user-written logic running against incoming telemetry at the edge, on Cloudflare Workers for Platforms — the step from device management to a programmable platform.
PidgeIoT is in beta and pre-revenue, and this page says so. There are no customer logos here because we haven't earned them yet — the public repos, the commit history, and the running product are the evidence. If you're evaluating us, read the code.
Send up your first bird
A real device is already reporting. Ten minutes, no hardware, no card.