> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/5.1/planning-and-installation/bare-metal/obtaining-the-weka-install-file.md).

# Obtain the installation packages

Register on get.weka.io and download the installation package for the selected installation path.

## Register with get.weka.io

Register with [get.weka.io](https://get.weka.io/ui/dashboard) before downloading installation packages.

**Before you begin:** Use an organization email address. Personal email addresses are not supported. Skip these steps if you already have a get.weka.io account.

**Procedure**

1. Open [get.weka.io](https://get.weka.io/ui/dashboard), then select **Create an account**.

<div data-with-frame="true"><img src="https://2745724548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZW262oqYA8pNNfGvXjHa%2Fuploads%2FEH4yRpIWyWGM76mzAJ6m%2Fget.weka.io.png?alt=media&amp;token=349c3e9a-70f3-479e-8b5f-a3161379317c" alt="Create an account" width="425"></div>

2. Enter your organization email address. Select **I’m not a robot**, then select **Send Registration Email**.
3. Open the registration email from WEKA. Select its confirmation link.
4. Enter your email address, full name, and password. Then select **Create Account**.

WEKA reviews your request. Sign in after you receive the approval email.

## Download the WEKA installation packages

Download the package for your installation path.

**Before you begin:** Register with get.weka.io and receive approval. Identify whether you install with WSA or manually.

**Procedure**

1. Open [get.weka.io](https://get.weka.io/ui/dashboard), then sign in.

The dashboard lists available installation packages.

<div data-with-frame="true"><figure><img src="https://2745724548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZW262oqYA8pNNfGvXjHa%2Fuploads%2F6dAnvySvqgASwj4ohyvf%2Fget.weka_dashboard.png?alt=media&amp;token=289b1145-868a-4975-8978-383b8d9edcd0" alt="get.weka.io dashboard showing available installation packages"><figcaption><p>get.weka.io dashboard</p></figcaption></figure></div>

2. Download the required package:
   * For automated installation with WSA, contact the Customer Success Team to get the WSA image.
   * For manual installation, select **Releases**, select the required release, then download the WEKA software tarball.

The download link includes an access token. The capture masks this token.

<div data-with-frame="true"><figure><img src="https://2745724548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZW262oqYA8pNNfGvXjHa%2Fuploads%2FIH35SKJATeEEcc7ClEhl%2Fget.weka_releases.png?alt=media&amp;token=b74f9fb5-b7dc-4fa1-b84e-e755ab489169" alt="Releases page showing the WEKA software tarball download link"><figcaption><p>Releases download page</p></figcaption></figure></div>

## Continue installation

Continue with the installation path that matches the downloaded package:

* WSA image: [Install WSA](/5.1/planning-and-installation/bare-metal/install-the-weka-cluster-using-the-wsa.md)
* WEKA software tarball: [Install OS and WEKA software](/5.1/planning-and-installation/bare-metal/manually-install-os-and-weka-on-servers.md)


---

# 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.weka.io/5.1/planning-and-installation/bare-metal/obtaining-the-weka-install-file.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.