Ozibus Device Cloud

Operate every connected device from one Ozibus control plane.

Provision fleets, capture telemetry, dispatch commands, monitor health, rotate device keys, and connect webhooks and API tools from the merchant IoT workspace.

Production control path Identity to device action

Access Confirm the active Ozibus session before opening the dashboard.

Provision Register devices, groups, tags, onboarding keys, and lifecycle states.

Stream Ingest telemetry, normalize events, and expose live operational signals.

Control Dispatch commands, track acknowledgement, retries, and command health.

Integrate Send device events to webhooks, support workflows, and Ozibus automation.

device.registered device.online device.offline telemetry.received alert.triggered

Live modules 10

for device operations

Access gate Ozibus session

shared with app, chat, broadcast

Scope merchant

tenant-aware dashboard access

API stance v1 + v2

legacy-safe expansion path

Implemented modules

A complete IoT workspace, split by how teams actually operate.

The IoT subdomain handles merchant device work: provisioning, telemetry, commands, alerts, API access, webhooks, and fleet health.

Capability group

Device operations

Provision devices, organize fleets, rotate keys, monitor health, and handle alerts without leaving the tenant workspace.

Provisioning Fleet Health Alert Rules Keys and Access

Capability group

Data and control

Use the IoT subdomain for telemetry ingestion, API testing, command queues, audit visibility, and device-facing workflows.

Telemetry Commands API Tools Webhooks

Operating model

From edge signal to Ozibus workflow.

Device data stays isolated by merchant scope, then becomes actionable events for alerts, webhooks, support workflows, and automation.

01Provision

Create device groups, bulk import fleets, assign tags, rotate keys, and prepare lifecycle states.

02Ingest

Receive telemetry through dedicated endpoints and retain event, severity, payload, and audit context.

03Decide

Evaluate fleet health, alert thresholds, API policy, and command readiness.

04Act

Dispatch commands, deliver webhooks, notify teams, and hand off events to Ozibus workflows.

Access state

Sign in to open the IoT dashboard.

The public overview remains available. Dashboard operations require the same Ozibus sign-in used by app, chat, and broadcast.