> For the complete documentation index, see [llms.txt](https://easyedge.gitbook.io/easyedge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://easyedge.gitbook.io/easyedge/getting-started/easyedge-studio/account-structure.md).

# Account Structure

EasyEdge offers a flexible multi-level hierarchy that adapts to both internal and external use cases. This structure helps you manage users, billing, and deployments across departments, sites, and customers.

<figure><img src="/files/uCzaLP32Nx48QWIyYbEM" alt=""><figcaption></figcaption></figure>

***

## Account

An **Account** represents your organization in EasyEdge. It is the top-level structure where you manage **Billing**, **Users**, and **Access Control**.

<figure><img src="/files/Di8iKHJevJDPB0otDlmK" alt=""><figcaption></figcaption></figure>

***

## Entity

Within each Account, you can create **unlimited Entities**.\
An Entity typically reflects an **organizational unit**, and its usage depends on how your organization or services are structured.

**Common examples:**

* A company with multiple departments can create one Entity per **Department**.
* A service provider managing multiple clients can create one Entity per **Customer**.

<figure><img src="/files/U7T2ohh5axWPCzDtnCsa" alt=""><figcaption></figcaption></figure>

***

## System

Within each Entity, you can create **unlimited Systems**.\
A System typically represents a **site, facility, or project deployment**.

**Common examples:**

* A company department managing several factory locations can create one System per **Site** within the department Entity.
* A service provider with multiple customer locations can create one System per **Installation Site** under each customer Entity.

<figure><img src="/files/TvKtTAASo7AUqdHgVISS" alt=""><figcaption></figcaption></figure>

***

## EdgeNodes

Each **System** can include one or more **EdgeNodes**, which are responsible for collecting, transforming, and sending data between field devices and connected applications.

An **EdgeNode** is the execution environment where EasyEdge runs at the edge. It can be deployed in two ways:

* **Native Installation** on supported Linux-based systems
* **Containerized Deployment** using Docker or equivalent runtimes (Linux or Windows environments)

{% hint style="info" %}
*(See the EasyEdge Node section for technical details.)*
{% endhint %}

EdgeNodes within the same System (or Site) can operate independently or collaboratively:

* They can **simultaneously contribute to one or more Namespaces**, depending on the number and type of **Applications** connected.
* This enables flexible deployment strategies—from single-gateway to multi-gateway architectures—while maintaining unified data models.

{% hint style="info" %}
🛡️ **High Availability:** For critical applications, EasyEdge supports high availability configurations where multiple EdgeNodes can ensure data continuity and system resilience. In the event of a node failure, others can continue processing and delivering data without interruption.
{% endhint %}

EdgeNodes can be added, configured, and managed remotely via **EasyEdge Studio**, ensuring seamless orchestration and monitoring across distributed environments.

***