Open app

Plexus Docs

Plexus stores and shows your machines' data. Stream telemetry from devices, query historical metrics, and watch your fleet in real time.

Get started

Quickstart
Set up with your coding agent in one line, or with the Python SDK on a device.
Hardware integration
Python SDK for Linux boards, plain HTTP for microcontrollers.
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   │
                                                  └──────────────┘
  • Set up — connect your coding agent to the Plexus MCP server and tell it "set up Plexus". See the Quickstart.
  • Device — send metrics, events and video from your hardware with the SDK or plain HTTP.
  • 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 Events API. See Send logs and events.
  • Fleet — your full collection of sources. The Fleet API lets you query and monitor all devices at once rather than one at a time.