Contact us

Platform

Company

Contact us

Pricing

Subscribe to it,
or run it yourself

Two routes: a SaaS subscription you can start on directly, or a licence to install the same platform on-premise or in your private cloud. Which fits is decided by where the data has to live and how many teams will use it.

SaaS subscription

Starter

One team proving it on real data

Subscribe and start. Bring your own documents and one schema and evaluate against a defined question set. Nothing to install and no infrastructure to plan.

  • Subscription billing, monthly or annual
  • One workspace, one schema
  • Document and database intake
  • Up to 3 published agents
  • Shared support channel
Try demo

Most common

SaaS subscription

Business

Multiple teams in production

The full platform on a subscription, with the governance layer that makes a wide rollout safe: data roles, row rules, audit and identity integration.

  • Multiple workspaces and teams
  • Data roles with row & table rules
  • Business-identity templates
  • Full question audit trail
  • Embeddable widget and open API
  • Named support contact
Try demo
On-premise & private cloud

Enterprise

Deployed in your own environment

The same platform installed in your network or your private cloud tenancy, under a licence term. Environment, integration and support are scoped per project, so this route starts with a conversation.

  • Your data centre or private cloud tenancy
  • Model serving on your own hardware
  • SSO / LDAP integration
  • Custom retention and residency
  • Dedicated engineering support
  • Roadmap input
Contact us

Questions

What buyers ask first

Subscription or private deployment — which should we pick?
If nothing forbids the data leaving your network, subscribe: you can be asking real questions the same day and there is nothing to operate. Choose on-premise or private cloud when regulation or a security review requires the platform to sit inside your own environment. The feature set is identical, so this is an infrastructure decision rather than a product one.
Can we start on a subscription and move in-house later?
Yes. Because both routes run the same platform, your workspace configuration — analysis model, agents, data roles — comes with you, so the move is an infrastructure exercise rather than a rebuild.
Why is there no price on this page?
Because it would not survive contact with your requirements. On a subscription, volume of documents and number of teams matter more than seat count; on a private deployment, environment and support level dominate. We would rather scope it with you than publish a figure we then renegotiate.
Do we need to move our data?
No. On both routes DataFact connects to the sources you already run. It does not require a copy of your warehouse, and documents can stay in the storage you use today.
Which models does it use?
Model choice is configuration, not architecture. You can point it at a commercial API, or at models served on infrastructure you control.
How long does it take to get going?
On a subscription, intake and parsing of a real document set is usually days rather than weeks. The part that takes real time is agreeing the metric definitions, and that work is worth doing regardless of tooling. A private deployment adds an environment and security review, which we scope with you up front.
What happens to our questions and answers?
They are retained as the audit trail under your retention policy — in your own workspace on a subscription, and entirely within your network on a private deployment.

Get a scoped number question

Tell us where the data lives, roughly how much of it there is, and who needs to ask questions. We will come back with a concrete proposal.

Try demo →See how it works

SaaS subscription or private deployment · No data migration either way