Documentation
Start with the product behavior. Keep the boundary beside it.
This documentation is for technical evaluators who need to understand what Spotonix represents, what can be inspected, how the system connects, and which deployment decisions remain environment-specific.
Choose an evaluator question
Four places to begin the technical review.
Each route owns a distinct question. Together they form the product and deployment evaluation path.
Product flow
What happens from question to answer?
Follow clarification, interpretation, plan inspection, execution, answer evidence, and workspace context through one workflow.
Interpretation
How is business meaning represented?
Inspect selected definitions, calculations, scope, filters, grain, ambiguity, and concept origins in the analytical plan.
Architecture
What runs where, with which identity?
Separate the stable product path from hosting, model, warehouse, credential, network, and retention decisions.
Security
Which controls and evidence must be confirmed?
Work through data flow, provider, identity, permissions, encryption, retention, deletion, and assurance questions.
Core vocabulary
Six concepts used across the product.
The vocabulary distinguishes company meaning, analytical structure, interpretation, and evidence instead of collapsing everything into “the AI answer.”
Context Graph
The explicit company, analytical, and data-model context available during interpretation.
Segment
The population the analysis is about: customers, accounts, stores, products, events, or another selected cohort.
Calculation
A measured quantity or comparison such as revenue, rate, growth, share, change, or benchmark.
Analysis pattern
A reusable analytical shape that combines concepts, calculations, comparisons, and scope for a recurring question.
Intent Algebra
The mechanism that represents selected meaning and material ambiguity as a visible analytical plan.
Answer evidence
The generated logic or SQL when present, sources, concept origins, and supporting artifacts available beside the result.
Current documentation boundary
What this site does not ask you to infer.
An honest technical reference names missing operational detail instead of filling it with generic product language.
API & SDK
No public versioned reference is published here yet.
This site documents product concepts and evaluation boundaries. It does not invent endpoints, request schemas, client libraries, or release versions.
Power BI
Model structure and DAX feed Intent Algebra.
Spotonix ingests Power BI structure and DAX measure semantics into the interpretation path. Calculated objects, operational BI responsibilities, and warehouse execution are mapped during onboarding.
Deployment
Reference architecture is not a universal topology.
Hosting, model credentials, warehouse identity, network routes, retention, and deletion are confirmed for the selected engagement.
Assurance
Certifications are claimed only when held.
Current security specifics and assurance status live on the Security page and the linked Trust Center.
Evaluation checklist
Bring the environment, the workflow, and the reviewer.
Choose representative business questions and reviewers.
Name the exact context inputs and connector boundaries.
Map the model, warehouse, identity, and network paths.
Define the interpretation and evidence artifacts reviewers need.
Record failure, correction, deletion, and escalation requirements.
Evaluate the current path and Spotonix against the same rubric.
Evaluate directly
Turn the documentation into a bounded evaluation.
Use your representative questions, inputs, identities, network constraints, and review requirements to test what the product does in the intended environment.
Book DemoSee how it works