DeviceChain
English
Download
Platform · Integrations

What DeviceChain connects to, and what it does not yet.

Every entry here ships today and links its docs page. Where support is partial, the cell says so and links the transport matrix row that explains the limit. Names are those of the projects and standards involved.

Integrations

Device transports

How devices reach the platform. Read, write and subscribe are the docs' transport matrix, cell by cell.

HTTP

A POST endpoint for the same JSON event body. Simple and one-way: a device that reaches the platform only over HTTP cannot be commanded.

  • Read None
  • Write None
  • Subscribe Full

Connecting a device: HTTP →

Integrations

LoRaWAN network servers and webhooks

A network server, or any system that can send an HTTP POST, forwards decoded uplinks to a tenant's integration. The device never connects to DeviceChain.

Integrations

Industrial and device-management standards

Standards-native edge protocols.

Sparkplug B

DeviceChain joins your Sparkplug environment as a Host Application on a broker you operate, follows the birth and death session protocol, and turns edge traffic into the same events every other transport produces.

Sparkplug-B ingestion → · Details →

LwM2M

Devices connect in to DeviceChain over CoAP/UDP secured with DTLS pre-shared keys. Registration, sensor objects, commands and firmware writes map onto the same device model as every other transport.

LwM2M ingestion → · Details →

Integrations

Outbound: where a rule can send

A rule's action can publish to these. Each is a one-way sink.

Amazon SNS

A rule's publish action sends to an SNS topic with a static per-tenant access key. The connector never borrows the pod's own cloud identity.

Outbound connectors →

Amazon SQS

A rule's publish action sends to an SQS queue with a static per-tenant access key. The connector never borrows the pod's own cloud identity.

Outbound connectors →

Integrations

SDKs

Build on the API from your own code.

TypeScript and React packages

@devicechain/client is the framework-agnostic TypeScript SDK. @devicechain/dashboards, @devicechain/widgets, @devicechain/widget-sdk and @devicechain/brand are the dashboard runtime, widgets, widget contract and brand tokens.

npm packages →

Integrations

AI agents

MCP server

An optional, opt-in server with curated read-only tools behind an OAuth 2.1 authorization server, plus Preview tools that propose alarm actions for a person to approve in the console. Every call runs under the signed-in user's own token.

MCP → · Details →

Integrations

Data access

Not available

Named so you do not wait for them.

Not available: WebSocket device ingest. The docs list what is not available and why.

Transport matrix: not available →