On this page
MSO Cloud is a multi-tenant platform that brings an organization's marketplace, marketing, social and market data into one governed warehouse, and turns it into dashboards, signals and recommendations with the reasoning attached. It recommends and records; people decide and act. When the data cannot support a number, it says so instead of showing one.
Project status: what is shipped, in beta and planned, with the evidence for each row. Last verified 24 September 2026.
Start by role#
| You are | Start here |
|---|---|
| Evaluating whether the platform fits your organization | Solutions, then What MSO Cloud is |
| Setting up an organization and its data sources | Set up an organization |
| Using it every day | Using MSO Cloud, then your role: Owner, Admin, Editor, Viewer |
| Operating the platform as a super admin | Platform administration |
| Building on it or integrating with it | Architecture, API reference |
| Checking what works today | Project status |
Start by organization type#
Every organization runs one type, and the type decides which screens, data and reports it gets. Organization types explains how a type is composed.
eCom · Marketing · Content Intelligence · Market Intelligence · HR · Finance · Warehouse
The operating loop#
flowchart LR A["Signal"] --> B["Decision"] B --> C["Activation"] C --> D["Validation"] D --> E["Learning"] E -->|"updates the next signal read"| A
The platform reads signals and proposes a decision with its reasoning attached. A person approves what gets activated; MSO Cloud does not act on marketing channels by itself. Validation checks the outcome against the organization's own first-party results, and that result changes how the next signal is ranked. The decision engine describes each step and its safeguards.
Sections#
- Solutions: what the platform solves, by use case and by industry, and the boundaries it holds on security and on numbers.
- Set up: provision an organization, connect its data, configure AI, alerts and sign-in.
- Use: daily work by organization type and by role.
- Features: what each feature does, what data it reads and where it stops.
- Architecture: how the system is built, the invariants it enforces and why each design was chosen.
- Reference: API, roles and capabilities, import templates, glossary.