# FAQ ## Frequently asked questions ### What is low-code?
Show answer Low-code is a way to build software mostly through configuration, visual tools, and reusable components. It reduces the amount of hand-written code needed for common features such as APIs, workflows, forms, and integrations. Teams still use code for edge cases, custom logic, or deeper extensions.
### What are the types of low-code platforms?
Show answer Low-code platforms usually focus on one or more of these areas: * **Internal app builders** for forms, lists, and back-office screens * **Workflow and BPM platforms** for process automation and task management * **Integration platforms** for connecting APIs, events, and external systems * **Database and CRUD app builders** for data entry and record management * **Backend and microservices platforms** for APIs, orchestration, business logic, and automation
### How does low-code compare with vibe coding?
Show answer Low-code and vibe coding solve different parts of the same problem. Low-code gives teams structured building blocks, reuse, governance, and operational control. It is strong for production systems that need consistency, security, and maintainability. Vibe coding is strong for rapid exploration, prototyping, and generating custom logic with AI assistance. It helps teams move faster when they need something more tailored. They complement each other instead of replacing each other. In practice, teams can use vibe coding to create or refine custom pieces, while low-code provides the stable platform for deploying, integrating, governing, and evolving the full solution.
### What is Rierino?
Show answer Rierino is a low-code backend platform for building microservices, APIs, workflows, and AI agents. It combines service development, orchestration, integrations, and an internal Admin UI in one platform.
### Is Rierino only for low-code teams?
Show answer No. It works for business and technical users together. Teams can move fast with configuration-first building blocks. Developers can still extend the platform when needed. See [Overview](https://docs.rierino.com/introduction/overview) and [Pro-Code](https://docs.rierino.com/devops/pro-code).
### What kinds of applications can I build?
Show answer Rierino fits backend-heavy applications with many workflows, integrations, or data operations. Common examples include: * Information management systems such as PIM, CMS, and MDM * Decision automation such as pricing, risk, and recommendations * BPM and task-driven internal applications * Integration and orchestration layers across many systems * AI-enabled services and agents See [Use Cases](https://docs.rierino.com/introduction/use-cases).
### Does Rierino include a user interface?
Show answer Yes. Rierino includes a built-in Admin UI for internal users. You can use it for forms, data lists, workflows, and operational screens. It is best suited for internal tools, partner portals, and back-office processes. See [User Interface](https://docs.rierino.com/design/user-interface).
### Can I use my own front-end?
Show answer Yes. Rierino is headless. You can connect any customer-facing web, mobile, or external system through APIs. The built-in Admin UI is optional. It is simply the fastest path for internal tooling. See [Platform Architecture](https://docs.rierino.com/introduction/platform-architecture).
### What does the platform architecture look like?
Show answer Rierino has three main layers: * A front-end layer for internal UIs and external channels * A back-end layer with gateways, service runners, and orchestration * A storage layer with pluggable databases, caches, search, and analytics stores This structure keeps the platform flexible and scalable. See [Platform Architecture](https://docs.rierino.com/introduction/platform-architecture).
### Can I build microservices without writing code?
Show answer Yes. You can assemble services from runners, handlers, states, queries, and flows through configuration. This covers common CRUD, orchestration, integration, and automation use cases. You can also add custom code when you need deeper specialization. See [Microservices](https://docs.rierino.com/devops/microservices) and [API Flows](https://docs.rierino.com/devops/api-flows).
### Can Rierino orchestrate existing services?
Show answer Yes. Rierino can orchestrate its own services and external services in the same flow. That includes REST APIs, SOAP services, event streams, and file-based processes. This makes it useful as both an application platform and an integration layer.
### Which data systems does Rierino support?
Show answer Rierino supports multiple storage types through adapters. That includes SQL databases, NoSQL databases, caches, search engines, file systems, and analytics-oriented stores. This helps teams switch or combine data systems without rewriting all service logic. See [State Managers](https://docs.rierino.com/devops/microservices/elements/state-managers) and [Query Managers](https://docs.rierino.com/devops/microservices/elements/query-managers).
### Does Rierino support event-driven and async patterns?
Show answer Yes. Rierino can consume and produce streams such as Kafka. It also supports async triggers, CDC-based flows, and real-time processing patterns. This is useful for high-volume automation and loosely coupled architectures. See [Streams](https://docs.rierino.com/devops/microservices/elements/streams).
### What AI and ML capabilities are included?
Show answer Rierino supports both traditional ML and generative AI. You can use ML for real-time scoring. You can use GenAI for assistants, content generation, and AI agents. You can also expose capabilities through MCP and A2A protocols. See [Built with ML & AI](https://docs.rierino.com/introduction/built-with-ml-and-ai).
### Can I build AI agents on Rierino?
Show answer Yes. Rierino lets you build agents that use governed models, call internal tools, access enterprise data, and trigger actions. This makes the agents useful for real business tasks, not only Q\&A. See [GenAI Models](https://docs.rierino.com/data-science/genai-models).
### Can Rierino use external AI services?
Show answer Yes. You can call external AI APIs from backend flows just like any other integration. This helps with summarization, extraction, classification, and prompt-driven automation. It also keeps authentication, retries, and observability consistent.
### Where can Rierino be deployed?
Show answer Rierino can be deployed in public cloud, private cloud, on-prem, or bare metal environments. This gives teams full control over security, scale, and operating model.
### Who is Rierino a good fit for?
Show answer Rierino is strongest when you need one or more of these: * Large-scale operations * Frequent business change * Many integrations * Data-heavy workflows * Decision automation * Incremental modernization from monoliths See [Use Cases](https://docs.rierino.com/introduction/use-cases).
### What is the fastest way to get started?
Show answer Start with the [Overview](https://docs.rierino.com/introduction/overview), then move into [Installation](https://docs.rierino.com/quick-start/installation) and [Quick Start](https://docs.rierino.com/quick-start). If you already know what you want to build, use [I would like to start with...](https://docs.rierino.com/quick-start/i-would-like-to-start-with...).