# Types of AuterionOS Images

Skynodes that are shipped by Auterion as part of the [evaluation kit](/hardware-integration/skynode/evaluation-kit.md) come with **unsigned development builds** of AuterionOS pre-installed. Skynodes that are integrated by manufacturers into their final product are typically shipped with **signed production builds** of AuterionOS.

A summary of the two common use cases is shown in the following table:

|              | **Production**                          | **Development**                  |
| ------------ | --------------------------------------- | -------------------------------- |
| **Signed**   | Used on vehicles purchased by customers | Special case                     |
| **Unsigned** | Special case                            | Used during OEM integration only |

Once a vehicle is distributed to end-users, the manufacturer should deploy signed production images only. The production image ensures that entry doors such as SSH are locked down and tampering is prevented. Signed images guarantee that no images from other sources than the manufacturer can be installed to cirvumvent the safety guards.

The sections below explain the differences between these image types in more detail:

## Production versus Development Images

Depending on your particular circumstances you might receive access to the development or production builds of AuterionOS. Below are the differences between these two types of images, particularly for the case of Skynode:

| Feature                                 | Production Build                                                                                                                              | Development Build                                                                                                                                                                                |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **AuterionOS Image Signature**          | These images are typically signed (see below for more details on signatures)                                                                  | These images are typically not signed (see below for more details on signatures)                                                                                                                 |
| **SSH**                                 | Access only with authorized keys that were [included in AuterionOS](/hardware-integration/auterion-developer-tools/adding-ssh-keys.md) before | Access to anyone with the [default logins](/hardware-integration/flight-controller-customization/flight-controller-shell.md#ssh-to-the-mission-computer) "root/auterion" and "auterion/auterion" |
| **Serial Console of Flight Controller** | Disabled                                                                                                                                      | Full Nuttx Shell                                                                                                                                                                                 |
| **Serial Console of Mission Computer**  | Disabled                                                                                                                                      | Full TTY shell                                                                                                                                                                                   |
| **Serial Console of Bootloader**        | Disabled                                                                                                                                      | Enabled                                                                                                                                                                                          |
| **User account "auterion"**             | Nonexistent                                                                                                                                   | Enabled                                                                                                                                                                                          |
| **APX4 Binary**                         | "Production" APX4 binary on mission computer is used for flashing                                                                             | "Development" APX4 binary on mission computer is used for flashing                                                                                                                               |
| **APX4 Parameters**                     | Only a "safe" subset of parameters can be changed                                                                                             | All APX4 parameters can be changed to arbitrary values, which can cause damage to the drone or harm people                                                                                       |

{% hint style="info" %}
Please [submit a ticket](https://auterion.zendesk.com/hc/en-us) if you are a manufacturer and need help setting up production builds, or if you are a developer required to work with a production build where you do not have SSH access.
{% endhint %}

## Signed versus Unsigned Images

Installing a signed AuterionOS image prevents future installations of unsigned and therefore unauthorized images on this particular Skynode.

Both production and development images can be signed. Once a signed AuterionOS image is installed onto the device, it will only accept signed images in the future. For this reason developers often work with unsigned development images of AuterionOS and only sign the production images.


---

# Agent Instructions: 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:

```
GET https://docs.auterion.com/hardware-integration/auterionos-system-guide/types-of-auterionos-images.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.