Native or cross-platform? Three questions decide it
Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through.
Analytics and BI turn data into numbers your teams agree on: we give every metric one definition, an owner and tests that run with every refresh.
Analytics and BI turn data into numbers your teams agree on: we give every metric one definition, an owner and tests that run with every refresh, and build the reports and dashboards your teams read.
"Reports nobody trusts" is one of the needs on our Services page, and it leads to Data: one set of pipelines and definitions behind every report. One definition and one owner for every metric, and tests that run with every refresh, before anyone reads a number.
Its definition, its owner, its source, its refresh and its tests. Here is the format, on an illustration (not a client's figures): weekly active customers, customers with at least one order in the week, each counted once.
Part | Example |
|---|---|
Owner | Finance |
Source | fct_orders |
Refresh | Daily, before the working day |
Tests | Not empty, one row per week |
Data governance decides who can see which data, where it is kept and for how long. Access is granted by role, kept to what each role needs, and every access is logged:
Personal data is masked where it is not needed, and retention and deletion run on a schedule.
In the region you choose. Your data and its backups stay in that region.
It is versioned with the model. ML data is the data your models learn from and are tested on. We label datasets for the model's task, redact personal data before labelling, and version each dataset with the model it trains, so any result can be traced back to its data.
Every metric and every dataset comes with its definition. You keep:
We never train models on your data without your opt-in. Your data stays isolated from other clients. How we handle it is on Trust, and our data processing agreement is public.
What you keep is drawn on our Data page, with who sees what beside it. Tell us your use case and timeline. We reply within one business day.
Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through.
A dedicated team fits a long roadmap, team extension a team you already run, and a fixed-scope project a clear scope, a fixed budget and a date to meet.
Migration moves your systems off your own servers to the cloud you choose, in planned waves, each workload with a rollback point.