Glossary
Definitions for the main Rierino terms used across the documentation, including runtime, UI, configuration, integration, and AI concepts.
In brief: This glossary defines the core terms used across Rierino documentation. Use it when you want a quick meaning, then follow the linked pages for full setup and reference details.
Core platform terms
Admin UI
The built-in web interface for internal users. Use it to manage data, workflows, operations, and configuration.
See User Interface.
App
A top-level container in the Admin UI. An app groups related screens, menus, and navigation for a business domain or team.
See Apps.
Branch
An isolated workspace for making changes before merging or migrating them to another environment.
See Managing Branches.
Deployment
A packaged runtime unit that installs one or more runners onto a target environment.
See Deployments.
Element
A building block inside a runner. Elements define what a runner can access and what it can do.
See Elements.
Gateway
The entry layer for external and internal API access. It handles routing, authentication, sessions, and edge security.
See Gateway & Security.
Microservice
A deployable backend service that handles part of the platform’s business logic, integration, or data processing.
See Microservices.
Rierino
A low-code backend platform for microservices, orchestration, integrations, internal UI, and AI-enabled operations.
See Rierino Overview.
Runner
The main runtime container for microservice capabilities. A runner holds elements such as handlers, systems, states, and streams.
See Runners.
Saga
A flow definition used for APIs, events, and process orchestration. A saga coordinates steps across one or more runners.
See API Flows.
Screen
A page inside an Admin UI app. Most screens combine a lister and an editor around one business task or record type.
See Layout & Navigation.
System
A shared configuration object for connecting to a data store, external API, message stream, or other integration target.
See Systems.
Runtime and orchestration
Action
A reusable function call, usually backed by a handler action with predefined parameters.
See Actions.
Event
A payload passed between steps, handlers, streams, or services. Events are the main unit of processing in many flows.
See Event Step.
Event step
A saga step that sends an event payload to an event handler for execution.
See Event Step.
Handler
A runtime component that executes logic when a runner receives an event or request.
See Handlers.
Listener
A runner element that watches for changes in state managers and reacts to them.
See Listeners.
Query manager
A runner element used to execute queries against a backing data system.
See Query Managers.
State manager
A runner element used to store and retrieve aggregate data. It provides a consistent model across different data stores.
See State Managers.
Step link
A connection between saga steps. Step links define how a flow moves from one step to the next.
See Step Link.
Stream
A runner element for input or output data flow, such as events, journals, or CDC feeds.
See Streams.
Transform step
A saga step that changes an incoming event before passing it onward.
See Transform Step.
Condition step
A saga step that checks a condition and routes flow based on the result.
See Condition Step.
Gateway and API terms
API flow
A saga used as a request-response API or service orchestration layer.
See API Flows.
Gateway channel
A mapping from an external path segment to a backend system or service route.
See Gateway Channels.
Gateway server
The service that accepts API requests at the edge and routes them into runners, flows, or gateway-native features.
See Gateway Servers.
Gateway service
A gateway-side integration for capabilities handled directly by the gateway, such as logging or file operations.
See Gateway Services.
Gateway system
A gateway configuration that defines how the gateway reaches backend runners or services.
See Gateway Systems.
Gateway token
A token definition for authentication details, claims, and user-type-specific access behavior.
See Gateway Tokens.
OpenAPI specification
A machine-readable API description generated from runner and saga configuration.
UI and design terms
Editor
The part of a screen used to view, create, and update one selected record.
See Layout & Navigation.
Lister
The part of a screen used to search, filter, and select records.
See Listers.
Menu action
A user-triggered action exposed through lister, editor, selection, or widget menus.
See Menus.
Option
A configurable list of values used in UI fields, selectors, and related display logic.
See Options.
Source
An API mapping that connects an Admin UI screen to listing, reading, or writing endpoints.
See API Mapping.
Translation
A configurable label or text resource used to localize the UI.
See Translations.
UI
A screen definition in the Design app. It controls layout, widgets, menus, and screen behavior.
See UIs.
Widget
A UI component used to display or edit a field, object, array, or related data.
See Widgets.
Configuration and logic terms
Business rule
A configurable decision rule stored as data instead of hard-coded logic.
See Business Rules.
Dynamic handler
A runtime-editable handler definition used to customize logic without Devops changes.
See Dynamic Handlers.
Query
A reusable query definition stored as configuration data and executed by a query manager or flow.
See Queries.
Schema
A structural definition of data fields, types, and validation rules used across the platform.
See Data Schema.
AI and data science terms
A2A
Agent-to-Agent protocol support. It lets other agents delegate tasks to Rierino-exposed agent capabilities.
See Built with ML & AI.
AI agent
A configured capability that combines models, tools, and orchestration to answer, decide, and act.
See GenAI Models.
CEP
Complex Event Processing. It evaluates streams over time for windows, patterns, and real-time analytics.
GenAI model
A governed large language model or similar generative model configured for prompts, agents, or automation.
See GenAI Models.
MCP
Model Context Protocol support. It exposes selected Rierino capabilities as tools and resources for LLM clients.
See MCP Servers.
ML model
A machine learning model used for scoring, prediction, classification, or other inference tasks.
See ML Models.
RAI
Rierino’s built-in AI assistant for guided productivity inside the platform.
See Built with ML & AI.
Related pages
Last updated