From your data lake to your boardroom.
One platform · five layers · open at every layer
Read top-down, the way an executive sees it. Source systems feed a workspace; the workspace is shaped in the studio; the engines run in the hub; the outcome reaches the boardroom. Data, agents and reference models are yours to bring at every layer.
Where leadership reads the decision — and what it cost to be resilient.
Where the engines run, third-party agents run beside them, and the artifacts live.
Where intent is authored — policies, drivers, filters, risks, scenarios, flows.
Where source data becomes a working decision-intelligence model.
The stack you already run — ERP, CRM, MES, and the rest.
Enterprise outcomes
The top of the stack is what an executive actually reads. The Decision Canvas puts the risk and the committed action on one surface. The Balanced Scorecard carries every KPI down to the order line, banded across futures, drillable to root cause. Financial Projections translate the decision into the language the board already speaks.
This is the only layer in any enterprise stack that can price the premium you pay to be resilient. A record system reports the past; a planning system projects one future. Neither can show you the cost of uncertainty, because neither decides across the full range of futures.
Decision Hub
The Decision Hub is the runtime. VYAN’s own agents run here — Risk Diagnostics and Resilience Optimization — and so do the agents you bring. It is where alerts surface, where root-cause analysis runs on the live distribution, where decision experiments compete, and where the resulting plans and insights are held as governed artifacts.
Because it is a runtime rather than a closed engine, the Hub is where the platform stays open: a third-party optimizer or heuristic runs on the same data, under the same Decision Policy, alongside VYAN’s own. The runtime Response and Learning behaviour lives here too — events are sensed and answered between cycles, outcomes are measured against what was decided, and drivers recalibrate from what actually happened.
Between planning cycles the world moves. Events are sensed, classified and answered within the bounds of the Decision Policy — continuously, not on a monthly cadence. When a response needs a replan, only the decisions that materially change are touched; the rest stays committed.
Every decision is measured against what actually happened. Outcomes feed back, drivers recalibrate from realised history rather than stale parameters, and the decision space gets richer over time. The system compounds because it learns from its own decisions.
Decision Studio
The Decision Studio is where the decision is defined before it is ever run. Decision Policies carry leadership’s intent. Drivers are calibrated from history into the distributions a resilient decision is defended against. Filters scope the work; risks catalog the supply, demand and capacity shocks to plan for; scenarios capture custom what-ifs; flows orchestrate the autonomous and ad-hoc workflows.
This is the layer that makes a decision authored rather than assumed. Nothing downstream improvises — the engines obey what is stated here, and every recommendation traces back to it.
Workspace
The Workspace is where raw enterprise data becomes a model you can decide on. A Reference Workspace is a ready-to-run, industry-specific decision-intelligence model — productive on day one. VYAN ships its own; partners and domain experts author theirs; both run natively on the platform.
Underneath sit the Dimension Store and the Measure Store — the structured, versioned representation of how your enterprise actually works, fed from the source systems below and read by everything above.
Source systems
The bottom of the stack is the systems you already run. VYAN is a new layer above them, not a replacement for them — connectors exist for every major planning and record system. The data lake stays where it is; the decision layer is what is new.
Bring your stack, or run VYAN standalone. Either way, the layers below keep doing what they do. What changes is what they are allowed to produce: not a single brittle plan, but a decision that already accounted for the futures the plan never saw.