> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/devops/devops-overview.md).

# Devops Overview

Overview of the Devops app for building API flows, microservices, gateways, deployments, and runtime operations in Rierino.

## **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="https://1659095931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcnDk3J1AzTgg2NFrGPlh%2Fuploads%2FIhQoIyHILOggQAWWxvk7%2Fimage.png?alt=media&amp;token=950f6d38-db7d-480d-90ab-2558af6ebe17" 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](https://docs.rierino.com/devops/api-event-and-process-flows.md) and building [microservices](https://docs.rierino.com/devops/microservices.md)
* **Gateway:** Key capabilities for configuring [API gateways](https://docs.rierino.com/devops/api-gateway-and-security.md), including authentication customizations
* **Rollout:** Key capabilities for creating & merging [branches](https://docs.rierino.com/devops/branching-and-migration.md), migrating to test & production environments and deployments
* **Control & Admin:** Key capabilities for [controlling](https://docs.rierino.com/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="https://1659095931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcnDk3J1AzTgg2NFrGPlh%2Fuploads%2Ft5Ulcn2y3MTloMWjUB0R%2Fimage.png?alt=media&amp;token=de562805-f32c-42bf-b999-0d2603022d11" 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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rierino.com/devops/devops-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
