Helix resources
A plain-language guide to the platform.
Understand the Helix architecture, product domains, operating model, and core terminology before starting a deeper technical or commercial conversation.
Helix is best understood as a connected commerce operating layer: ingest and resolve data, analyze what happened, detect what needs attention, investigate the evidence, and coordinate the operational response.
Capabilities connected by shared context.
Data plane
The ingestion, registry, fact, mart, and query layers that turn operational events into consistent analytical context.
Decision plane
Analytics, intelligence, anomaly, recommendation, AI assistance, investigation, and reporting capabilities.
Action plane
Rewards, support, messaging, integrations, scheduling, configuration, and administration workflows.
Control plane
Identity, authorization, consent, audit, encryption, monitoring, reconciliation, and platform governance.
Designed outcomes
What this domain helps a team do.
A shared vocabulary for product and engineering
A clearer path to evaluation
Questions routed to the right Helix specialists
Useful context before a conversation.
01What is an investigation in Helix?
An investigation is a structured, multi-step workspace linked to a trigger such as an anomaly, recommendation, prompt, manual request, or client inquiry alert.
02What is a source instance?
A source instance identifies an upstream QueueBuster environment within Helix’s registry and scope model. It helps preserve origin and access context across merchants and data flows.
03What is a mart?
A mart is a purpose-built analytical dataset produced from governed facts for a specific business question or product experience.
III. Bring us the real question