Tartabit IoT Bridge · CoAP

Bring CoAP device data into Azure, AWS and Google Cloud

Receive CoAP messages, associate them with devices and transform their payloads before forwarding data to your cloud. Tartabit IoT Bridge connects your device protocol to the services your application already uses.

Read the docs

Review the technical references, then contact us or sign up to evaluate.

From device protocol to cloud application

Configure the device connection, the data transformation and the cloud destination independently.

01 · Devices

CoAP requests and device payloads

Your hardware, network and reporting cadence.

02 · Tartabit IoT Bridge

  • Receive and identify device messages
  • Decode payloads in JavaScript triggers
  • Publish through your cloud connector

03 · Your cloud

  • Microsoft Azure
  • Amazon Web Services
  • Google Cloud
Payload mapping and connector configuration depend on the device and destination. A shared integration layer does not make every device or cloud service interchangeable.

Choose your cloud destination

Use the connector reference for credentials, configuration, events and actions.

Amazon Web Services

AWS IoT Core

Publish device data into AWS IoT Core using the configured service and topics.

Read AWS IoT Core docs →

Google Cloud

Pub/Sub

Publish application payloads to Pub/Sub topics for downstream Google Cloud services.

Read Pub/Sub docs →

What to have ready

Use these details to check the integration fit before you configure a trial.

  • The device request method, path, content format and a representative payload.
  • Listener access, device identity and the security settings supported by your deployment.
  • Cloud credentials and a trigger that maps the received data to your application schema.

Start with the technical details

Read the configuration and connector references. When you are ready, use the docs links to contact us about your integration or sign up through Azure or AWS Marketplace. The US and EU hosting choices can both serve integrations with Azure, AWS or Google Cloud.

Read the docs →