robots.txt
See which AI crawlers other sites block →# Content Signals (contentsignals.org): canonical policy preamble, verbatim.
# Directive line follows the User-agent group below.
# As a condition of accessing this website, you agree to
# abide by the following content signals:
# (a) If a content-signal = yes, you may collect content
# for the corresponding use.
# (b) If a content-signal = no, you may not collect content
# for the corresponding use.
# (c) If the website operator does not include a content
# signal for a corresponding use, the website operator
# neither grants nor restricts permission via content signal
# with respect to the corresponding use.
# The content signals and their meanings are:
# search: building a search index and providing search
# results (e.g., returning hyperlinks and short excerpts
# from your website's contents). Search does not include
# providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models
# (e.g., retrieval augmented generation, grounding, or other
# real-time taking of content for generative AI search
# answers).
# ai-train: training or fine-tuning AI models.
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS
# RESERVATIONS OF RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN
# UNION DIRECTIVE 2019/790 ON COPYRIGHT AND RELATED RIGHTS
# IN THE DIGITAL SINGLE MARKET.
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /
# Cloudflare-reserved endpoint. Cloudflare injects hidden, expiring
# /cdn-cgi/content?id=... honeypot links (AI Labyrinth) into served HTML;
# without this rule crawlers fetch them after the id expires and log 404s
# in Search Console. Cloudflare's own docs recommend disallowing /cdn-cgi/.
Disallow: /cdn-cgi/
Sitemap: https://pidgeiot.com/sitemap.xml
llms.txt
Compare with other sites' llms.txt files →# PidgeIoT
> Open-source IoT device management platform: provision devices, push
> configuration through device shadows, collect telemetry with queryable
> history, receive email alerts, and update firmware over the air. Built in
> Rust end to end: the backend runs on Cloudflare Workers + Durable
> Objects, the dashboard is a WASM single-page app. AGPL-3.0 licensed,
> developed in the open, free for up to ten devices.
Devices authenticate with per-device Ed25519 keypairs and compact binary
bearer tokens (not JWTs); refreshing a token cryptographically revokes the
previous one. Supported device transports today: HTTPS, WebSocket, and
CoAP on port 5684, both CoAP-over-DTLS/UDP (the primary transport for
constrained cellular devices) and RFC 8323 CoAP-over-TLS/TCP, each
authenticated by a per-device TLS-PSK, and MQTT 5 or 3.1.1 over TLS on
port 8883, authenticated either by a certificate handshake with the device
token as the CONNECT password or by a per-device TLS-PSK. There is no
cleartext listener on any transport. The device library targets Zephyr
RTOS (vendor-agnostic), with samples for ESP32-C6, Nordic nRF9160/nRF9151,
and a native_sim target that runs the whole platform flow on a desktop
with no hardware, the mqtt_init sample among them: it drives the whole
device-to-platform MQTT path against a broker on the same machine.
## Docs
- [Getting Started](https://pidgeiot.com/getting-started/): zero-to-telemetry
in about ten minutes with a simulated device, no hardware required
- [Documentation](https://pidgeiot.com/documentation/): the connect-a-device
steps, links to the source, and support
- [API Reference](https://pidgeiot.com/api-reference/): the full HTTP
surface: dashboard routes, device routes, auth models, WebSocket frames
(markdown variant: https://pidgeiot.com/api-reference/index.md)
- [Architecture](https://pidgeiot.com/architecture/): how the platform is
built, edge to database
## Stories
- [Stories](https://pidgeiot.com/stories/): field notes from the devices
the platform was built for (markdown variant:
https://pidgeiot.com/stories/index.md; each post has its own at
https://pidgeiot.com/stories/<slug>/index.md)
- [Stop 73: How a Bus Sign Became a Platform](https://pidgeiot.com/stories/departure-board/):
three solar bus departure signs for a transit agency, and the platform
they became the first tenant of (markdown variant:
https://pidgeiot.com/stories/departure-board/index.md)
## Try it
- [Live Demo](https://pidgeiot.com/demo/): real device telemetry, no signup
- [Features](https://pidgeiot.com/features/) and
[Pricing](https://pidgeiot.com/pricing/): ten devices free, paid tiers
priced by what you connect
- [Compare](https://pidgeiot.com/compare/): every IoT platform price we could
verify, per device per month at three fleet sizes, each with its source
and the date we checked it
- [Self-hosting costs](https://pidgeiot.com/self-hosting/): what running
free software on your own server costs once the licence, the box, and
the hours on call are counted
## For agents
- [auth.md](https://pidgeiot.com/auth.md): how an agent authenticates,
covering Kratos account flows, session cookies, device bearer tokens
- [API catalog](https://api.pidgeiot.com/.well-known/api-catalog): RFC 9727
linkset for the API host (also mirrored at
https://pidgeiot.com/.well-known/api-catalog)
## Legal
- [Terms of Service](https://pidgeiot.com/terms/): the agreement for using
the service (markdown variant:
https://pidgeiot.com/terms/index.md)
- [Privacy Policy](https://pidgeiot.com/privacy/): what we collect, where
it is processed, and how long we keep it (markdown variant:
https://pidgeiot.com/privacy/index.md)
- [Data Processing Agreement](https://pidgeiot.com/dpa/): the processor
terms the Terms incorporate, annexes included (markdown variant:
https://pidgeiot.com/dpa/index.md)
- [Sub-processors](https://pidgeiot.com/subprocessors/): every third party
that processes customer data, what reaches it, where, and under which
transfer mechanism (markdown variant:
https://pidgeiot.com/subprocessors/index.md)
## Source
- [pidgeiot](https://github.com/justins-engineering/pidgeiot): the platform
itself, backend, dashboard, shared wire types (AGPL-3.0)
- [pigeon](https://github.com/justins-engineering/pigeon): Zephyr device
library (AGPL-3.0)
- [pigeon-examples](https://github.com/justins-engineering/pigeon-examples):
device samples incl. the no-hardware native_sim variants (AGPL-3.0)
security.txt
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
# PidgeIoT vulnerability disclosure, per RFC 9116.
#
# Two files carry this text. security.txt.unsigned is the source anyone
# edits; security.txt is what the origins serve, either a copy of that
# source or a cleartext OpenPGP signature over it. A dovecote test compares
# their payloads, so the served document cannot drift from the source.
#
# fancier serves it as a static asset, dovecote bakes it into the API
# worker with include_str!, and the status worker imports it as a text
# module, so all three origins answer with the same document. Renew Expires
# before it passes, and re-sign when you do: a security.txt past its own
# Expires is stale by its own terms.
Contact: mailto:security@pidgeiot.com
Encryption: https://pidgeiot.com/.well-known/pgp-key.txt
Expires: 2027-02-26T00:00:00Z
Preferred-Languages: en
Canonical: https://pidgeiot.com/.well-known/security.txt
Canonical: https://api.pidgeiot.com/.well-known/security.txt
Canonical: https://status.pidgeiot.com/.well-known/security.txt
Policy: https://github.com/justins-engineering/pidgeiot/blob/main/SECURITY.md
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQQq3pNoF4pi7pmzVhXd4co86IP3sgUCao+fQAAKCRDd4co86IP3
sqDZAQDqfeUMT8CspThiJlVxKhx+Sn7h/bUrkH0xzbc6NuUaPAD/UvA42a/nGDe/
apA/t/dj5Sw7DR5tzTQl1QdRBON28QM=
=iH/l
-----END PGP SIGNATURE-----