No warehouse project required.
Reports on the records themselves
Dashboards read the same entities the field writes — no ETL pipeline, no morning-after data.
Data Studio underneath
Governed datasets, permissioned access, scheduled delivery — the analytics layer is part of the platform, not beside it.
Sense for the ad-hoc questions
The one-off question doesn’t need a dashboard — ask it in plain language, get a cited answer.
Not a module. The platform.
From record to dashboard — governed the whole way.
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Analytics |
|---|---|
| Role-scoped dashboards and KPI widgets | Native |
| Banded, print-perfect report designer | Native |
| Pivot designer | Native |
| Report wizard | Native |
| Scheduled email subscriptions | Native |
| Row-level security on every report | Native |
| Star-schema datasets | Integrated — Data Studio |
| Managed warehouse refresh | Integrated — Data Studio |
| Archive rules | Integrated — Data Studio |
| Governed embedded BI | Native |
Everything in Analytics & Reporting.
The questions evaluators ask.
Do I need a data warehouse to report on this?
No — the warehouse comes managed. Your operational data reshapes into clean, analysis-ready star-schema datasets that materialize into a managed cloud warehouse, provisioned and refreshed on schedule for you. There are no pipelines to build and no servers to babysit; dashboards, pivots and banded reports all draw from the same datasets, so everyone argues about the decision instead of the numbers.
What is the difference between Analytics and Data Studio?
Analytics is where numbers are consumed: dashboards and KPI widgets, print-perfect banded reports, pivots, scheduled email subscriptions. Data Studio is the modelling layer beneath it: governed data models, dataset building, refresh schedules and archival rules that feed everything above. Define revenue once in the studio and every report downstream means the same thing by it. Explore xMatix Data Studio.
Can reports respect the user's record permissions?
Yes — row-level security lives with the data, not with each report. The same dashboard shows a branch manager their branch and a region head their region, automatically; each user queries the same dataset and sees only their slice. Because the rules travel with the dataset, a new report cannot accidentally widen access.
Can I export or connect BI tools?
Approved dashboards publish into other apps and portals through governed embedded BI — what is shared is allowlisted, so nothing leaks that should not. Scheduled subscriptions deliver any report to the team's inbox on a cadence. For ad-hoc slicing, the pivot designer answers most spreadsheet-export impulses in place: drag dimensions and measures until the answer appears, then save the view and it stays live.
