# Application areas

Where Vraelis Contour is meant to apply. Intended application areas. Vraelis has no customer deployments in them.

> **Intended, not deployed.** Intended application areas. Vraelis has no customer deployments in them.

| Area | Why release integrity matters there |
| --- | --- |
| [Defense](https://docs.vraelis.com/defense) | AI in mission systems, where an unexpected model change can create security and operational risk. |
| [Critical infrastructure](https://docs.vraelis.com/critical-infrastructure) | AI in energy, water and communications, where releases cross operators. |
| [Autonomous systems](https://docs.vraelis.com/autonomous-systems) | AI in robots and vehicles, where models ship to machines in the field. |
| [Government and institutions](https://docs.vraelis.com/government) | Public bodies that need evidence a reviewer can read. |
| [Suppliers and integrators](https://docs.vraelis.com/integrators) | The teams who ship model updates into systems they do not own. |

## What they have in common

- Model updates ship into systems someone else operates.
- An unexpected release can create security and operational risk. A baseline kept on purpose is not an incident.
- Reviewers need evidence they can read: what was approved, what loaded, and what could not be confirmed.

---

Vraelis documentation, Vraelis. https://docs.vraelis.com/application-areas