# Architecture overview

Kameleo is composed of cooperating components running both locally (on your machine) and in the cloud. Understanding their responsibilities helps when automating flows, diagnosing issues, or scaling usage across teams.

flowchart LR
  %% Layout
  classDef cloud fill:#eef6ff,stroke:#88a,stroke-dasharray:5 5;
  classDef node fill:#ffffff,stroke:#999,rx:8,ry:8;

  %% Left
  GUI[GUI]:::node
  SCRIPT["Your automation scripts"]:::node

  %% Top
  SERVICES["Kameleo Cloud Services"]:::cloud

  %% Center
  ENGINE["Local Engine instance"]

  %% Right (Profiles)
  subgraph P1["Chroma instance"]
    direction TB
    CHROME(("Profile #1 data"))
  end

  subgraph P2["Junglefox instance"]
    direction TB
    FIREFOX(("Profile #2 data"))
  end

  %% Connections
  SERVICES <--> ENGINE
  GUI --> ENGINE
  SCRIPT --> ENGINE
  ENGINE --> P1
  ENGINE --> P2

Kameleo Engine (local)
The central orchestrator that runs on your computer. It exposes a local REST API (default: http://localhost:5050) used by the Desktop GUI, your automation scripts (SDKs / HTTP calls), and other tools. All functional operations you perform - creating profiles, launching browsers, exporting cookies, shutting down sessions - are executed by this process.

GUI (Desktop UI)
Primarily a rich client atop the local API, but with added convenience and productivity features.

Automation scripts (SDKs & custom code)
Your scripts (C#, TypeScript/JavaScript, Python, etc.) talk directly to the local API or via official SDKs. They perform the same actions the GUI does, enabling CI/CD and large‑scale orchestration.

Cloud services
Kameleo cloud-side infrastructure provides authentication, subscription & team management, fingerprint generation, and other remote capabilities the Engine depends on. The Engine maintains secure sessions with these services as needed.

Profile data (virtual browsers)
Each running browser instance (e.g., Chroma, Junglefox) is tied to a virtual browser profile storing fingerprint parameters, storage (cookies, localStorage), stateful artifacts, and session history. The Engine persists and updates these as you operate the profile.