> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/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/akamas-docs/3.6/getting-started/akamas-free-trial.md).

# Free Trial

Akamas offers a Free Trial option to quickly understand Akamas concepts and capabilities and experience the power of its AI-based optimization platform.

You can join Akamas Free Trial quickly:

1. **Fill out this** [**form**](https://www.akamas.io/free-trial/) on the Akamas website;
2. **Receive credentials** to access your dedicated **Akamas server** (a cloud instance on AWS EC2) - optimally you can also **download** **& install** the **Akamas CLI** and learn how to fully automate the optimization process;
3. **Explore** already executed optimization studies or **create & run** new studies to optimize a microservice app at both the JVM runtime and Kubernetes level - here you can take advantage of [Akamas Quick Guides](https://docs.akamas.io/quick-guides/quick-guides-aias).

What you will get:

* **Understand** the Akamas methodology
* **See** Akamas AI-powered optimization in action
* **Learn** to use Akamas by following the how-to guides
* **Familiarize** yourself with Akamas UI and CLI
* **Touch** the benefits Akamas can deliver to your organization

Enjoy!


---

# 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/akamas-docs/3.6/getting-started/akamas-free-trial.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.