> For the complete documentation index, see [llms.txt](https://docs.chassy.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chassy.io/user-guides/platform-user-guide/creating-a-platform.md).

# Creating a Platform

## Public platforms

There is an existing set of reference platforms publicly available on Chassy. These software platforms target popular chips like the Nvidia Jetson and Raspberry Pi ecosystems.

## What makes a platform?

### Type

Every platform has a platform type. *Type* defines the nature of the execution hardware target. Existing hardware types platform types:

* `LINUX`
* `WINDOWS`
* `RTOS`
* `FPGA_FIRMWARE`
* `BAREMETAL`

### Compatibility

Compatibility describes in three properties version information and what hardware and software a platform is compatible with.

#### Version ID

Version ID allows you to identify a particular version of a platform.

#### Operating System ID

#### Architecture

Architecture indicates the CPU architecture of the platform. Chassy has several supported architectures for platforms.

* `AMD64`
* `ARM64`
* `ARMv6`
* `ARMv7`
* `RISCV`

### Image

Specifies a Chassy Machine Image (CMI) associated with this platform definition. A CMI is a bootable full system image incorporating the operating system, kernel, device tree definitions intended for a specific platform.

### Name

Specifies a human-readable name assigned to your platform that you will see from the Chassy console.

### Access

Indicates the visibility of a platform. `PUBLIC` platforms can be used by anyone, but `PRIVATE` platforms are only available within your workspace. By default all platforms are private.