Who is Max for?
Teams integrating factories, buildings, charging infrastructure or mixed device fleets need to map protocols and keep delivery behavior visible when a destination slows down. Max adds selected protocol acquisition/gateways, validation, rules and provider adapters to the durable broker profile.
How does a device reading reach the right system?
Choose the declared protocol profile, validate the input, select the matching topic/rule and configure its destination. Bounded schemas can check object fields; publish rules support literal enrichment, bounded republish and configured bridge enqueue. The supported schema dialect is narrower than full JSON Schema; use its documented limits.
The broker records durable intent and the bridge process performs the external interaction. Retry, dead-letter and backpressure behavior stay bounded. A broker acknowledgement alone cannot establish that the destination committed the effect; verify its own receipt.
Which protocols and providers are included?
Device profiles include MQTT/WSS, MQTT-SN 1.2, HTTPS, CoAP, LwM2M 1.2, Sparkplug B 3.0 over MQTT, OCPP 1.6J over WSS and a LoRaWAN network-server link.
Modbus TCP polling and OPC UA client/subscription acquisition are initiated by the broker process.
These are selected profiles with explicit configuration and limits; inspect the exact device requirements before deployment.
Configured destinations include PostgreSQL, HTTPS webhook, MQTT, Kafka, Redis Streams, ClickHouse, S3-compatible storage, InfluxDB, TimescaleDB and RabbitMQ/AMQP 0.9.1. The provider adapters use the public SDK and carry their own scoped evidence. Cloud IoT service links remain unavailable.
Can I use my own integration?
Yes. Use the same public C Bridge SDK v3 with v1/v2 compatibility and supply a target-compatible library/configuration package. The Build guide covers the complete path.
Custom adapters are available in every tier; Max adds the selected provider catalog and integration workflows.
What must operations verify?
Supply provider trust and credentials privately. Test exact payload projection, ordering, duplicates, outage/restart, terminal failures and sink commitment.
Keep one side-effect owner during cutover. Use the integration skill and migration skills to retain decisions and evidence.
Max runs a durable single active node. Fenced standby, SSO/RBAC command governance and the Enterprise operating commitment belong to Enterprise. The panel/API support operational reads; governed writes are blocked in the shipped Max configuration.