Skip to content
MSO CloudDocumentation

System context

On this page

In short#

One deployment serves every organization: people reach it through their organization's host, first-party data and third-party estimates flow in, and it calls model, notification and storage services. The platform reads its sources and never writes to them.

PeopleOrg members and adminsSuper admins (platform staff)through the organization's hostOrganization directoryLDAP/AD or OpenID Connectper organization, when enabledMCP clientsAn engineer's own toolingreads the metric catalogMSO CloudOne deployment, every organizationHost decides the organizationOrg and brand isolation in the databaseThree data planes never mixCredentials never returnedNumbers traced to supplied factsRecommends; people actthe system boundaryLanguage-model providersOrdered failover list per orgthrough one AI packageNotification transportsWeb push, email, Telegram, Zaloplatform, org, person all agreeObject storageBackups and uploads, privatedownloads proxiedFirst-party sourcesMarketplaces · ad, web, search, CRM accounts · sheets and filesscheduled pull, upload, sheet bindingThird-party sourcesMarket estimates · social listeningown estimate store, always labelled
The platform as one box: who reaches it, what flows in and which services it calls.

An organization owns brands; a brand is a partition inside it, not a separate tenant or installation. Nothing in the box is built per customer: an organization runs what its plugins and blueprint enable, inside its own row-level-security scope. The containers inside the box: System architecture.

People and directories#

Actor What they do Where
Org member (editor, viewer) Read dashboards and reports, explore data, ask the data assistant The organization's workspace
Org admin (owner, admin) Connectors, members, brand access, AI, alerts, menu, directory login, backups /settings
Super admin Platform staff: create organizations, apply blueprints, enable plugins /admin
Org directory (LDAP/AD, OpenID) Authenticates members where a super admin turned directory login on Called over an encrypted link

Owner and admin hold the same capabilities; rank separates them. A super admin holds no membership in any organization. Full matrix: Roles and capabilities matrix.

Systems it reads#

Source Examples Rule
First-party marketplace TikTok Shop, Shopee, Lazada seller APIs; Shopee and Lazada CSV/XLSX exports The only ground truth for order money
First-party marketing Google Ads, Meta Ads, TikTok Ads, Shopee Ads, GA4, Search Console, LinkedIn Page, Brevo Conversions stay with the reporting platform
First-party records A Google Sheets workbook or uploaded file: people, budget, finance, a corpus Declared datasets, no engineer needed
Third-party market intel Market-data feeds and file drops, social listening Own store, labelled estimate, never a KPI
Shared trend feed The social trend vendor API, read by one platform connector for every organization One account and sync; org-less tables read through a gated reader

Connector family is the data plane, and the planes never mix. A shared dataset is synced once for all organizations and read only by those that hold it: Data planes and the warehouse.

Services it calls#

Service What Rule
Language-model providers Google, Anthropic, OpenAI, OpenRouter, Ollama, Mistral, DeepSeek, OpenAI-compatible Ordered failover list per org; model never shown
Notification transports Web push, email, a Telegram bot, a Zalo Official Account The in-app inbox needs no transport
Object storage S3-compatible bucket for backup archives and uploads Never public; downloads proxied through the app
MCP clients An engineer's own tooling reading the metric catalog Same catalog as every dashboard
Connected apps ContentHeat, a separately deployed app that signs in through MSO Cloud Tokens, Platform API reads, signed webhooks; never a database connection

Every model call goes through the platform's AI package. MCP details: MCP server.

What crosses the boundary#

System outside the boxThe platform readsThe platform writesMarketplace seller APIsorders, products, inventory, creatorsneverAd, web, search and CRM accountsspend, conversions, sessions, leadsneverGoogle Sheets and uploaded filestabs and files through a mapping templateneverMarket-data feeds, social listeningestimates and mentions, labelled as suchneverLanguage-model providersthe reply texta prompt built from supplied factsNotification transportsnothingmessages that passed all three gatesObject storagearchives and uploads on requestarchives and uploads, never publicMember directory (LDAP/AD, OpenID)the member's attributesone bind for that sign-inMCP clientsa tool callcatalog answers, same as a dashboard
Direction of every crossing. Sources are read only: the platform never writes to a marketplace or an ad account.

An approved action becomes manual steps for a person; the platform reads marketplaces and ad accounts and never writes to them. Outbound messages pass three gates before leaving: Notifications. Third-party estimates are periodic, not real time, and their provider is never named in the product. Connector readiness: Project status.

MSO Cloud is the OpenID Connect issuer for separately deployed apps. Apps receive tokens, Platform API reads and signed webhooks, and never a database connection: App family and sign-in.

Where it stops#

Connector readiness, directory sign-in and app-family readiness are on Project status.

Decisions#

Decision Why Enforced by
The request's host picks the organization; the cookie decides only on a platform host A cookie remembers the last organization; on a tenant host it can name another one Audits refuse session-organization reads and origin-built URLs
Every organization runs the same build; differences are plugins, blueprint and config A branch on one customer turns the platform into forks the next customer inherits A shrink-only ratchet audit refuses customer names, pinned slugs, account ids
Sources are read, never written A write path to an ad account turns a recommendation into an unreviewed action The action package records approval and returns manual steps; dispatch is closed by policy

Mechanisms: Tenancy and security, Configured, not coded.