A bridge between the Internet and the Things.
Don't start IoT from scratch. Build scalable IoT products based on HTTP infrastructure.
Take advantage of the extensive HTTP-based ecosystem.
Build on top of your existing HTTP components and know-how.
Avoguard MQTT-to-HTTP Gateway is a bidirectional bridge between MQTT and HTTP. It bridges the gap between IoT infrastructure and the cloud by creating a well-defined, observable, controllable interface between cloud backends and edge devices.
The gateway can work as a MQTT Server (Broker) or an MQTT Client, depending on your use case and existing infrastructure.
It is designed to run on hardware, on-premise servers, or private cloud.
Without writing any code, get a full control of traffic in both directions. Define rules for traffic routing, circuit breaker, rate limiting, and more.
Distribute ingress MQTT traffic to one or multiple HTTP endpoints. Distribute egress HTTP traffic to one or multiple MQTT topics. All while reusing your existing HTTP infrastructure.
Scale your IoT product to millions of devices. The gateway is designed to scale horizontally, has no single point of failure, and can be deployed in a cluster of multiple instances that share the workload.
Get full visibility of all data flows and their metrics like packet rate, bit rate, latency, or errors. Observe in real-time or drill down to a historical time frame.
Define per-topic rules for traffic routing. Both ingress and egress traffic can be controlled. Can be used for load balancing, traffic shaping, or custom handling of specific traffic.
Prevent disasters, and recover quickly. Define limits to prevent overloading downstream systems, and specify conditions for safe and quick recovery.
Limit the rate of message delivery to downstream systems or IoT devices, on a per-topic basis.
Protect your data with TLS encryption and authentication. Define device authentication mechanisms and per-topic security credentials for downstream systems.
Avoguard MQTT-to-HTTP Gateway can be deployed on a dedicated hardware appliance supplied by Avoguard, or a software application on a compatible edge gateway. Contact us for more information.
Deploy on hardwareWith no cloud dependencies, Avoguard MQTT-to-HTTP Gateway can be easily deployed on-premise. It can run as a VM in your own data center, or as a Docker container.
Deploy on-premiseNeed a Kubernetes ingress for MQTT? We got you covered. With Avoguard MQTT-to-HTTP Gateway you can reuse all existing Kubernetes HTTP-based components for MQTT traffic.
Deploy cloud nativeThe cloud and the edge are two very different worlds. The Avoguard Gateway provides a well-defined, well-documented interface that your teams can use to define the intersection of your IoT fleet and your cloud infrastructure, while each team can focus on their own domain.
Your business logic does not need to hide in the code of your IoT devices or in the code of cloud backends. With Avoguard Gateway, your operations / DevOps teams will have full, real-time control of all the traffic.
How much traffic is flowing? How quickly are we processing it? How quickly do devices get their data? Where are errors coming from? With Avoguard Gateway, your operations / DevOps teams will have full visibility of all the traffic, and get answers to your questions faster.
Security audits and penetration testing are a breeze to handle when you have a single, well-defined interface that bridges your device fleet and your cloud. With Avoguard Gateway, your security teams will have full control of authentication mechanisms, TLS encryption configuration, and credentials for access to your cloud backends.
Your IoT product is growing, and you need to scale. With Avoguard Gateway, you can scale your IoT product horizontally, by adding more instances of the Gateway. Your operations / DevOps teams will have full control of the scaling process, and can scale up or down as needed.
Do you have an existing cloud team? For them, HTTP must be second nature. Rather than learning how to implement and maintain MQTT infrastructure, they can leverage their existing know-how, libraries, and APIs to build your IoT product.
The gateway is designed to be handled by your operations, IT, or DevOps team.
It has a graphical configuration interface, but ultimately is controlled by a set of configuration parameters that can be supplied as a configuration file, or controlled by the Gateway's API. In any case, you do not need to write any code.
In the configuration, your business specific logic is defined. Usually, this is a number of rules that define the routing of the MQTT traffic to the HTTP backends, and vice-versa. With the rules defined, monitoring and logging will be automatically started.
In case your MQTT connections or HTTP connections require authentication, you will need to supply the corresponding credentials and configure the authentication method.
From there, just deploy the gateway on your hardware, on-premise servers, or private cloud, and watch the data flowing.
Avoguard Gateway comes in two variants: a Client or a Server. A Server can act as an MQTT broker, whereas Client needs an existing external MQTT broker.
Avoguard Gateway |
Server |
Client |
|---|---|---|
| MQTT 3.1.1 | ||
| MQTT 5.0 | ||
| Inbuilt MQTT Broker | ||
| HTTP 1.1 / 2 / 3 | ||
| IaC Control | ||
| GUI Control | ||
| API Control | ||
| TLS | ||
| TLS Termination | ||
| MQTT (Mutual) Authentication | ||
| HTTP (Mutual) Authentication |
If you have questions about any of the features, or would like to request a feature, please contact us.
If you're ready to use or evaluate the Avoguard Gateway, please contact us to get a quote or a demo.
Avoguard MQTT gateway is not a MQTT broker. It is a bridge between MQTT and HTTP.
It can be used as a MQTT client or a MQTT broker (server), depending on your use case. It can be used as a MQTT client to connect to a MQTT broker such as Mosquitto or RabbitMQ.
But in the use-cases where you don't need a separate MQTT broker, the Gateway can act as an MQTT broker (server) to accept connections from MQTT clients, and translate them directly to HTTP.
If you are building a simple IoT product, you might not need an MQTT Gateway. But if you are building a production-grade IoT product, you will need to consider the architecture of your solution.
The MQTT Gateway is a component that can be used to bridge the gap between your IoT infrastructure and your HTTP infrastructure. It can act as a well defined observable and controllable bridge between the two, separating the concerns of your IoT product from the concerns of your HTTP infrastructure.
It frequently also bridges the gap between internal teams in your organization, and gives your operations team the tools and confidence to operate a large device fleet.
In a typical IoT product / project, the initial users are the software engineers on either the cloud team or the device team. They use the Gateway to agree on the interface between the two teams and the software they are developing.
Once the IoT product reaches first field tests, the operations team takes over. They use the Gateway to monitor and control the traffic between the device fleet and the cloud backends, and make sure that the product is operating as expected.
This is the stage where the Gateway saves a lot of finger pointing, and helps speed up resolution of issues.
If you have a question about the Avoguard Gateway that is not answered here, please contact us. Our IoT team will be happy to answer your questions.
Contact us to get a quote or book a demo.