Skip to main content
Version: Current

IB-X Application Architecture

Overview​

The IB-X Application Architecture describes how the platform is deployed, connected, and operated across cloud and customer environments.

IB-X follows a centrally governed architecture, where the AI Command Center acts as the unified environment for designing, executing, monitoring, and managing agents.   Execution may occur centrally or within the customer network, depending on automation requirements, while governance and visibility always remain centralized.

This architecture applies consistently across both SaaS and self-hosted deployment models.

Architecture Scope​

This document focuses on:

  • Deployment boundaries between IntelliBuddies Cloud and customer environments
  • Network and execution flow of agents
  • How local execution is incorporated when UI or on-premise access is required
  • How external services and integrations are accessed

It intentionally avoids detailing individual platform components, which are covered separately.

🖼️ Reference Diagram: IB-X Application Architecture

Deployment Models​

AI Command Center Deployment Options​

The AI Command Center is the central runtime and governance environment of IB-X.   It supports two deployment models without changing agent behavior, lifecycle, or execution semantics.

SaaS Deployment (IntelliBuddies Hosted)​

  • AI Command Center is hosted and managed by IntelliBuddies
  • Customers access the platform via a browser
  • Scalability, availability, and upgrades are centrally managed
  • Suitable for customers seeking minimal infrastructure management

Self-Hosted Deployment (Customer Managed)​

  • AI Command Center is deployed within customer-controlled infrastructure
  • Can run:   - On-premise   - In a private cloud or isolated VPC
  • Enables complete control over data residency, network isolation, and compliance

Note:   The architecture diagram represents a logical view. Component placement does not imply a fixed hosting model.

Centralized Execution & Governance Model​

IB-X does not separate control and execution into different planes.

  • Agents are designed, executed, and monitored within the AI Command Center
  • All agent execution instances are persisted in the AI Command Center backend
  • Monitoring, logs, execution state, retries, and operational actions are handled centrally

Every agent execution produces an execution instance that can be:

  • Tracked
  • Monitored
  • Managed
  • Audited

This applies equally to SaaS and self-hosted deployments.

Local Execution Within Customer Network​

Some automation scenarios require:

  • UI interaction with desktop or web applications
  • Access to on-premise systems
  • Execution within restricted customer networks

In these cases, execution is delegated to Local Agent components running inside the customer’s LAN.

Key characteristics:

  • Local execution is invoked and governed centrally
  • Only the execution step runs locally
  • Control, monitoring, and lifecycle management remain in the AI Command Center
  • Execution instances are persisted centrally

Local execution is used only when required and does not represent a separate execution model.

External Integrations & Connectivity​

Agents interact with external systems through Activities and Connectors, including:

  • Enterprise applications (ERP, CRM, HR, Finance)
  • SaaS platforms
  • Databases and data sources
  • APIs, files, messaging systems, and event streams

These integrations:

  • Are invoked as part of agent execution
  • Can be accessed from central or local execution contexts
  • Are governed through the AI Command Center

AI Services & Entitlements​

IB-X supports AI consumption through two models:

Managed AI Services​

  • Third-party AI services are accessed via the Integration Gateway
  • Usage is governed using IB-X Currency
  • Subscription and entitlement validation is handled centrally

Bring Your Own Keys (BYOK)​

  • Customers provide their own credentials for supported AI providers
  • IB-X invokes AI services using customer-managed keys
  • Enables flexibility in cost and compliance

Both models integrate seamlessly into agent execution without altering deployment topology.

Network & Security Boundaries​

The architecture enforces clear boundaries:

  • Central platform services operate in the IntelliBuddies Cloud or customer-managed environment
  • Local execution components operate strictly within customer networks
  • External integrations are accessed via secure, controlled connections
  • No direct exposure of customer systems is required

Summary​

The IB-X Application Architecture:

  • Uses the AI Command Center as a unified runtime and governance environment
  • Supports SaaS and self-hosted deployment models
  • Executes agents centrally by default, with local execution only when required
  • Maintains centralized monitoring and lifecycle management
  • Integrates securely with enterprise systems and AI services

This architecture enables IB-X to scale across diverse enterprise environments while preserving governance, visibility, and operational consistency.