# Devops Overview

## **What the Devops app does**

The Devops app is where you design, deploy, and operate the platform’s core building blocks. It brings the runtime pieces (runners and deployments) together with orchestration (sagas) and the edge layer (gateway and security), so you can ship changes quickly and still keep control.

<figure><img src="/files/SNOhkvFq9sXa6yEkpmNX" alt=""><figcaption><p>Devops App</p></figcaption></figure>

## **Core Devops capability areas**

Devops capabilities fall into four main areas:

* **Runtime:** Sagas, actions, runners and elements used for implementing [API flows](/devops/api-event-and-process-flows.md) and building [microservices](/devops/microservices.md)
* **Gateway:** Key capabilities for configuring [API gateways](/devops/api-gateway-and-security.md), including authentication customizations
* **Rollout:** Key capabilities for creating & merging [branches](/devops/branching-and-migration.md), migrating to test & production environments and deployments
* **Control & Admin:** Key capabilities for [controlling](/devops/administration.md) deployed services and users

## **How Devops components work together**

These building blocks are tightly connected. A typical request starts at the gateway, gets routed to one or more runners, and is often orchestrated through a saga. Supporting configuration, such as queries or model definitions, is usually stored in state managers so it can be updated without redeploying code.

<figure><img src="/files/Xn7szBAFjuo0oiOLbEyv" alt=""><figcaption><p>Relations between Blocks</p></figcaption></figure>

* **Gateway configuration** maps API channels (URL paths) to backend runners and services.
* **Deployments** package and install microservices. Each deployment contains one or more **runners**, and each runner contains **elements** that define what it can do and what it is allowed to access (handlers, systems, states, streams, and so on).
* **Sagas** orchestrate work across runners. A saga is a step graph that calls specific elements, potentially across multiple microservices, and returns a response or emits downstream events.
* **Configuration data** required by steps (for example queries, rules, or ML model definitions) is stored in **state managers** as records. This keeps behavior editable at runtime and easier to migrate between environments.


---

# 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.rierino.com/devops/devops-overview.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.