Public SDK / integration development
Build a bridge for your destination.
Build a C adapter to deliver MQTT events to your destination. The public Bridge SDK is available in every tier.
Compile against the installed SDK header, then add the shared library, configuration and topic rule to your deployment.
Build a file sink.
The hello-world adapter receives a selected MQTT event and appends a non-secret topic/length summary to a file. It uses the public ABI v1 entry point, which the current v3 host continues to support.
MQTT topic: hello/world/#
→ broker topic rule
→ configured bridge target
→ isolated adapter worker
→ libhello_world_adapter.so
→ file owned by the destinationDefine the delivery contract.
Choose the point where the destination has committed the effect. Return canonical retryable or terminal results. Preserve the host’s idempotency identity and verify behavior after ambiguous network outcomes.
The bridge host owns retry scheduling, backpressure, dead letters and durable replay when selected. ABI v2/v3 batches are bounded to 32 events and 1 MiB. ABI v3 includes full event identity and a host-generated idempotency key.
Each target runs in its own worker. Native faults can restart that worker, while host resource exhaustion remains a shared risk. Only load trusted customer code.
Free keeps delivery state in memory. Pro and higher can use the PostgreSQL outbox. Max and Enterprise include provider adapters and their scoped evidence; custom adapter development remains available throughout.
What goes into your adapter package?
| File | Purpose | Check before delivery |
|---|---|---|
adapter.so | Client-library interaction through the public vtable. | CPU, libc, negotiated ABI, callbacks and capabilities match the installed host. |
| Worker configuration | Target, trusted library path, timeout and bounded execution policy. | Canonical path, safe owner/modes, optional expected digest and private credential references. |
| Guardian manifest | Names the selected bridge and its worker configuration. | Use the normal shared guardian; keep each target’s state separate. |
| Topic route | Selects events for the configured target. | Use the tier’s supported rules or bridge-only routing profile. |
| Test and operating notes | Describe commitment, retry, duplicates, drain and recovery. | Verify destination effects and credentials privately with the intended image. |
Build outside the runtime image with any compatible C toolchain. Mount the library and configuration read-only, preserving the selected node’s IPC/PID/network joins. The installed header is the authority for ABI declarations.