Product overview
Tessallite sits between business tools and source data.
BI tools, Excel, APIs, and agents ask Tessallite for data. Tessallite checks the published semantic model, confirms access, chooses the right execution path, and returns the same governed answer to every client.
What happens when a tool asks a question
- The Gateway receives the SQL, DAX, XMLA, API, or agent-backed request.
- The Query Router maps fields to approved dimensions, measures, joins, calendars, and glossary terms.
- Security rules, persona restrictions, row filters, and column restrictions are applied before execution.
- Tessallite uses an aggregate or pocket table when it safely matches the query shape.
- If no safe fast path exists, the request runs through the source path and the miss is logged for optimisation.
Why teams use it
Most analytics problems are caused by inconsistent definitions, unclear ownership, slow repeated queries, and tool-specific logic. Tessallite moves the definitions and routing rules into one governed layer so every downstream tool sees the same metric logic.
Who owns it
Data platform teams operate the services. Modellers define the semantic model. Analysts and business users consume the model through Excel, BI tools, applications, or the conversational agent.
Next steps
See the product surfaces and install path.
Product screens
Review the modeller, query routing, endpoints, Excel, and BI workflows with real screenshots.
Local evaluation
Request a licence, download the signed bundle, and follow the install guide.