> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/general/applications.md).

# Applications

akenza consists of four interlinked applications, each covering a different part of an IoT project.

akenza is made up of four applications. They share the same devices, data, users, and permissions, so moving between them needs no export, no second login, and no duplicate configuration.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-microchip">:microchip:</i></td><td><strong>Device Management</strong></td><td>Where you manage your setup: connectivity, devices, data flows, business logic, and users.</td><td><a href="/device-management/create-new-device.md">Devices</a></td></tr><tr><td><i class="fa-chart-line">:chart-line:</i></td><td><strong>Dashboard Builder</strong></td><td>Where you visualize your data. Share dashboards with people who have no akenza account, and run signage screens in your offices.</td><td><a href="/dashboard-builder/dashboard-builder.md">Overview</a></td></tr><tr><td><i class="fa-comments">:comments:</i></td><td><strong>Genio</strong></td><td>Where you talk to your IoT setup through a chat interface, in beta.</td><td><a href="/genio/genio.md">Overview</a></td></tr><tr><td><i class="fa-qrcode">:qrcode:</i></td><td><strong>Device Setup Assistant</strong></td><td>A specialized app for deploying devices at scale, by scanning a QR code on site.</td><td><a href="/device-setup-assistant/device-setup-assistant.md">Overview</a></td></tr></tbody></table>

## Which application to use when

<table><thead><tr><th width="230">If you want to</th><th>Use</th></tr></thead><tbody><tr><td>Connect a device, decode its payload, or decide where its data goes</td><td>Device Management</td></tr><tr><td>Roll out many devices on site and configure them as you install them</td><td>Device Setup Assistant</td></tr><tr><td>Build a view of your data, or share one with someone outside akenza</td><td>Dashboard Builder</td></tr><tr><td>Get an answer without building a view for it first</td><td>Genio</td></tr></tbody></table>

## Application contexts

akenza has two working contexts, and which one you are in determines which applications are available:

* The [organization context](/general/organization-context.md) covers everything under your account, across all of its workspaces.
* The [workspace context](/general/workspace-context.md) covers a single workspace, typically one project or site.

Device Management and the Device Setup Assistant are available in both contexts. The Dashboard Builder and Genio are organization-level applications, so you open them from the organization context, and a dashboard can draw on devices from any workspace you have access to.

## Access and subscription

You may access all applications regardless of your subscription, but functionality is restricted to specific tiers.

Billing and subscription are handled at organization level, and workspaces inherit access to features from the organization they belong to. See [Billing & Subscription](/device-management/managing-an-organization/subscription.md) for the plan your organization is on, and [akenza.io/pricing](https://akenza.io/pricing) for what each tier includes.

{% hint style="info" %}
Some allowances are counted per application. Dashboards and signage screens, for example, have separate allowances in each plan. See [Dashboard Types](/dashboard-builder/dashboard-types.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.akenza.io/general/applications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.