Skip to content
MSO CloudDocumentation

Architecture

On this page

In short#

How MSO Cloud is built and why, for engineers who review, extend or integrate with it. Each page ends with its decisions and the gate enforcing each.

1 · SourcesMarketplace seller APIsAd, web, CRM accountsSheets and filesMarket estimatesSystem context2 · IngestAPI pull, upload, sheetIdempotent promotersWatermarks, outboxClassified failuresIngest pipeline3 · WarehouseBronze, Silver, GoldThree planes never mixInteger VNDVietnam timeData planes4 · Web and workerServer pages and tRPCQueues and schedulersPlugins per orgOne AI packageSystem architecture5 · PeopleDashboards, ExploreData assistantMorning briefProposals to approveDecision engineTenancy and security wrap every stepHost picks the organization · forced row-level security · non-bypass runtime roles · encrypted secretsEvery organization runs the same build; plugins, blueprint and configuration rows decide what it sees
The system map. Tenancy and security wrap every step; each column names the page that covers it.

System#

Data#

Decisions and measurement#

Extension and technology#

Where it stops#

These pages describe what is built. Readiness and dated evidence per capability are on Project status; directions are on Future direction.

In this section

API reference