Glossary
Key terms and concepts used throughout this documentation.
Admin Console
The web interface for managing users, roles, AI providers, and system configuration. Part of the Operaide Platform.
Agent DB
A database extension that provides SQLite-based storage for agents to persist and query structured data. It supports snapshots, backups, and cross-instance synchronization via import/export functionality.
AI Provider
A configured connection to an external AI model service (e.g. OpenAI, Azure OpenAI, Anthropic). AI Providers supply the language models that power Aktors and agents. Managed via the AI Provider section in the sidebar.
Aktor
A building block of Operaide workflows. There are two kinds: AktorFunction (does actual work in TypeScript) and AktorComposition (connects Aktors into a reusable workflow). Both look the same from outside: inputs in, output out. This is an implementation of the Composite Pattern.
API Key
An authentication token used to access Operaide's REST APIs programmatically. API Keys can be created and managed per organization in the Organization Settings.
App
A container for one or more Reaktors, along with other resources like databases and APIs. An App is the deployable unit in Operaide — your own project that bundles related workflows and configuration.
App Instance
A live, running version of an App. Multiple instances of the same App can be created, each with its own configuration. While an App is the blueprint, an App Instance is the deployed, operational version.
App Store
A marketplace within the Operaide Platform for discovering, deploying, and sharing Apps across an organization. Provides pre-built applications, starter templates, and community-contributed solutions.
App UI
A feature that allows developers to create custom business user interfaces within their App, beyond the default platform UI.
Connections
Integrations between Operaide and external systems such as SAP, CRM platforms, or databases. Managed in the Connections section of the sidebar, including API credentials, authentication tokens, and data sync settings.
Deployment
The process of publishing a Reaktor from Operaide Studio to the Operaide backend, making it available for execution. Two modes are available: one-time deployment and continuous deployment (Watch mode).
Document Intelligence
Platform capabilities for processing, analyzing, and extracting information from documents.
Embedding Pipeline
The process of converting data (text, documents) into vector embeddings for use in vector databases and RAG applications.
One-Click Tasks
Predefined commands in Operaide Studio that developers can trigger directly from the toolbar — without typing into the terminal. Common tasks such as deploying an App are available as one-click actions out of the box.
Operaide Framework
The open development framework for building AI-powered applications. Provides reusable components and a clear structure for developing Apps, Reaktors, and Aktors. Can be used independently and hosted on any infrastructure.
Operaide Platform
The managed environment for deploying and running Operaide Apps — comparable to what Vercel is for Next.js. Provides hosting, scaling, operations, and tools such as Operaide Studio, Agent DB, App Store, and Admin Console.
Operaide Studio
The browser-based integrated development environment (IDE) for building, testing, and deploying Reaktors. Features a code editor, integrated terminal, AI support (beta), and direct deployment to the Operaide backend.
Organization
The top-level entity in Operaide that groups users, settings, permissions, and resources. Each organization has its own configuration, branding, API keys, and member management.
RAG (Retrieval-Augmented Generation)
A technique that enhances AI model responses by retrieving relevant information from a knowledge base (Vector Database within Agent DB) before generating an answer. Supported through Operaide's data management capabilities.
Reaktor
A deployable workflow registered with Operaide. The platform executes it — handling parallelization, tracing, caching, and diagram generation. A Reaktor wraps an Aktor and adds a public API (input/output schemas).
Reaktor Diagram
An auto-generated visual representation of a Reaktor's structure, showing all elements — Aktors, databases, and APIs — and how they connect. Accessible via the Diagram tab on Reaktor and Reaktor Instance views.
REST API
The programmatic interface through which deployed Reaktors can be invoked. Each Reaktor Instance exposes API endpoints for integration with external systems.
Roles and Permissions
The access control system in Operaide. Determines which functions and UI elements are available to a user. Managed by Platform Administrators in the Organization Settings.
Sandbox
The isolated execution environment in which Operaide runs App code. Only a defined set of modules is available, keeping Apps secure and predictable across tenants.
Starter Template
A pre-built example Reaktor available in the App Store or Reaktors overview (e.g. Basic Chat, Document Analysis, Web Research, Email Assistant). Provides a working foundation that developers can customize.
Streaming
Real-time processing and delivery of responses, allowing partial results to be sent to the client as they are generated rather than waiting for the complete response.
Vector Database
A specialized database that stores data as vector embeddings, enabling semantic search and similarity matching. Used in RAG applications within Operaide's Agent DB.
Vibe Coding
An AI-driven development approach aimed at non-technical users who want to build applications quickly through natural language interaction, without deep technical expertise.
Vibe Engineering
An AI-driven development approach for experts building scalable, secure, and reliable AI applications. Combines natural language interaction with engineering best practices to maintain code quality, architecture integrity, and production readiness.
Workflow
A directed graph of Aktors that describes what should happen. Operaide decides how — execution order, parallelization, caching. Workflows are defined in code; the Reaktor Diagram is auto-generated.
Workspace
An organizational container in the Operaide Platform for grouping related projects, agents, and workflows. Workspaces persist active Operaide Studio sessions and can be resumed or deleted independently of deployed Apps.