# Overview
## The naming scheme
Automated Radio, AutoRadio, or most commonly named _AURA_, follows an _Automobile-naming-scheme_.
All components are named after key components of a car.
- **Steering**: This is the single source of thruth, holding all the radio data, hence steering some radio's broadcast.
- **Battery**: Just spleen without steam. That's where your shows, tunes and recordings are managed. Fuelling your broadcast with materials and keeping background jobs running.
- **Dashboard**: Observe and control what's happening. That's the backend user interface of your radio with individual views for hosts and program managers.
- **Engine**: The playout server allowing you to broadcast via FM and web audio streams. Includes silence detection and optional recording options.
The naming convention mentioned above serves as the foundation for the namespacing of individual services.
The following diagram outlines the high-level elements of AURA.
[
](https://gitlab.servus.at/aura/aura/-/raw/main/assets/images/aura-simplified-overview.png)
## Deployment bundles
Same as a car has fixed and moving parts, AURA likewise has parts which are fundamental and parts
which are optional.
In order to keep administrators life simple, we have defined [Docker Compose](https://docs.docker.com/compose/)
bundles, providing a simplified deployment for to most common deployments:
- AURA Web: Contains all the web facing services, including digital asset management
- AURA Playout: Contains all things required for scheduling & broadcasting
- AURA Record: Record audio and periodically sync to archive
:::{tip}
:name: admin-guide
Before digging deeper into AURA development, also make yourself acquainted with the
[Administration Guide](../administration/index.md).
:::