TagoIO Documentation

website·Indexed 34 days ago

https://docs.tago.io

Technical documentation for the TagoIO IoT platform, including TagoCore, TagoDeploy, TagoTiP, and the TagoIO API. It covers edge computing, data management, MQTT client and broker configuration, ACL permissions, and the development of plugins using Action Trigger, Payload Encoder, and Service modules.

Tokens
208.5K
Snippets
480
Records
1.9K
Agent score
65%

What's inside TagoIO

  1. Overview of TagoCore Plugins

    Plugins in TagoCore are add-on components that function like apps for the IoT platform. They allow users to expand the platform's capabilities by adding new integrations, data sources, storage options, and specialized functionality without modifying the core system. Plugins can be created by the TagoIO team or the community.
  2. Overview of TagoCore IoT Platform

    TagoCore is a free, fast, and open-source IoT platform designed for edge computing and data management. It allows developers and businesses to self-host a solution for collecting, processing, and analyzing data from IoT devices. Key capabilities include real-time data processing, Docker-based deployment, and an extensible architecture via plugins for cloud integration and custom functionality.
  3. Overview of TagoIO MCP Server

    The TagoIO MCP (Model Context Protocol) Server acts as a bridge between AI-powered development tools and the TagoIO IoT platform. It allows AI agents to understand and interact directly with real device data, platform configurations, and other TagoIO resources to enable intelligent workflows.
  4. Overview of Single Sign-On (SSO) in RUN

    Single Sign-On (SSO) in RUN allows applications to delegate authentication to an external identity provider. This enables users to maintain a single set of credentials across multiple services and provides organizations with centralized access control, removing the need to manage passwords directly within the RUN platform.
  5. Overview of TagoDeploy Monitoring Alerts

    TagoDeploy Monitoring watches the underlying infrastructure of a TagoDeploy project (services, resources, and account spend) rather than application-level data like dashboards or devices. It uses alert rules to monitor a specific metric on a specific resource and triggers a response (Action) when a defined threshold is crossed. The system consists of three main components: Alerts (the rules), Actions (the responses, such as email, SMS, or webhooks), and Logs (the record of checks and triggers).
  6. Overview of TagoCore Analysis

    An Analysis in TagoCore is a custom script that processes device data in real-time. It acts as a data processor that can automatically transform data, calculate new values, detect patterns, or trigger actions when devices send information to TagoCore.
  7. Overview of TagoIO Actions

    Actions in TagoIO allow you to execute specific operations on devices based on user-defined events. This feature enables automated responses and integrations such as sending SMS or emails, executing scripts via Analysis, making HTTP POST requests, sending account or RunUser notifications, and publishing messages to MQTT topics based on defined conditions.
  8. Overview of the TagoIO REST API

    The TagoIO Application Programming Interface (API) allows developers to programmatically manage accounts, data, devices, dashboards, and scripts. The API follows RESTful principles and provides the same capabilities as the Admin page, enabling the connection of devices, data sources, and third-party applications to a TagoIO account.
  9. Overview of TagoIO Access Management

    Access Management (AM) in TagoIO is used to securely grant access to specific account resources. The system operates by creating 'Targets' (which can be Users or Analysis) and assigning them 'Permissions' to define exactly which resources those targets are authorized to access.
  10. Overview of TagoTiP/S Secure Crypto Envelope

    TagoTiP/S (Secure) is a binary crypto envelope that provides AEAD (Authenticated Encryption with Associated Data) for TagoTiP data. It is intended for use in environments where TLS is unavailable or too costly, such as LoRa, Sigfox, NB-IoT, or raw UDP. To minimize overhead, TagoTiP/S uses a 'headless inner frame' that omits fields already present in the envelope header, reducing message size by approximately 40-50 bytes.
  11. Overview of TagoIO Monitoring Actions

    An action is a reusable notification or automation trigger that executes when a monitoring alert fires. While an alert detects a condition, the action defines the response (e.g., sending an email or triggering a webhook). Actions are defined independently and can be linked to one or multiple alerts.