> For the complete documentation index, see [llms.txt](https://docs.ellipsis-drive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ellipsis-drive.com/installation/system-architecture-and-configuration/managing-your-instance.md).

# Managing your instance

When operating your own Private Ellipsis Drive Instance, two system-level accounts are available:

* **Admin**
* **Backoffice**

The initial credentials for these accounts are provided in the configuration file during deployment.

These accounts provide access to the Ellipsis Drive management dashboard, which is available through the UI after login.

The dashboard consists of two main sections:

* User management dashboard
* System health dashboard

***

#### Kubernetes support

Ellipsis Drive runs in Docker containers and is compatible with Kubernetes.

Kubernetes-based scaling is supported but not required. Scaling can also be managed manually through additional virtual machines.

***

#### User dashboard

The user dashboard provides operational insights and controls, including:

* Total storage usage per user
* Quota management
* Usage intensity and activity statistics

***

#### System health dashboard

The system health dashboard provides infrastructure monitoring, including:

* Node status across the Ellipsis Drive cluster
* CPU and memory usage per component
* Storage capacity of raster and vector processing nodes

***

#### Admin vs backoffice accounts

The admin account has full access to all system content, regardless of user-defined permissions. This includes access to all datasets and resources within the instance.

The backoffice account is limited to system-level metadata, user management, and operational monitoring. It does not grant access to user data content.

***

#### Troubleshooting and scaling guidance

If your instance is not performing as expected, use the system health dashboard to identify the bottleneck and apply the appropriate scaling action.

<table><thead><tr><th>Condition</th><th>Action</th><th data-hidden></th></tr></thead><tbody><tr><td>High API CPU usage or slow API responses</td><td>Add additional virtual machines to the API pool</td><td></td></tr><tr><td>Raster storage is full or near capacity</td><td>Increase disk size or add an additional virtual machine to the raster storage pool.</td><td></td></tr><tr><td>Vector storage is full or near capacity</td><td>Increase disk size or add an additional virtual machine to the vector storage pool</td><td></td></tr><tr><td>Raster activation nodes are saturated</td><td>Add virtual machines to the raster activation pool</td><td></td></tr><tr><td>Vector activation nodes are saturated</td><td>Add virtual machines to the vector activation pool</td><td></td></tr><tr><td>Slow API responses without high CPU usage</td><td>Add a virtual machine to the cache storage pool</td><td></td></tr><tr><td>File storage is full or near capacity</td><td>Increase underlying storage volume</td><td></td></tr></tbody></table>