polythings
HomePlatformMigrateBenchmarksBlogOpen sourceRoadmap
Open source

Open where it matters to you

Polythings is a commercial platform built on open-source projects we maintain. Everything that runs on your devices, and every format your data is kept in, is open source under Apache 2.0, so the platform is a choice you can reverse.

Our commitment

  1. 01

    Software on your devices is open source

    The device agent, embedded SDK, update format, edge gateway and client SDKs are Apache 2.0. You can read, audit and fork every line that runs on your hardware.

  2. 02

    Your data is in open formats

    Telemetry, events, alarms and audit logs are Apache Iceberg tables of Parquet files, readable by DuckDB, Spark, Snowflake and others, in a bucket you can own.

  3. 03

    Standard protocols

    Devices speak MQTT, HTTP, CoAP and LwM2M, not a protocol only we implement.

  4. 04

    Leaving works

    Your configuration exports in documented formats, and the open-source stack keeps your devices and data working without us. We test the exit.

  5. 05

    Open stays open

    Code we release as open source is never relicensed under a more restrictive license.

  6. 06

    We build in the open

    The open projects' specifications, roadmaps and benchmarks are public, including where we're slower.

Projects

Public repositories under github.com/polythings. Planned projects will be developed in the open from their first commit.

Timelake

v0

The 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.

Website GitHub

sensim

design

A 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.

GitHub

Device agent

planned

For Linux devices and gateways: identity, twin, commands, configuration, over-the-air updates, logs and data sync.

Embedded SDK

planned

A C library for microcontrollers on Zephyr, FreeRTOS, ESP-IDF or bare metal: connect, send data, receive commands and update with MCUboot.

Update format

planned

Signed update manifests, the installer interface any device can implement, and delta images.

Connectivity server

planned

An MQTT broker with per-device authentication, and the layers that let devices built for Azure IoT Hub or AWS IoT Core connect unchanged.

SDKs and CLI

planned

API clients for TypeScript, Python, Go and Rust, and the poly command line.

Where the line is

The open projects are useful on their own. The platform is what we sell: running all of it for you, at scale, with the pieces that only make sense as a service.

Open source · Apache 2.0
  • Everything that runs on your devices and sites
  • Every format your data is stored in
  • Storage, ingestion and rules (timelake)
  • Client SDKs and the CLI
Polythings platform
  • The managed, multi-tenant cloud
  • Console, dashboards and the embeddable portal
  • Rollout orchestration, alarm management, the metric catalog and job runtime
  • Migration tooling, AI features, enterprise features