Tartabit logo

Tartabit IoT Bridge · Custom devices and mixed fleets

Connect your LPWA devices to the cloud you use

Bring custom devices, off-the-shelf sensors and existing fleets into Azure, AWS or Google Cloud. Start with LwM2M and CoAP, or use TCP/UDP connectors when your devices speak a bespoke protocol.

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

LwM2M · CoAP · custom TCP/UDP

Your hardware, network and reporting cadence.

02 · Tartabit IoT Bridge

  • Select a connector for your devices
  • Decode, normalize and enrich data
  • Deliver a consistent application payload

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.

Start with your device integration

Focus on a known protocol, or explore an existing or mixed fleet.

LwM2M

Connect LwM2M devices to Azure, AWS and Google Cloud

Explore integration →

CoAP

Bring CoAP device data into Azure, AWS and Google Cloud

Explore integration →

Custom devices and mixed fleets

Connect your LPWA devices to the cloud you use

Explore integration →

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.

  • Device protocols and security requirements, whether the fleet is new, existing or mixed.
  • Payload definitions, endpoint identifiers and framing rules for custom TCP/UDP.
  • Network reachability and any listener-port allocation required by the connector.
  • Target cloud resources and the data model required by downstream applications.
LwM2M server docs →CoAP connector docs →TCP connector docs →UDP service docs →

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 →