Product · Architecture
Follow the path from question to query. Verify every deployment boundary.
This page separates the stable product path from the infrastructure choices that must be confirmed for your environment. A useful technical evaluation should make both visible.
Stable product path
Six responsibilities from understanding to answer evidence.
The stages describe what to inspect. They do not claim that every deployment uses the same infrastructure or credential mode.
01
Understand
Identify the question and the context it needs.
Spotonix identifies the analytical task, business terms, entities, time language, and context required to make the request explicit.
02
Interpret
Represent the intended analysis.
Spotonix selects or assembles business concepts, calculations, scope, filters, and grain into a visible analytical plan.
03
Clarify
Pause when missing meaning changes the path.
When a material company term cannot be grounded, the workflow can ask a person rather than silently choosing a definition.
04
Generate
Use the configured model path.
The question and analytical plan inform generation through a configured Claude, Gemini, or OpenAI/Codex path for the engagement.
05
Check
Compare material bindings to the plan.
Semantic checks inspect whether selected query bindings carry the material concepts represented in the plan.
06
Execute & expose
Use the configured connection and show the basis.
Execution uses the selected warehouse path. The answer experience can expose logic or SQL, sources, and supporting result artifacts.
Deployment diligence
Customer-VPC deployment.
Six facts to document for your environment.
Hosting is in the customer VPC. The account, region, identity, network, retention, provider, and evidence details still belong in a dated, environment-specific record.
Hosting location
LiveSpotonix is deployed in the customer VPC. Document the customer account, region, runtime, storage, logs, retained artifacts, and support path for that deployment.
Warehouse identity
EngagementConfirm the adapter, network route, credential owner, permitted data slice, and whether the connection uses a service or delegated identity.
Model provider
EngagementRecord the provider, model, endpoint, key owner, region, provider terms, and data included in each request.
Network boundary
EngagementMap ingress, egress, private connectivity, allowlists, DNS, and any customer-managed routing requirements.
Retention & deletion
EngagementName what is retained, for how long, where backups exist, and how deletion is initiated and evidenced.
Audit evidence
EngagementIdentify the events and artifacts the evaluator needs to reconstruct an analytical run and its human interventions.
Do not infer
Architecture is clearest when responsibility is named.
Product behavior
Visible interpretation is stable; exact outputs are not promised identical.
Evaluate the plan, clarification behavior, generated logic, sources, and artifacts. Do not infer a deterministic plan-to-query compiler.
Deployment choice
Customer-VPC hosting still needs an exact topology.
The deployment lives in the customer VPC; credentials, identity, region, network routing, retained artifacts, and support access are documented for that environment.
Control ownership
The customer remains responsible for source permissions.
Spotonix uses the configured access path; it does not create warehouse authorization or substitute for source-system access controls.
Continue the technical path
Inspect the mechanism, inputs, and security boundary.
Interpretation
Intent Algebra
See how the analytical plan represents selected meaning before execution.
Inputs
Integrations
Review supported formats, onboarding mappings, model paths, and warehouse connectivity.
Controls
Security
Work through identity, data flow, provider, retention, deletion, and assurance questions.
Evaluate directly
Turn the reference path into your deployment checklist.
Bring a representative data slice, the intended model path, identity requirements, network constraints, and the artifacts your security team needs to inspect.
Book DemoSee how it works