I would like to start with...

Use this page when you know what you want to build, but not where to start.

If you are brand new to the platform, first skim Development and Training Examples. They give you the basic mental model fast.

A CRUD service

Typical use cases

• You need a backend for a front-end or admin tool.

• You want standard create, read, update, and delete endpoints.

• You want to expose a collection or table quickly.

This is the fastest path in Rierino. In most cases, you only need to drag & drop an element to an existing runner and click on save.

Start here

• Exercise: Create a CRUD Service

• Video: Build full CRUD under 60 seconds

Learn next

• State Managers for storage patterns

• Runners for selecting microservices for your services

• Gateway Channels for granular control on RBAC

An API endpoint

Typical use cases

• You need more than standard CRUD behavior.

• You want a custom request/response contract.

• You need validation, transformation, aggregation, or branching.

• You want an API-first architecture.

In Rierino, custom APIs usually start as Sagas. A saga is a flow. It can call handlers, states, queries, and other services.

Start here

• Exercise: Create an API Endpoint

Most common flow steps

• Read Data

• Write Data

• Query Data

• Transform Step

• Condition Step

Learn next

• API Flows for details on how to build Sagas

• Handlers for rich set of actions available in steps

Multi-systems integration or orchestration

Typical use cases

• You need to call third-party APIs.

• You need to combine multiple internal services.

• You need fan-out, batching, retries, or transformations.

• You want middleware or ESB-like behavior.

This path is also saga-first. The difference is that the saga coordinates multiple systems, not just one endpoint.

Start here

• Call Rest API

• Video: Integrate External APIs in 2 Minutes

Learn next

• API Based Systems

• Call SOAP API

An internal application

Typical use cases

• You need an admin tool or back-office UI.

• You want forms, lists, editors, and actions without custom front-end code.

• You want internal users to manage data or trigger flows.

Start here

• Exercise: Create a UI Screen

• Video: Build a Functional UI in 2 Minutes

Learn next

• Apps for grouping UIs into applications

• UIs for creating data entry and workflow forms

• API Mapping for mapping backend to frontend

• Data Schema for structuring your data model

• Orchestrate User Task for business process flows

An AI agent

Typical use cases

• You want a conversational interface on top of your services.

• You want an agent that can call tools, not just chat.

• You want to expose capabilities as agent APIs, MCP, or A2A.

Rierino agents are usually built from:

• a governed GenAI model

• one or more tool sagas or tool states

• optional interfaces for richer responses

Start here

• AI Agent Example

• Video: Build Actionable AI Agents in 2 Minutes

• GenAI Models

Learn next

• AI Agent APIs

• Service MCP Requests

• Service A2A Requests

If you are not sure which path fits

Use this quick rule:

• Need standard data APIs fast → start with CRUD service

• Need custom business endpoints → start with API endpoint

• Need multi-system coordination → start with integration or orchestration flow

• Need an internal screen → start with internal application

• Need conversational automation → start with AI agent

If you want one guided path that touches most core concepts, start with the In-depth Exercise.