Overview

akenza is the IoT application enablement platform that connects, controls, and manages devices, data, and applications, all in one place.

akenza is a self-service IoT application enablement platform. It covers everything between a sensor in the field and the decision you want to make from its data: connecting devices, decoding their payloads, processing and storing the results, triggering actions, and visualizing it all, without building and operating your own IoT infrastructure.

High-level overview of the akenza platform

Start here

Getting Started

Create your organization and workspace, your working environment on akenza.

Connect a Device

Bring your first device online and see its data arrive.

Data Flows

Configure how device data is decoded, processed, and forwarded.

REST API

Automate akenza and integrate it with your own applications.

No hardware at hand? The Device Simulator lets you send realistic uplinks and build a complete setup before your devices arrive.

How akenza works

The akenza data processing pipeline is structured as follows:

The akenza data processing pipeline

1. Connect. A device sends an uplink over its connectivity (LoRaWAN, HTTP, MQTT, CoAP, NB-IoT, mioty) or through a connected third-party cloud. The device connector authenticates the message.

2. Decode. The device type parses the raw payload into structured, human-readable JSON.

3. Process & store. Output connectors write the result to akenza DB or forward it to your own database, streaming service, or webhook.

4. Act. The rule engine evaluates the data and triggers notifications, downlinks, or aggregations.

5. Visualize. The Dashboard Builder turns stored data into dashboards, signage screens, and shareable links.

Applications

The platform is made up of four interlinked applications. You can access all of them regardless of your subscription, though some functionality is restricted to specific tiers. See Applications for details.

Device Management

Manage connectivity, devices, data flows, business logic, and users.

Dashboard Builder

Build data-driven dashboards, share them via public links, and run signage screens.

Genio

Ask questions about your IoT data in natural language and get contextual answers.

Device Setup Assistant

Roll out devices at scale with QR-code scanning and guided, on-site configuration.

Platform capabilities

Device Management

Full control over all your assets at any time. Device management supports every phase of the device lifecycle and offers a comprehensive set of features to manage your fleet at scale: an asset inventory with custom fields and tags, bulk import and bulk actions, per-device message history, signal quality and battery monitoring, and device lifecycle reports.

Connectivity Management

Connectivity integrations let you integrate and manage devices from different connectivity providers, such as Swisscom LPN, Loriot, Actility, ChirpStack, or The Things Network, so that existing deployments can be operated alongside new ones from a single point.

The Connectivity-as-a-Service offering additionally lets you onboard devices without establishing a contract with a network provider.

Data Processing

Data flows let you configure a complete data processing pipeline once and then apply it to any device in your fleet. akenza makes sure data is reliably decoded, processed, and forwarded or stored. Payload decoding and encoding can use a device type from the library or your own custom scripts.

Connectors & Storage

Output connectors specify the destination of your data and store it for future use: akenza DB, InfluxDB, SQL databases, and Snowflake, or streaming targets such as webhooks, Azure IoT Hub, AWS Kinesis, Google Cloud Pub/Sub, and Apache Kafka.

Rule Engine

With the rule engine you can analyze and process data from multiple devices simultaneously and trigger actions when needed. Actions include sending SMS or email notifications, posting to Slack or Microsoft Teams, sending downlinks, and aggregating your data.

Data Fusion Layer

The Data Fusion Layer normalizes telemetry from multi-vendor devices into a standardized digital twin based on a tailored subset of the Brick Schema ontology, so that data is available in its spatial context of sites, floors, zones, and assets, rather than as isolated device silos.

Akenza Building Edge

Akenza Building Edge connects building management systems directly to akenza, bringing existing BMS data into the same pipeline as your IoT devices.

Key concepts

Device

A device (a "thing") represents deployed hardware in the field, capable of connecting to the internet via a supported connectivity. Devices send data via uplinks and optionally receive commands via downlinks. They are managed in the asset inventory.

Data, topics, and samples

All data is sent from devices to the cloud, usually telemetry and state, such as environment measurements. Devices typically send data either interval- or event-based. Each uplink triggers the data processing pipeline specified by a data flow.

Data can be partitioned into topics based on its purpose or schema, which helps retain the structure of the data. A single data point is called a sample and is uniquely identified by device ID, topic, and timestamp.

Connectivity

The communication protocol a device uses to reach akenza: LoRaWAN, HTTP, MQTT, CoAP, NB-IoT, or mioty. Devices living in a vendor cloud, such as Disruptive Technologies, VergeSense, Spaceti, or Haltian, are connected through their respective device connectors.

Integrations

Integrations allow managing devices of connectivity providers (for example Swisscom LPN, Loriot, Actility, or The Things Network). This lets you integrate with existing IoT deployments and manage all assets from a single point.

Data flow

A data flow defines the data processing pipeline:

• Device connector specifies the connectivity used to connect a device

• Device type specifies the type of device and implements payload decoding and encoding

• Output connectors specify one or multiple data destinations

Downlink

Downlinks are commands sent to a physical device (actuator or sensor) to either configure it, for example its sending interval, or trigger an action, such as turning on the lights or closing the blinds. Downlinks are supported for LoRaWAN, NB-IoT, and MQTT devices.

Rules

Rules apply business logic to incoming data in order to trigger actions or alarm notifications.

Output connectors & rule actions

Output connectors specify the data destination for a data flow, while rule actions are the response to a triggered rule. Examples include storing data with the akenza DB connector and sending notifications by email.

Organizations & workspaces

An organization is the account under which a business collaborates across many workspaces. A workspace is where the actual work happens: adding data flows and rules, and managing devices.

Keep going

Tutorials

Step-by-step guides for specific devices, notifications, and enterprise integrations.

Changelog

What's new in akenza, release by release.

Support Center

FAQ, status page, service desk, and feature requests.