Skip to Content
Introduction

Plexus Docs

Plexus is a hardware observability platform. Stream telemetry from devices, query historical metrics, and monitor fleets in real time.

Get started

Quickstart
Send your first metric and read it back in under 5 minutes.
Hardware integration
Python SDK, ESP32, and Arduino patterns for shipping firmware.
Guides
Walkthroughs for batching, events, tags, and live streaming.
API Reference
Every REST and WebSocket endpoint on the Plexus Data API.

How it works

                                                  ┌──────────────┐
                                             ┌──> │  Dashboard   │
┌──────────┐   SDK / HTTP   ┌─── ──────────┐ │    └──────────────┘
│  Device  │ ────────────->  │   Gateway   │─┤
└──────────┘                └─── ──────────┘ │    ┌──────────────┐
                                             └──> │   Data API   │
                                                  └──────────────┘
  • Device — set up the SDK or HTTP to stream metrics, events, and video from your hardware.
  • Consume — query and visualize via the Data API or built-in dashboards.

Key concepts

  • Source — a device or process identified by a stable source_id. It’s the top-level unit in Plexus: all metrics, events, and commands belong to a source. Plexus creates it automatically on first ingest.
  • Metric — a named numeric time-series value scoped to a source (battery.voltage, motor.rpm). Queryable by range, streamable live, and aggregatable across the fleet.
  • Event — a structured non-numeric payload attached to a source: faults, state changes, or log entries. Stored separately from metrics and queryable via the Logs API.
  • Fleet — your full collection of sources. The Fleet API lets you query and monitor all devices at once rather than one at a time.
Last updated on
Quickstart