Platform Architecture

Design documentation for the FlexGalaxy.AI Application Platform as a Service (APaaS). This covers the platform’s service architecture, cross-cutting patterns, and application validation scenarios.

Note

These are design docs — they describe the intended architecture of the platform. For implementation status and usage guides, see each project’s own documentation.

Overview

• FlexGalaxy.AI Platform Architecture
  • Overview
  • Core Principle
  • Platform Service Map
  • IoT Layer — Technology Stack
  • Execution Contract Model
  • Application Validation
  • Cross-App Architecture Validation Summary

Service Planes

• Data Plane — The Physical World Interface
  • Purpose
  • Services
  • Interaction Model
  • Data Ownership
  • IoT Technology Layer
• Identity Plane — Who and What Has Access
  • Purpose
  • Services
  • Subsystem Relationship
  • Interaction Model
  • Endpoints
  • Data Ownership
• Spatial Plane — Where Things Are
  • Purpose
  • Services
  • Relationship
  • Data Ownership
• Intelligence Plane — What To Do, When, and How
  • Purpose
  • Services
  • Pipeline
  • Two-Tier Planning
  • Data Ownership
• Governance Plane — Rules That Guide All Decisions
  • Purpose
  • Services
  • Policy Hierarchy
  • AI Policy Agent Architecture
  • Data Ownership
• Ecosystem Plane — Distribution
  • Purpose
  • Services
  • Key Interactions
  • Data Ownership

Services

• DeviceAdmin
  • Purpose
  • Responsibilities
  • What DeviceAdmin Is Not
  • Key Entities
  • Relationship with Provisioning Service
  • Alert Monitoring
  • OTA Status Visibility
  • API Surface
  • Implementation
  • Dependencies
  • Consumed By
• ThingIO
  • Purpose
  • Responsibilities
  • How ThingIO Relates to Other Services
  • Account Scoping
  • React SDK
  • Application Integration
  • Data Processing Pipelines
  • API Surface
  • Implementation
  • Dependencies
  • Consumed By
• OTAForge
  • Purpose
  • Responsibilities
  • How OTAForge Relates to Other Services
  • Policy-Driven Rollouts
  • Proxied DDI Endpoint
  • Access Key Model
  • Artifact Management
  • Administration UI
  • API Surface
  • Implementation
  • Dependencies
  • Consumed By
• DotID
  • Purpose
  • Subsystems
  • Keycloak (Core OIDC Provider)
  • Authorization Service
  • Implementation
  • Consumed By
• Org Service
  • Purpose
  • Responsibilities
  • Three-Tier Model
  • Key Entities
  • API Surface
  • Dependencies
  • Consumed By
• IAM Identity Center
  • Purpose
  • Responsibilities
  • Key Scenarios
  • Key Entities
  • Dependencies
  • Consumed By
• StarGate
  • Purpose
  • Responsibilities
  • Technology
  • Pages
  • Dependencies
  • Deployment
• Equator
  • Purpose
  • Responsibilities
  • Key Entities
  • API Surface
  • Dependencies
  • Consumed By
• Marie
  • Purpose
  • Responsibilities
  • Key Query Types
  • API Surface
  • Dependencies
  • Consumed By
• Planner
  • Purpose
  • Responsibilities
  • Key Entities
  • Planning vs Edge Planning
  • API Surface
  • Dependencies
  • Consumed By
• Scheduler
  • Purpose
  • Responsibilities
  • Scheduling Modes
  • Key Entities
  • API Surface
  • Dependencies
  • Consumed By
• Execution Manager
  • Purpose
  • Responsibilities
  • Execution Contract
  • Device State Machine
  • Contract Failure Recovery
  • API Surface
  • Dependencies
  • Consumed By
• Policy Service
  • Purpose
  • Responsibilities
  • Policy Tiers
  • Key Entities
  • API Surface
  • Decision Examples
  • Dependencies
  • Consumed By
• Policy Validator
  • Purpose
  • Responsibilities
  • Validation Checks
  • API Surface
  • Dependencies
  • Consumed By
• AI Policy Agent
  • Purpose
  • Responsibilities
  • Operating Modes
  • Domain Policy Schema
  • Conversation Flow
  • API Surface
  • Dependencies
  • Consumed By
• Marketplace
  • Purpose
  • Responsibilities
  • Key Entities
  • API Surface
  • Dependencies
  • Consumed By

IoT Layer

• IoT Layer — Technology Stack
  • Purpose
  • Technology Map
  • Architecture Overview
  • Integration Topology
  • Credential Model
  • Deployment
  • Alternatives Considered
• ThingsBoard CE
  • Purpose
  • Why ThingsBoard CE
  • Platform Mapping
  • Multi-Tenancy Model
  • Device Connectivity
  • Rule Engine Integration
  • Deployment Architecture
  • API Integration Points
  • Boundaries
• Apache StreamPipes
  • Purpose
  • Responsibility Split
  • Integration with ThingsBoard
  • Pipeline Examples
  • Pipeline Builder
  • Deployment
  • Boundaries
• Eclipse hawkBit + Hara
  • Purpose
  • Why hawkBit
  • What hawkBit Delivers
  • Rollout Management
  • DDI API (Device Domain Interface)
  • Eclipse Hara — Device Client
  • Integration with ThingsBoard
  • Admin Interface
  • Deployment
  • Boundaries

Patterns

• Execution Contract Pattern
  • Context
  • Pattern
  • Consequences
  • Examples
• Edge-Cloud Reconciliation Pattern
  • Context
  • Pattern
  • Consequences
  • Examples
• Policy Architecture Pattern
  • Context
  • Pattern
  • Consequences
  • Examples
• Device Provisioning Pattern
  • Context
  • Provisioning Scenarios
  • Pattern
  • Device Lifecycle
  • API Surface
  • Dependencies
  • Consumed By
  • Consequences
• Supply Chain OTA and Ownership Pattern
  • Context
  • User Story
  • Actors and Accounts
  • Pattern
  • Services Involved
  • Design Decisions
  • Consequences

Application Validation

• WES — Application Validation
  • Overview
  • Platform Services Consumed
  • Planes Exercised
  • Validation Scenarios
  • Architecture Insights Surfaced
• ClearJanitor — Application Validation
  • Overview
  • Ownership vs Operation
  • Platform Services Consumed
  • Planes Exercised
  • Validation Scenarios
  • Architecture Insights Surfaced