> 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.
***
## Account
An **Account** represents your organization in EasyEdge. It is the top-level structure where you manage **Billing**, **Users**, and **Access Control**.
***
## 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**.
***
## 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.
***
## 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.
***
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://easyedge.gitbook.io/easyedge/getting-started/easyedge-studio/account-structure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.