Platform Documentation

/

Platform Overview

Use NEQTO.ai to monitor equipment, track moving assets, investigate readings with AI, and send commands back to Devices. Connect hardware and external services, build operational Dashboards, and automate responses to Alert conditions. Your Account holds your team and resources; an Application organizes selected resources for a project, site, or team.

Monitor, Analyze, and Respond

Follow readings from connected equipment through visual monitoring, analysis, and action.

📡
Endpoints & Devices

Create an Endpoint for your connection type. Incoming payloads identify Devices and their Attributes, such as temperature or humidity. Check the mapped readings.

  • MQTT, HTTPS & WSS endpoints
  • Auto-created devices & attributes
  • Real-time ingestion feedback
  • Connectivity status & timeouts
📊
Dashboards

Combine live readings, historical trends, and location views. Save layouts, switch between Dashboard tabs, and export selected data Widgets to PDF.

  • Gauges with colored ranges, including tank-level displays
  • Fan forecasts with uncertainty bands, based on recorded history
  • Image Maps, World Maps, and Tracking Maps with location trails
  • Tables, distributions, XY comparisons, and calculated values
🧠
Analytics

Review one Application over a period you choose. An AI Analysis Report summarizes aggregated readings and Alert activity.

  • AI Analysis Report
  • Critical, Warning & Normal cards
  • Alert events timeline
  • CSV export
🔔
Alerts

Notify your team or send commands when conditions are met. For example, a Threshold Alert can send a cooling command when a temperature exceeds your limit, using a payload your equipment understands.

  • Threshold, connectivity & anomaly types
  • Email & SMS notifications
  • Automatic payload push to supported Endpoints or Integrations
  • Alert History & triage

Forecasts estimate future values and need sufficient history. World Maps and Tracking Maps require Google Maps availability and suitable location data. Widget Calculations can turn readings into values such as dew point, power, or the difference between two temperatures.

AI Across Your Workflow

AI is integrated throughout NEQTO.ai. Use plain language to explain what you want to build, change, understand, or investigate.

Build and refine Widgets, calculations, Alerts, Reports, Integrations, Tags, and simulations with Ask AI. Ask how a feature works, which sensors exceeded a limit, or why two periods differ. Start from chat, a Widget, or a setup screen to include the relevant context. AI also maps Integration samples and summarizes Application activity. Review generated settings, formulas, and targets before applying changes. Your permissions still control access.

Organizing and Extending

Model physical equipment, connect other services, share reports, and control Devices from the same Application.

Feature What it does
Systems Build a visual digital twin of a building, machine, or fleet. Nest Systems, place Devices and child Systems on floor plans or equipment images, and inspect live readings at their pins. Show the same System view on a Dashboard and navigate into its child Systems.
Reports Create one-time or scheduled CSV or PDF reports of Device summaries and email them to selected recipients. Include Alert and anomaly summaries or an AI summary. Daily, weekly, and monthly schedules are available according to your plan. Use Analytics for interactive review.
Integrations Bring external data into the same Device and Attribute model as sensor readings, or push JSON to another service. Use prebuilt connectors, such as Weather, or configure a custom HTTPS, WSS, or MQTTS connection. Prebuilt connectors provide scheduled updates; custom pull connections support manual samples from the UI.
Tags Apply reusable key:value labels, such as floor:3, to find and filter Devices across operational views.

Control Devices and automate responses

Add a Data Push Button or Form to a Dashboard to send commands through an MQTT or WebSocket Endpoint. For automatic control, configure a Threshold Alert’s Payload push action, such as a cooling command triggered by a high temperature. In Actions, inspect the destination and payload, preview it without sending, approve and enable it, and check delivery outcomes. Your equipment must handle the command; confirm the resulting state in its readings.

Tip: the Glossary of Key Terms is a general primer on the platform and IoT vocabulary. For what a feature actually does, use its own page.

Quick Start

Connect a Device, confirm its readings, and then build a Dashboard or Alert.

  • 1
    Sign in with an emailed magic link or a password. See Administration to invite teammates and manage access.
  • 2
    Open Applications, select +, name the Application, assign existing resources if needed, and select Create. See Applications.
  • 3
    Open the Application and go to Devices > Device Endpoints > Add Device Endpoint. Select the setup for your hardware. Copy and securely store the connection details.
  • 4
    Use How to connect a device to send a payload. Find the resulting Device and verify its Attribute values and units.
  • 5
    Build a Dashboard and configure an Alert. Use Ask AI to request a Widget or Alert draft if you want help getting started.

No hardware yet? Create a Demo Device Endpoint and use the Built-in Simulator to generate readings. Confirm the simulated data reaches the Device before testing an Alert.

Accounts, Applications, and Users

Use these five concepts to understand where settings and readings belong.

Layer What it is Where you manage it
Account Your organization. Holds users, roles, billing, and every application. Administrator > Account Settings
Application A project or team’s view of selected Devices and Endpoints, with its own Dashboards, Alerts, Systems, Tags, members, and reports. The same Device can be assigned to more than one Application. Applications
Device Endpoint One protocol and authentication configuration. The devices that publish through it are grouped underneath it. Devices > Device Endpoints
Device An identified source of readings, such as a sensor, simulated sensor, or Integration. Devices
Attribute One measurement from a device, such as temperature or battery. Mapped automatically

Roles grant permissions at Account or Application scope. A user can have both kinds of role. See Administration for the role and permission reference.

The Default Application. Includes all current and future Account Devices and Endpoints. Its assignments are fixed.

Applications

Create an Application for a project, site, or team. Assign Endpoints or individual Devices to choose which resources it includes.

Assigning an Endpoint includes its current and future Devices. The sidebar shows Dashboard, Analytics, Devices, Alerts, and Reports according to your permissions. Follow Applications for creation, assignments, and user access.

How Data Gets In

Choose the connection according to which system initiates it.

Path Use it when What you configure
Device Endpoint Your hardware or software connects to NEQTO.ai. A connectivity type and authentication type. NEQTO.ai issues the credentials.
Integration NEQTO.ai must connect out to an external service. The service URL and credentials, with pull for incoming data or push for outgoing data.

Processed readings feed Dashboards, Alerts, Analytics, Reports, and Systems. A push-only Integration sends data out without creating incoming readings.

Connectivity types

An Endpoint’s connection type is fixed at creation. Changing it requires a new Endpoint.

Type Use it for
MQTT Most IoT devices and gateways. A persistent, low-overhead connection.
HTTPS Devices, scripts, or services that push data with an HTTP request.
WSS Apps and gateways that keep a live WebSocket open and stream frames.

Use TLS when your hardware supports it. MQTT Device Endpoints also offer an unencrypted option. HTTPS and WSS Device Endpoints use TLS. Choose a secured connection for Device data and credentials. Integrations require TLS and offer HTTPS, WSS, and MQTTS.

NEQTO.ai accepts flexible JSON and recommends neqtoai-std to identify the Device, time, values, and units explicitly. Auto-Parsing maps supported payloads, including supported EnOcean telegrams and BLE gateway reports. Check ingestion feedback and verify the resulting readings. See Endpoints & Devices and Supported Devices. Guided setups are available for HPE Networking and Blues.