Platform Documentation

NEQTO.ai turns device data into dashboards, alerts, and analysis without writing code. Inside your Account, Applications are scoped workspaces, each holding the device endpoints, devices, dashboards, alerts, maps, and tags assigned to it. A Device Endpoint is the secure inbound channel your hardware connects to, a Device is one piece of equipment sending data, and an Attribute is one measurement from that device, such as temperature, humidity, or battery.

Quick Start

The shortest path from a new account to a device you can chart and alert on.

• 1
  Create your account and invite your team
  Sign-in starts with a magic link emailed to your address. Open Administrator > User Management to invite teammates. See Administration.
• 2
  Create an Application
  Open Applications, select +, and enter a name. Choose a template to preselect the sidebar sections, then assign device endpoints or individual devices.
• 3
  Add a Device Endpoint
  Inside the application, go to Devices > Device Endpoints, click Add Device Endpoint, and pick a connectivity type: MQTT, HTTPS, or WSS. Copy the credentials from the final step and store them securely.
• 4
  Send your first payload
  Use the endpoint’s How to connect a device helper, which shows a working example for your protocol. After the first valid message is processed, the Device appears and its readings become Attributes.
• 5
  Build on the data
  Add widgets in Dashboards, set conditions in Alerts, review the period in Analytics, and pin devices on a Map.

Accounts, Applications, and Users

Five layers stack from your organization down to a single reading. Each one is managed in a different place.

Access is granted through roles, and permissions come in two scopes that never mix: account scope covers the whole organization, and application scope covers one workspace. A user can hold an account-wide role, a role in one or more applications, or both. For the full role and permission reference, see Administration.

Applications

An Application is the highest-level organizational unit in your account, a dedicated project environment where your team builds and manages a complete IoT solution.

Creating an application is a three-step wizard: details, template, then devices. The template only selects a starting set of sidebar sections, and you can change them later.

How Data Gets In

Data reaches NEQTO.ai in two ways, and the difference is simply which side opens the connection.

Either way the result is the same: a Device with auto-mapped Attributes, usable in dashboards, alerts, analytics, and maps.

Connectivity types

You choose the type when you create the endpoint, and it cannot be changed afterward. To change it, you create a new endpoint.

NEQTO.ai accepts flexible JSON, with neqtoai-std as the recommended envelope rather than a required one. Incoming payloads go through automatic data normalization: Auto-Parsing recognizes the payload shape, registers the Device from a stable identifier, and maps each reading to an Attribute, so differently shaped payloads end up in one consistent structure with no manual field configuration. Auto-Parsing also decodes EnOcean radio telegrams and BLE gateway scans natively, so those families need little or no payload shaping. For payload guidance and the device families covered, see Endpoints & Devices and Supported Devices. Guided setups exist for HPE Networking and Blues hardware.

The Four Pillars of an Application

Every application is built from four functional blocks covering the full lifecycle of your IoT data, from hardware ingestion to actionable intelligence.

Organizing and Extending

Beyond the four pillars, these features organize your devices and extend what you can do with their data.