MQTT (platform broker)
The default path. The broker is the MQTT server built into NATS, so there is no separate broker to run. Each device is bound to its own subjects.
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.
How devices reach the platform. Read, write and subscribe are the docs' transport matrix, cell by cell.
The default path. The broker is the MQTT server built into NATS, so there is no separate broker to run. Each device is bound to its own subjects.
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.
The platform can subscribe as a client on an existing broker to ingest from it. That connection is plaintext and presents no broker credentials, so the docs recommend the platform broker unless you need this.
On the platform's MQTT broker, a device can authenticate with a client certificate that chains to a trust anchor the tenant added, and a certificate profile can register it on first connect.
A device with no credential yet can register itself over HTTPS with a provisioning profile's key and secret and receive its own device token.
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.
ChirpStack's HTTP integration posts uplinks to a tenant's integration URL with a bearer token. The platform stores the values your ChirpStack codec decoded, or decodes the frame itself with a payload decoder on the device profile.
A custom webhook on a Things Stack application posts uplinks to a tenant's integration URL with a bearer token. The platform stores the output of your payload formatter, or decodes the frame itself with a payload decoder on the device profile.
Any system that can POST JSON: a gateway vendor's cloud, a middleware, a script. You say where the device identifier and the uplinks are in the body.
Standards-native edge protocols.
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.
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.
A rule's action can publish to these. Each is a one-way sink.
A rule's httpCall action sends a POST to a URL, with a sealed credential if you attach one. A non-POST method is refused.
A rule's publish action sends to a Kafka topic through a versioned connector, with TLS and SASL (PLAIN, SCRAM-SHA-256, SCRAM-SHA-512).
A rule's publish action sends to a topic on a broker you name, at QoS 0, 1 or 2, over tcp, ssl, mqtts, ws or wss URLs.
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.
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.
Alarm notification channels reach people rather than systems, over SMTP and webhook, under a per-tenant policy.
Build on the API from your own code.
@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.
DeviceChain.Sdk on NuGet, with ahead-of-time compilation checks. A Unity package, built from source, wraps it with Unity transports.
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.
One GraphQL schema for each area of the platform. The schema files are published with the docs.
Telemetry lives in TimescaleDB, which is PostgreSQL. Declare a read role, and any tool that speaks Postgres can query your tenant's analytics views.
Not available: WebSocket device ingest. The docs list what is not available and why.