Cross-source analytics across CRM, ERP and warehouses
"Which large open opportunities have overdue invoices?" is an ordinary question and it lives in no single system.
A question becomes a decision
Which open deals belong to customers with overdue invoices?
- 01
Connect
CRM opportunities + ERP invoices
- 02
Resolve meaning
Account relationship (certified, where required)
- 03
Review the answer
A cross-source result that lists both sources, or a refusal naming the missing link where a certified one is required.
Illustrative workflow. Results depend on configured sources, definitions, and permissions.
Nexatron can federate queries across connected sources using an embedded DuckDB engine, so a question spanning a CRM and an ERP can be answered without first consolidating both into a warehouse. Federation is on by default for new workspaces, and a workspace admin can turn it off. By default, a cross-source answer does not need a certified entity link between the sources. A workspace admin can require one, and the platform then declines a question whose sources have no certified link, or whose link could multiply rows at the requested grain, and names what is absent. Where federation cannot show that a merged result is correct, it declines rather than return a plausible number.
What it does
- Warehouses and business applications, togetherNine warehouse connectors sit alongside a business-application layer (Salesforce, NetSuite, Oracle Fusion, QuickBooks and others), so the CRM and the ERP are queryable sources rather than pipelines waiting to be built.
- No migration as a preconditionFederation runs through an embedded DuckDB engine at query time. The consolidation project may still be the right long-term call; it stops being the thing that blocks the first answer.
- Per-user authorization at the sourceFor applications with their own permission models, connections can be authorized per user, so the source system's own rules still apply rather than being flattened by a shared service account.
- Currency and calendar stay separate until told otherwiseAmounts in different currencies are reported separately rather than summed into one unlabelled total that looks authoritative and means nothing.
What it deliberately won’t do
Each of these is a case where returning something would have been easy and wrong, so the product is built not to.
- A certified key, when you require oneMatching customers by company name is a guess, and a guess that is usually right is more dangerous than one that is obviously wrong. Cross-source joins do not require an approved key by default. Once a workspace admin requires one, a cross-source question with no approved key between its sources is declined.
- Grain safety is checked against the certified linkWith certified links required, where a link could multiply rows at the requested aggregation, the platform stops rather than return an inflated total. It will suggest a record-level reconciliation instead.
Test the claim, don’t take it
Ask it something you already know the answer to, then ask it something your data cannot answer. Those two questions tell you more than a feature list.