Operaide Platform Glossary
This glossary provides clear definitions for key terms and concepts used throughout the Operaide Platform documentation. Use it as a quick reference to better understand the platform and its components.
Aktor
A functional, reusable building block in Operaide. Aktors perform specific tasks (such as data transformation, API calls, or logic operations) and can be composed together to form complex workflows.
AktorFunction
A lightweight wrapper that turns a plain TypeScript function into an Aktor, making it easy to integrate custom logic into workflows.
App Store
A built-in Operaide feature that provides a catalog of ready-to-use templates, starter projects, and reusable components (apps). Apps can be installed per organization and used as starting points or deployed directly.
Deployment
The process of making a Reaktor available for execution in the Operaide Platform. Deployed Reaktors can be accessed via the UI or through REST APIs.
Execution Metrics
Statistics collected for each Reaktor, such as the number of successful and failed runs. Used to monitor workflow health and performance.
Instance (Reaktor Instance)
A specific, deployed version of a Reaktor, including its configuration and settings. Each instance can be managed and monitored independently.
OpenAPI / Swagger
A standard for describing REST APIs. Operaide automatically generates OpenAPI (Swagger) documentation for each deployed Reaktor, making it easy to integrate with external systems.
Organization
A logical grouping within Operaide, typically representing a company, team, or project. Apps and Reaktors are installed and managed per organization.
Reaktor
A deployable workflow in Operaide, composed of one or more Aktors. Reaktors define the logic, inputs, outputs, and settings for a business process or automation.
Reaktor AI Engine
The core execution environment in Operaide where Reaktors are deployed, configured, tested, and monitored.
Registry
The internal Operaide system that stores and manages apps, templates, and framework components. Ensures compatibility and version control.
REST API
A web-based interface that allows external systems to interact with deployed Reaktors. Each Reaktor exposes a REST endpoint for execution.
Settings (Reaktor Settings)
Configurable parameters for a Reaktor instance, defined using the aktorSetting() function. Settings can be changed without modifying the underlying code.
Template
A pre-built app or workflow provided in the App Store. Templates serve as starting points for new projects or as reusable solutions for common use cases.
UI (User Interface)
The web-based graphical interface of the Operaide Platform, where users manage Reaktors, install apps, configure settings, and monitor executions.
Tip: If you encounter an unfamiliar term in the documentation, check this glossary or use the search feature for a quick explanation.