Inventory
Devices + customers
Devices, customer accounts, and cohorts share consistent IDs and metadata.
Platform - Architecture
Control plane architecture for OEM fleets.
Dataplicity keeps device identity, signals, and customer surfaces in one data model so engineering teams stop stitching together five consoles.
- Device identity is the primary key for telemetry, logs, and firmware.
- Events, alerts, and incidents share the same timeline.
- Customer status and dashboards read from the same dataset.
- Security activity and access policies live alongside fleet data.
Identity graph
A single device record ties hardware, customer ownership, and firmware lineage together.
Provisioning
Device classes
Per-SKU configuration and provisioning defaults stay linked to devices.
Ownership
Customers + entitlements
Customer accounts and licenses bind hardware to the right account.
Firmware
Version lineage
Firmware bundles and rollout status stay attached to each device.
Signal pipeline
Telemetry, logs, and alerts run through one workflow instead of separate tools.
Telemetry
Ops dashboard
Metrics arrive over the same outbound connection as logs.
Logs
Syslog search
Device and backend logs land in one searchable timeline.
Events
Event history
Deploys, restarts, and config changes are correlated automatically.
Response
Alerts + incidents
Rules, routing, and incident tracking stay in one UI.
Customer surfaces
Status pages and dashboards reuse the same source of truth.
Status
Status pages
Public uptime surfaces are driven by live monitors.
Dashboards
Read-only dashboards
Expose metrics without handing out credentials.
Portals
Whitelabel access
Brand the customer portal without forking the product.
See the full platform overview.
Browse the modules that ship with Dataplicity today.