****************
Bowtie Downloads
****************

.. spelling:word-list::

   checksums

Bowtie installations are comprised of two distinct types of software: :doc:`clients <client>` and :doc:`controllers <controller>`.
This page explains how to acquire each.

When checksums are available for your desired download, we recommend validating the integrity of the package using an appropriate checksum tool. For example, on Linux, use the command ``sha256sum`` against a download to compare it to the checksum listed on the package distribution page.

.. code:: sh

   sha256sum bowtie-service_amd64.deb

.. _client-packages:

Client Packages
***************

As part of :doc:`setup-client`, you will need to :ref:`client-download`.

Client packages for each major operating system (Linux, Mac, and Windows) are available for download on Bowtie’s `platforms page <https://api.bowtie.works/platforms>`_.

The `package listing page <https://api.bowtie.works/packages>`_ offers a complete list of available versions.
The operating systems listed under "Platform", package formats listed under "Type", and version may be filtered by clicking on them.

Platform pages like `MacOS <https://api.bowtie.works/platforms/MacOS>`_ support appending ``/latest`` to the URL to automatically fetch the latest stable version of a package.
For example, the following links will navigate directly to the latest downloads for each major platform:

- `MacOS package <https://api.bowtie.works/platforms/MacOS/latest>`_

- `Windows installer <https://api.bowtie.works/platforms/Windows/latest>`_

- `Ubuntu Linux <https://api.bowtie.works/platforms/Ubuntu/latest>`_

- `CentOS Stream <https://api.bowtie.works/platforms/CentOS-Stream/latest>`_

Controller Images
*****************

Bowtie :doc:`controllers <controller>` are provided as operating system images.

.. admonition:: Updates and New Images
   :class: hint

   After deploying any initial Controllers, you may elect to leverage :ref:`controller-updates` to bring deployed controllers up-to-date in-place without re-deploying updated machine images. No downsides to this approach exist and update channels are identical to their image-based counterparts.

Cloud Images
------------

Instructions for :ref:`azure`, :ref:`gce`, and :ref:`aws` are available.
These image types are registered in their respective cloud platforms and so you will deploy Controllers against a recent image ID sourced from the official Bowtie account for the public cloud you're operating within.
Downloading from the `Bowtie package distribution and download page <https://api.bowtie.works/platforms/>`_ is unnecessary for these deployment types but we do provide direct launch links for platforms like `AWS <https://api.bowtie.works/platforms/AWS>`_ to expedite the process.

.. admonition:: Regions & Availability
   :class: note

   If you deploy into a region that is not associated with any current Bowtie Controller image, please reach out to your Bowtie representative so we can make plans to support the additional regions.

.. include:: partials/cloud-disk-images.rst

Virtual Machine Images
----------------------

The same `platforms download page <https://api.bowtie.works/platforms/>`_ as for :ref:`client-packages` is available to browse and download these Controller images.

.. include:: partials/compression.rst