> 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/readme.md).

# Sandbox options

## Introduction

This section provides a set of "quick guides" that can be used during the Akamas Sandbox (see here the different [options](/quick-guides/readme.md) available).

While all the guides are meant to be self-contained, it is advised to first read this [introduction](broken://pages/RzV0DOdxUeXDX31wHuCZ) about Akamas and its [architecture](broken://pages/3ii2F2Dzgep2C1qUisXQ). You may also refer to the[ glossary](broken://pages/nBcpkquVpfYViiwhQjKt), when necessary.

## Akamas Sandbox options

There are two options when running an Akamas Sandbox:

1. **Akamas-in-a-sandbox (AIAS)**
   * Akamas-provided sandbox as cloud instance - no setup time
   * sample applications (e.g. Online Boutique) included in the AIAS environment as optimization targets
   * predefined optimization study and artifacts available to quickly familiarize with Akamas concepts
   * access via both UI and CLI (from your own workstation)
2. **Akamas-in-a-box (AIAB)**
   * Akamas server to be installed on your own system (server/laptop)
   * sample applications (e.g. Online Boutique) included in the AIAB package as optimization targets
   * ability to connect Akamas to your own environment to be managed.

The AIAS option is the standard one that is activated, while the AIAB option is available upon request.


---

# 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/readme.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.