Customers
Some customers subscribe and are asking real questions the same week. Others need the platform inside their own network, with no external model calls at all. Supporting both is why every part of DataFact can run wherever the data has to stay.
Deployment
The capability set is identical across all four. What changes is who operates it and where the boundary sits — the subscription you can start on today, the rest we plan with you.
Where it is used
Named references are available under NDA on request.
~40,000 staff · on-premise
The problem
Quality and supplier documentation spread across two decades of filings, with performance data in a separate warehouse.
What changed
Supplier performance evaluated against signed terms; variance investigations that used to take days.
Provincial operator · private cloud
The problem
Analyst team acting as a query desk for the same recurring reporting questions across many regional teams.
What changed
Agents published per region with row-level scoping, so each team sees only its own footprint.
Group holding · on-premise
The problem
Regulatory and safety documentation that must stay inside their own network, with no external model calls.
What changed
On-premise deployment with model serving on their own hardware.
Detailed case studies are in preparation. If you would like to speak to a reference customer in your industry, mention it when you get in touch.
We can arrange a conversation with a team operating DataFact at a similar scale and under similar constraints to yours.
SaaS subscription or private deployment · No data migration either way