Skip to main content

Network Middlewares

Middleware adds managed endpoints that connect external networks and systems to TagoIO. You install it from the App Catalog, which you open from Apps in the top navigation. Inside a project, a middleware's app label reads Middleware {Type}, for example "Middleware Chirpstack".

The catalog changes over time, so this guide covers how to deploy and operate any middleware. Available types today are AWS IoT, Chirpstack, Everynet, Generic HTTPS, Loriot, MachineQ, Myriota, Senet, Sigfox, Tektelic, and TTN.

An active middleware instance runs inside your single-tenant environment and uses your project's resources. You can scale instances, attach custom domains, and point external networks to the middleware's endpoint.

What is a middleware?​

A middleware bridges data between an external network or platform and your TagoDeploy project. It receives uplinks and forwards data to TagoIO, and most types also handle downlinks or callbacks. Each middleware runs as an isolated service with its own configuration, token, and scaling policy.

Installing a middleware​

You install a middleware from the App Catalog. Open Apps in the top navigation, find the middleware type, and click its card to open the detail dialog. Click Next to open the install dialog.

The install dialog first asks where the middleware should run:

  • In a project: Add it to an existing project. Action button "Add to Project".
  • New Project: Provision it alongside a new project. Action button "Review and Install".

You then set these fields:

  • Project: The target project (only when installing into an existing project).
  • Region: The AWS region the service runs in.
  • Version: Defaults to the latest unless you need compatibility with an older stack.
  • Name: Display name for the service instance, under Settings.
  • Network Token: The token the middleware uses to write and read in your project.
  • TagoIO API URL: Pre-filled with your project's API endpoint.

Confirm to deploy. The service provisions networking, compute, and a default autoscaling policy.

Domains​

You can attach a custom DNS domain to a middleware after you deploy it. See Domain Registration at TagoDeploy Domains Management.

Using the middleware​

After it deploys, point your external network or platform at the middleware's public endpoint. The endpoint URL is on the middleware's Overview page in the project. Follow the integration steps for your network in the TagoIO documentation.

The middleware authenticates with the Network Token you selected at install time. That token scopes which devices the middleware can write and read in your project.

Billing considerations​

Middleware instances use compute, memory, and network resources in your TagoDeploy environment, so they add to project costs. Size your machine tier and autoscaling limits to the load, and check the utilization graphs now and then so you don't over-provision.