CrewClaw Cloud-Native Development Platform Architecture

Cloud Architecture · flowchart diagram · Apache-2.0

A layered cloud-native architecture for the CrewClaw development platform, detailing browser access, control plane, runtime orchestration, and model access

Source: https://github.com/machinesociety/ClawLoops/blob/7d2c1214f45e98d01c1e3dc8b8c519a1c2e53488/README/README_zh-CN.md
Curated by machinesociety
Cloud-Native System Architecture Microservices Kubernetes API Gateway AI/ML File Management

Mermaid source

flowchart TB
    A([Browser])
    M([本地文件])

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

    subgraph L2[平台层]
        direction TB
        D[ClawLoops 控制平面]
        E[Web UI]
        K[文件管理服务]
        N[文件上传服务]
    end

    subgraph L3[编排层]
        direction TB
        F[Runtime Manager]
    end

    subgraph L4[运行时层]
        direction TB
        G[每用户 OpenClaw Runtime]
        L[容器文件系统]
    end

    subgraph L5[模型层]
        direction TB
        H[LiteLLM]
        I[上游模型提供商]
    end

    J[(数据存储)]

    A -->|访问入口| B -->|路由转发| D
    B -->|静态资源| E
    E -->|API 调用| D
    E -->|文件管理操作| K
    E -->|文件上传| N
    M -->|选择文件| E
    K -->|文件操作请求| D
    N -->|上传请求| D
    D -->|生命周期管理| F -->|启动/停止/管理| G
    D -->|文件操作| F -->|容器文件操作| L
    D -->|文件上传| F -->|文件写入| L
    D -->|模型访问| H -->|代理请求| I
    D -->|数据持久化| J

    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;
    classDef file fill:#fef3c7,stroke:#d97706,stroke-width:2px,color:#0f172a;

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

What this diagram shows

This diagram illustrates the multi-layered architecture of the CrewClaw cloud-native development platform. It details the flow from browser access through an Entry Layer (Traefik), Platform Layer (Control Plane, Web UI, File Management), Orchestration Layer (Runtime Manager), Runtime Layer (per-user OpenClaw Runtime, Container File System), and a Model Layer (LiteLLM, Upstream Model Providers), including interaction with local files and data storage.

When to use it

Use this diagram to understand the design of a comprehensive cloud-native development environment, visualize the separation of concerns in a layered system, or explain the data and control flow within a platform integrating various services including AI models and file management.

How to adapt it for your project

This architecture can be adapted by swapping out specific components (e.g., different API gateways, container orchestrators, or model proxies), adding new specialized layers for monitoring or security, or integrating with different cloud providers' services. It can also be simplified for smaller applications or scaled for larger enterprise needs.

Key concepts