Leverege Connect is the Ideal Replacement for Google IoT Core

<!-- wp:paragraph --> <p><br>To organize devices within a registry, users can utilize device groups. Device groups allow administrators to add user permissions and assign actions to a subset of the devices in registries. A group can have many devices and a device can belong to many groups, providing flexible and effective device management. These device management features are designed for enterprises that need to manage thousands to millions of devices at scale. </p> <!-- /wp:paragraph -->

<!-- wp:image {" />

Secure Key Pairs, Authentication Methods, and Multiple Supported Protocols

To verify device identity, Leverege Connect uses public key (or asymmetric) authentication. Authentication can be enforced at the device or registry level, and is configurable in the registry properties. Leverege Connect supports RSA and Elliptic Curve Algorithms. How the JWT is sent to Leverege Connect depends on the connection protocol. 

These capabilities enforce authentication at the device level or registry level, providing flexibility to accelerate testing and ensure security at scale. In addition, administrators can choose to allow anonymous devices to connect to a given registry, meaning that no authentication is enforced. This can be helpful during development and testing. 

Leverege Connect fully supports MQTT and HTTP transport and support for other transfer protocols such as UDP and CoAP are on the product roadmap.

No-Code Message Routing 

Actions built into Leverege Connect allow users to decide where different types of messages get routed. Actions allow you to route messages to different places based on logic that you can define, like which Pub/Sub topic to route your data to. Users can create multiple actions for each registry or device group for fine-tuned control over device data flow. Supported Action triggers include: 

• Telemetry Events Reported by Device
• State Changes Reported by Device
• Config Settings Sent to Device

In addition to Actions, Secrets provide a secure way to store sensitive information that the system needs to reference in Leverege Connect integrations. Service accounts for Pub/Sub are one example. Adding a secret to Leverege Connect assigns an ID to the secret and makes it available to reference in your Actions.