The AIoT platform
for connected products
Everything under a connected product, as building blocks behind one API: device management and over-the-air updates, ingestion and storage, assets and metrics, alarms, analytics and serverless jobs. Your data stays yours, and you can always take it with you.
Building blocks
Use one, or all of them. Each has its own API and works without the others, the way WorkOS made enterprise features an afternoon's work.
Devices
Identity, provisioning and a registry for every device, from microcontrollers to gateways, with twins, commands and remote configuration.
Certificate authority
A certificate for every device without a PKI team: issued at the factory, renewed automatically, revoked with the device, under our root or yours.
Cellular connectivity
SIMs and eSIMs managed next to the devices they're in, with connectivity providers such as Teal: usage, cost, and carrier changes rolled out like updates.
Over-the-air updates
Signed updates for any device: firmware on microcontrollers, A/B images on Linux, containers, files and ML models, rolled out in waves.
Ingestion
MQTT, Sparkplug B, HTTP, CoAP and LwM2M from devices, OPC UA and Modbus through an edge gateway, and streams from Kafka and other clouds.
Storage and retrieval
Time series kept as open Apache Iceberg tables with timelake, in our bucket or yours. Query by device or by asset, with SQL or the API.
Assets and bindings
Model the machines, rooms and vehicles your devices measure. Bind devices to them over time, so history survives a sensor swap.
Metrics
A catalog of what every number means: unit, definition, owner and lineage, computed from measurements, formulas, rollups or jobs.
Alarms
Rules on metrics, defined once per asset model, with an ISA-18.2 lifecycle, flood suppression, and notifications where your team works.
Analytics and serverless jobs
SQL, dashboards and notebooks on the platform, and your own SQL or Python run on a schedule, on new data, or on an event.
Predictive maintenance
Health scores and remaining useful life per asset, learned from its history and its maintenance records, so you fix machines before they fail.
AI agents
Agents read devices, assets, metrics and alarms through the same API and permissions as people, and act only with approval.
Assets, not device IDs
Devices change; assets last. Bind a device's readings to the machine, room or vehicle it measures, for a time interval. When a sensor is replaced, the asset's history continues, and its dashboards, metrics, alarms and jobs keep working.
asset pump-7 · bearing_temp ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━▶ one history bound sensor 8f2 ──────────────────────────────╳ replaced sensor c41 ╰────────────────────────▶ 2025-01 2026-03 now
Device security without a PKI team
Giving every device its own certificate is the right way to secure a fleet, and the part most teams skip because running a certificate authority is a specialist job. We run it for you, under our root or yours.
At the factory
A station on the production line signs each device as it's tested, and keeps working when the factory's internet drops.
In the field
Short-lived certificates renewed automatically by our open-source SDK and agent, so an expired certificate never takes a machine offline.
In one place
Every certificate, where it's used and when it expires, with an alarm when one shows up on two devices at once.
Open underneath
Open-source projects we maintain, in public, under Apache 2.0. The platform is built on their released versions, so you can always run them without us.
Timelake
v0The open time-series lakehouse: fast queries on your own object storage, with no database and no maintenance jobs. The platform's storage, ingestion, rules and edge gateway.
Repositorysensim
designA field of simulated devices that talk real protocols and misbehave the way real devices do. Our test bench, and the virtual devices you'll try the platform with.
RepositoryDevice agent
plannedFor Linux devices and gateways: identity, twin, commands, configuration, over-the-air updates, logs and data sync.
Embedded SDK
plannedA C library for microcontrollers on Zephyr, FreeRTOS, ESP-IDF or bare metal: connect, send data, receive commands and update with MCUboot.
A way off IoT Hub, IoT Core and Particle
IoT platforms are shrinking and changing hands: Google Cloud IoT Core shut down in 2023, AWS ended support for IoT Analytics in December 2025 and IoT Events in May 2026, and Particle became part of Digi International in 2026. We're building the move as a product, not a services project, from these and from ThingsBoard, Thinger.io, Mender, Eclipse projects, and platforms you built yourself.
Compatible device endpoints
Devices built for Azure IoT Hub or AWS IoT Core connect with their existing topics, twins, shadows and certificates.
Device cloud connectors
Particle fleets connect through Particle's own API in minutes. Move the devices over later, with one last firmware update.
Bridge mode
Run both platforms side by side and compare data and alarms before moving a single device.
Importers
Registries, device models, routing rules, detector models and history, translated into Polythings definitions.
A cutover plan
Which devices move unchanged, which need a configuration push first, and what it costs on both sides.
Roadmap
What comes first. Nothing on this page is available yet.
Design
- The platform specification
- This website, with the migration guide, benchmarks and blog
- Our open-source commitment
- The Polythings brand
Foundation
- Workspaces, environments and API keys
- Device identity, provisioning and registry
- The certificate authority: issue, renew and revoke device certificates
- MQTT and HTTP connectivity, ingestion into timelake
Assets, metrics and alarms
- Assets, asset models and bindings
- The metric catalog
- Alarms with lifecycle and notifications
- Connectors for Particle and similar device clouds
Device management and OTA
- Twins, commands and configuration
- The open-source device agent and embedded SDK
- Over-the-air updates with rollouts and health gates
- Cellular connectivity with Teal and other providers
From the blog
- Comparison · Polythings and Azure IoT Hub: what's differentIoT Hub connects devices very well, and leaves the rest to other services. Where we think one platform does better, and where IoT Hub is ahead.
- Security · Device certificates without a PKI teamWhy device identity is where fleets cut corners, what doing it properly looks like, and how our certificate authority will make it the easy option.
- Regulation · What the Cyber Resilience Act means for connected equipment makersReporting obligations started on 11 September 2026; the rest apply from December 2027. What equipment makers have to be able to do, and how a platform helps.