See it work
One hour of fleet alerts, collapsed to the two that matter — each with its root cause and an autonomous response, in plain language.
For teams. And agents.
Purpose-built for monitoring and resolving software and hardware systems. Where humans and agents share the watch.
Purpose-built for monitoring and resolving software and hardware systems. Where humans and agents share the watch.
One hour of fleet alerts, collapsed to the two that matter — each with its root cause and an autonomous response, in plain language.
Add Plexus by pasting one prompt.
No install. Paste this into Claude Code — or any coding agent — and it wires telemetry into the signal that matters. Operating your fleet then happens in the app's built-in AI.
You're adding Plexus telemetry to this codebase. Plexus ingests metrics and events over HTTP.
Contract:
- POST https://gateway.plexus.company/ingest
- Header: x-api-key: $PLEXUS_API_KEY (read from env, never hardcode)
- Body: {"source_id":"<stable-slug>","points":[{"metric":"<subsystem.name>","value":<number>,"timestamp":<unix ms, optional>,"tags":{...}}]}
Do this:
1. Walk the repo and find the few sites worth instrumenting — external calls (latency + errors), error/retry boundaries, lifecycle (boot/shutdown), throughput (queue depth, batch size), and key domain events. Rank them, cap to ~10–20, and skip getters, pure helpers, and hot loops. Instrument the signal, not every line.
2. Show me the plan (file:line, metric, why) before editing.
3. On approval, add one small client with a batched send() (buffer ~64 points or 5s, back off on 429/5xx), then the emit calls. Never block the hot path or throw from telemetry.
4. Add one usage example and a README line.
Get a key from the Plexus app (/dev/keys) and set PLEXUS_API_KEY.Plexus is one platform across the lifecycle of a hardware fleet: Connect a device with three lines of Python. Observe it on dashboards shaped like the thing you built. Predict failures before they ship.
Hardware-native — edge buffering when the link drops, thermal overlays on real CAD, schemas you can query — not bolted onto a time-series DB. Your IP stays yours.
We design for the engineer at 2am. If the SDK doesn't feel right, we keep cooking until it does. Dashboards come after the API, not before.
Edge buffering when the link drops. Thermal overlays on real CAD. Schemas you can query. Not a TSDB with extras bolted on.
Your IP — dashboards, anomaly models, schema, firmware wrappers — stays yours.
One platform across the lifecycle. Hardware-native — edge buffering when the link drops, schemas you can query — and it surfaces the one real signal instead of drowning you in alerts.
Drop the SDK into the firmware you already ship. Structured metrics, edge buffering when the link drops — from an ESP32 in a lab to a bus on orbit.
from plexus import Plexus
px = Plexus(source_id="drone-001")
px.send("battery", 3.7)
px.send("temp", 82.4)Thermal overlays on real CAD. Fleet-wide anomaly ranking. Schemas you can query — not bolted onto a time-series DB.
<plx-chart series="battery" window="60s" live />
Catch a bearing trending hot. Flag a conjunction window. Identify the design choices you’d make again next time.
px.alert( metric="bearing.temp", above=85, window="15m", )
One platform across the lifecycle. Hardware-native — edge buffering when the link drops, schemas you can query — and it surfaces the one real signal instead of drowning you in alerts.
Drop the SDK into the firmware you already ship. Structured metrics, edge buffering when the link drops — from an ESP32 in a lab to a bus on orbit.
Thermal overlays on real CAD. Fleet-wide anomaly ranking. Schemas you can query — not bolted onto a time-series DB.
Catch a bearing trending hot. Flag a conjunction window. Identify the design choices you’d make again next time.
A Plexus engineer deploys alongside your team — telemetry flowing, dashboards live, fleet in production. Weeks, not quarters.
Drop the SDK into the firmware you already ship. Three lines of Python, telemetry flowing. No setup call. $5 in free credits to start.
A Plexus engineer deploys alongside your team — telemetry flowing, dashboards live, fleet in production. Weeks, not quarters.
Drop the SDK into the firmware you already ship. Three lines of Python, telemetry flowing. No setup call. $5 in free credits to start.
Telemetry flowing from every unit, dashboards shaped like your hardware, anomaly signals before a failure ships. Onboarding is a conversation — tell us what you’re flying, driving, launching, or deploying. We read every one ourselves and write back the same day.