> 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/configuration/configuration-overview.md).

# Configuration Overview

Rierino provides low/no-code capabilities for designing and deploying configurations in real-time.

## **What the Configuration app does**

The Configuration app is where you define reusable “logic as data”. Instead of hardcoding queries, rules, or script-based handlers into a service, you store them as managed records and let runners and sagas load them at runtime. This keeps behavior easier to audit, migrate, and adjust across environments.

<figure><img src="https://1659095931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcnDk3J1AzTgg2NFrGPlh%2Fuploads%2FV2GK20I0ryufZQwhuHk2%2Fimage.png?alt=media&amp;token=f252e376-64ec-45b2-a65e-c00e683df425" alt=""><figcaption><p>Configuration App</p></figcaption></figure>

## **Core Configuration capability areas**

Configuration capabilities fall into three main areas:

* **Queries:** Define portable, parameterized queries that can be executed from handlers and sagas.
* **Business Rules:** Store and manage rulesets as configuration, so decision logic can evolve without service redeploys.
* **Dynamic Handlers:** Add or customize handler logic during runtime, typically for rapid iteration and controlled extensions.

## **How Configuration components work together**

In practice, these show up inside API flows and microservices. A saga step might execute a stored query, evaluate a ruleset, or run a dynamic handler action, while the runner enforces what systems and state managers are allowed. That separation gives you fast iteration without losing control over access, deployment, or operational safety.


---

# 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/configuration/configuration-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.
