Skip to content

Entities

This page describes the key entities within the Raikoo system and how they relate to each other.

Organizations

An Organization is a group of users that manages users, teams, and their association to projects. Every user is granted a personal, private team when their account is created. Users can join many organizations, and when they join any organization they are automatically placed in the default team.

Organizations are also the scope for several shared resources including database connections, external connections, vector stores, and roles.

Teams

Teams are groups of users who share access to one or more projects within an organization. Every organization has a default team which can be changed in organization settings.

Teams gain access to projects through the TeamXProject association, which links teams to specific projects and controls which team members can access which work efforts.

Projects

Projects are useful to organize and control access to work efforts inside Raikoo. Each project has its own agents, operations, workflows, and custom tools. Users gain access to projects through team associations, allowing granular control of project membership.

Project-level agents and tools can be configured independently, enabling teams to maintain separate AI configurations for different work streams while sharing organization-level resources like database connections.

Workflows

Workflows are composed of operations which can be sequenced and optionally run in parallel. They are designed inside the Workflow Builder tool and can be executed in the Execute Workflow tool. Workflows operate on a workspace, creating, modifying, and deleting files and folders as needed to complete the task.

Workspace

A workspace is a virtual file system where operations store and retrieve data during workflow execution. It provides a consistent environment for all operations within a workflow and maintains state across the entire execution process.

Operations

Operations are individual tasks within a workflow. Operations can be either AI-based tasks or typical code-based tasks (loops, conditionals, data conversions, etc). AI-based operations can be created based on a template or completely customized, and both types of tasks can be configured when placed within a workflow.

Agents

Agents are configurable AI assistants that power both chat interactions and workflow operations. They can be created at either the organization level or project level.

Each agent includes:

  • System Prompt - Custom instructions that guide the agent's behavior and expertise
  • Model Selection - Choice of AI model (Claude Opus, Sonnet, Haiku, etc.)
  • Tool Configuration - Selection of which tools the agent can use
  • Max Tool Roundtrips - Limit on how many tool-calling iterations the agent can perform

Agents are used in two primary contexts:

  • Chat Agents - Interactive conversations with users
  • Workflow Agents - Execution of multi-step AI operations within workflows

AI Providers

AI providers are organization-level connections to external LLM services such as OpenAI, Anthropic, Google, and Azure OpenAI. Each provider holds the API credentials and configuration needed to access that service. Providers expose a set of models to agents, workflows, and chat sessions within the organization.

Multiple providers of the same type can be configured -- for example, separate OpenAI accounts for development and production. Each provider independently manages which models are available through its model management settings.

Model Families

Model families are logical groupings of AI models with an ordered fallback sequence. When a workflow or agent targets a family rather than a specific model, Raikoo selects the best available model from the group at runtime. If the preferred model is unavailable, the next model in the family is tried automatically.

Model families provide an abstraction layer that lets teams upgrade or swap models without modifying individual agents or workflows.

Database Connections

Database connections are organization-level entities that provide secure access to external database systems. Raikoo supports five database types:

  • PostgreSQL - Full-featured relational database
  • MySQL/MariaDB - Popular open-source relational databases
  • SQL Server - Microsoft's enterprise database platform
  • MongoDB - Document-oriented NoSQL database
  • SQLite - Lightweight file-based database (workspace-only, no external connection needed)

Database connections include:

  • Secure Credential Storage - Credentials stored in Azure Key Vault
  • Read-only/Write Controls - Two-level permission model for defense in depth
  • Safety Guardrails - Query validation, row limits, and timeouts
  • SSL/TLS Support - Encrypted connections to database servers

Once configured, database connections can be used by agents through specialized database tools.

External Connections

External connections store platform credentials for integrations with external communication and collaboration services. These are organization-level entities that enable Raikoo to interact with:

  • Microsoft Teams - Enterprise chat and collaboration
  • Slack - Team messaging platform
  • Google Chat - Google Workspace messaging
  • Twilio SMS - Text messaging service
  • Outlook Email - Email integration
  • Outlook Calendar - Calendar and meeting integration
  • Generic Webhooks - HMAC-verified webhook endpoints

External connections provide the authentication credentials needed for triggers and outbound communication tools.

Triggers

Triggers are inbound event listeners that can invoke either chat agents or workflows when external events occur. Each trigger is bound to a specific channel or endpoint and can operate in two modes:

  • Chat Agent Mode - Routes inbound messages to a configured chat agent
  • Workflow Mode - Executes a workflow when an event is received

Triggers enable bidirectional integration with external platforms, allowing Raikoo to both receive and respond to events from services like Teams, Slack, Email, and webhooks.

Vector Stores

Vector stores enable Retrieval-Augmented Generation (RAG) by providing semantic search capabilities over document collections. Raikoo supports 10 vector store providers:

  • Azure AI Search - Microsoft's cloud search service
  • Pinecone - Managed vector database
  • Weaviate - Open-source vector database
  • Qdrant - High-performance vector search engine
  • Milvus - Open-source vector database
  • Chroma - AI-native embedding database
  • MongoDB Atlas - Vector search in MongoDB
  • PostgreSQL (pgvector) - Vector extension for PostgreSQL
  • Redis - Vector search in Redis
  • Elasticsearch - Search and analytics engine

Vector stores are organization-level resources that can be used by agents through vector store tools to retrieve relevant context from large document collections.

Roles

Roles define permission sets that control what users can do within Raikoo. Roles exist at two levels:

  • Organization Roles - Control access to organization-level resources (database connections, external connections, vector stores, organization settings)
  • Project Roles - Control access to project-level resources (agents, workflows, operations, custom tools)

The role system enables granular permission management, ensuring users have appropriate access to resources while maintaining security and compliance requirements.

Conclusion

These entities form the building blocks of the Raikoo platform. Understanding how they relate to each other is key to effectively organizing your AI operations, managing access control, and building powerful workflows that leverage the full capabilities of the system.