> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/4.0/overview/distribution-packages.md).

# Distribution Packages

Flopsar distribution includes:

`Flopsar Server` - Flopsar Server Docker Image. 

`flopsar-agent-X.Y.Z.jar` - Flopsar Agent for JVM 8 and older.

`flopsar-agent-9-X.Y.Z.jar` - Flopsar Agent for JVM 9 and newer.

`flopsar-workstation-X.Y.Z.zip` - Flopsar Workstation application.

`setup-flopsar-workstation-X.Y.Z.exe` - Flopsar Workstation install the application for Windows.

`SHA256.asc` - PGP signed file of all binaries checksums. In order to verify the signature, use our [PGP public key](http://flopsar.com/pgp).

{% hint style="success" %}
All the files can be downloaded from our [release site](http://bin.flopsar.com).
{% endhint %}

## Verifying Packages

In order to verify `SHA256.asc` file, you must first import our public key. You can do this by executing the following command:

```
$ gpg --keyserver pgp.mit.edu --recv-keys 4E1CBB4012E01B7A
```

and verify the file itself:

```
$ gpg --verify SHA256.asc
```

If the file is valid, you should see the output:

```
gpg: Good signature from "Flopsar Technology (Flopsar Technology Secure Key) <pgp@flopsar.com>"
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flopsar.com/4.0/overview/distribution-packages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.