> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/other/system-requirements.md).

# System Requirements

This page outlines the system requirements needed to run Ango Hub smoothly.

While Ango Hub does not have hard system or hardware requirements, below are some recommended specs to follow.

{% hint style="info" %}
The type and size of data makes a large difference in what specs you will need. Working on single image assets will be "lighter" than working on long videos or 3D medical assets, for example.
{% endhint %}

## Recommended System Specifications

To ensure optimal performance, please verify that your system meets the following basic requirements:

* **RAM**: At least 8GB is recommended for most workflows. Note that more RAM may be necessary when handling complex medical or 3D multi-sensor fusion workflows.
* **Browser**: The latest version of Google Chrome is the required browser for full compatibility. We do not support Ango Hub on other browsers or older versions of Chrome.
* **CPU**: We do not have a hard CPU requirement, but generally we recommend a mid-range laptop CPU from the last 5 years.


---

# 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.imerit.net/other/system-requirements.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.