ClawLoops Layered System Architecture

System Design · flowchart diagram · Apache-2.0

This diagram illustrates the layered architecture of the ClawLoops system, detailing the flow from browser access through ingress, control plane, runtime o

Source: https://github.com/machinesociety/ClawLoops/blob/7d2c1214f45e98d01c1e3dc8b8c519a1c2e53488/README/README_ja-JP.md
Curated by machinesociety
system architecture layered design microservices AI/ML Kubernetes Traefik PostgreSQL

Mermaid source

flowchart TB
    A([Browser])

    subgraph L1[入口層]
        direction TB
        B[Traefik]
    end

    subgraph L2[プラットフォーム層]
        direction TB
        D[ClawLoops 制御プレーン]
    end

    subgraph L3[編成層]
        direction TB
        E[Runtime Orchestrator]
        F[Runtime Manager]
    end

    subgraph L4[Runtime 層]
        direction TB
        G[ユーザーごとの OpenClaw Runtime]
    end

    subgraph L5[モデル層]
        direction TB
        H[モデルサービス / 資格情報プロキシ]
        I[LiteLLM]
        J[vLLM / Ollama / Upstream Providers]
    end

    K[(PostgreSQL)]

    A -->|入口| B -->|セッション検証| D
    D -->|期待状態| E -->|ライフサイクル編成| F -->|起動 / 停止 / 復旧| G
    D -->|モデルアクセス| H --> I --> J
    D -->|プラットフォームデータ| K

    classDef edge fill:#eff6ff,stroke:#2563eb,stroke-width:2px,color:#0f172a;
    classDef plane fill:#dcfce7,stroke:#16a34a,stroke-width:2px,color:#0f172a;
    classDef runtime fill:#f3e8ff,stroke:#7c3aed,stroke-width:2px,color:#0f172a;
    classDef model fill:#ffe4e6,stroke:#db2777,stroke-width:2px,color:#0f172a;
    classDef data fill:#f8fafc,stroke:#64748b,stroke-width:2px,color:#0f172a;

    class A,B edge;
    class D plane;
    class E,F,G runtime;
    class H,I,J model;
    class K data;

What this diagram shows

This diagram shows the multi-layered architecture of the ClawLoops system, starting with a Browser, passing through an Ingress Layer (Traefik), a Platform Layer (ClawLoops Control Plane), an Orchestration Layer (Runtime Orchestrator, Runtime Manager), a Runtime Layer (User-specific OpenClaw Runtime), and a Model Layer (Model Services, LiteLLM, vLLM/Ollama/Upstream Providers). PostgreSQL is used for platform data.

When to use it

Use this diagram when designing or explaining a complex, multi-layered application, particularly one involving AI/ML model serving, runtime management, and robust access control. It's suitable for illustrating system boundaries and component interactions.

How to adapt it for your project

This architecture can be adapted by swapping components within each layer (e.g., different ingress controllers, databases, or model providers). The runtime orchestration can be scaled or modified for various containerization technologies beyond OpenClaw. New layers or services can be introduced for additional functionalities like monitoring or logging.

Key concepts