> For the complete documentation index, see [llms.txt](https://docs.akamas.io/quick-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/quick-guides/quick-guides-akamas-in-a-box/aiab-00-install-akamas-in-a-box.md).

# \[AIAB-00] Install Akamas-in-a-box

In this guide, you will install an Akamas-in-a-box, which is a full-functional Akamas instance as a Virtual Machine (VM), running on your workstation or in the cloud.

#### **What you will learn** <a href="#user-content-what-you-will-learn" id="user-content-what-you-will-learn"></a>

* How to install an Akamas instance on a VM
* How to execute some basic Akamas commands

#### **What you will need** <a href="#user-content-what-you-will-need" id="user-content-what-you-will-need"></a>

The minimum requirements to get Akamas running are:

* 2 CPUs
* 8 GB of RAM
* 30 GB of disk space
* an Akamas license.

These requirements refer to the VM that hosts Akamas. If you are creating it on your desktop or laptop it should have at least 4 Cores and 12GB of RAM to effectively run the Akamas VM.

To get started, you only need the following:

* A workstation to install Akamas
* An Akamas license

Notice: an Akamas license should have been sent to you as part of the free trial welcome kit. If that's not the case, please send a request to <info@akamas.io>


---

# 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.akamas.io/quick-guides/quick-guides-akamas-in-a-box/aiab-00-install-akamas-in-a-box.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.
