Systems
Orientation pages for Marqo's major systems — what each one is, the repos and APIs that make it up, and where to go deeper. Use these to build a mental model before diving into a specific repo's docs.
For the full picture of every repo, see the Repository Map. For design docs across all repos, see Architecture & Design.
The big picture
Marqo Cloud is, roughly, three planes:
| System | Responsibility | Primary repos |
|---|---|---|
| Control Plane | Account/index management, APIs, agentic search, integrations, deployment | cloud_control_plane, cloud_control_plane_cdk |
| Data Plane | Running indexes: multitenant EKS, ingest, query, reindexing | cloud_data_plane, reindexing-pipeline |
| Ecommerce | Customer-facing ecommerce & agentic shopping APIs and demos | cloud_control_plane (ecom/agentic), agentic_api_poc_ui, agentic-chat-demo |
Supporting services (cost observability, access management, IaC, CI, clients) are covered in the Repository Map.
How a request flows
A customer request typically enters through an ecommerce / API surface (control plane), which authenticates and routes it to the data plane, where the index actually lives and the query/ingest is executed. Deployment and infrastructure for the control plane are managed via CDK.
Each system page below expands on its piece.