Skip to main content

Qurify

Let Your Questions
Clarify.

A subscription AX solution that automates office, sales, and other functional work with LLM-based agents, and keeps the know-how gained along the way as company assets.

From ThanoSQL to Qurify

Qurify is the successor product to ThanoSQL, the core technology SmartMind AI has developed since 2018 — a next-generation database platform that applies transformer models to SQL. In 2024, this foundation was extended into an AI engine that connects documents and data to answer with evidence, launching officially as Qurify in June 2025. ThanoSQL's unstructured-data processing and distributed parallel-processing technology remain the technical foundation of Qurify's NL2SQL and hybrid RAG engines today.

At a glance

One-sentence definition

Qurify is a subscription AX solution that automates office, sales, and other functional work with LLM-based agents. An FDE sets it up in about a month; every answer carries its sources, and know-how gained at work is kept as company assets.

Who it is for

Analysts, planners, finance and operations teams, plus IT/AX organizations that run ERP or a data warehouse.

Problem it solves

Without an ERP, daily, weekly, and monthly reports take two to three weeks, the data built for them is not kept, and know-how stays in employees' heads.

Key capabilities

  • ·Natural language to SQL and document retrieval in one question
  • ·Shows the documents and data behind each answer, and flags unverified parts and missing data
  • ·Answers include SQL and source documents; an LLM Judge scores quality
  • ·MCP integration with internal tools; SaaS and on-premise deployment

Environment, integrations, deployment, security

Major RDBMSs (PostgreSQL, Oracle, SQL Server, MySQL), documents (PDF, Excel, Word), on-premise, closed networks, and SaaS. AES-256, RBAC, PII masking.

Limitations

Qurify does not answer from unmapped schemas or documents. Customer source data is not sent to external LLMs in the default setup. Demo figures use fictional scenario data and vary by environment.

Why Qurify

Two to three weeks per report — Qurify makes it one question

Without an ERP, every daily, weekly, and monthly report means meetings and data gathering. The data built for it is not kept, so each new analysis takes the same time again.

Before

  • Two to three weeks per report

    Without an ERP, daily, weekly, and monthly reports take two to three weeks of meetings and data gathering.

  • Data that never accumulates

    The data built for each report is not kept, so every new analysis starts from scratch.

  • Know-how stays in people's heads

    How good work gets done lives with individual employees and leaves when they do.

With Qurify

  • One question, one report

    Figures and documents come together in a single answer, with evidence.

  • Accumulated in the ontology

    Connected data builds up in the ontology, so the next analysis starts on top of it.

  • Know-how becomes a company asset

    Know-how is drawn from everyday conversations into personal assets, and the best ones are rolled out company-wide.

Agents

Several agents working on one ontology

Setup centers on the Ontology Agent and the work agents your FDE configures; operation centers on our own Assetization Agent. Tacit knowledge that lived only in employees' heads builds up as company assets.

Setup

Ontology Agent

Pulls structured and unstructured data — RDBs, ERP, OneDrive — and chat data into your company's ontology, then handles Q&A and data analysis across your company's data.

Setup · Operation

Work Agents

Your FDE takes the work and business requirements you want covered and configures multiple agents for office, sales, and other functions. Teams use them by chatting.

Operation

Assetization Agent

Developed in-house by SmartMind AI. As each user works through conversations under the permission model, their know-how is turned into assets automatically.

Coming soon

Data Science Agent

Runs advanced AI modeling on the data built up in the ontology.

How the Assetization Agent builds up know-how

  1. 01

    Work by conversation

    Each user works with agents through conversation, within the permission model.

  2. 02

    Personal assets

    Know-how in those conversations becomes personal assets automatically.

  3. 03

    Self Improvement

    The assetization algorithm keeps refining assets as they are used.

  4. 04

    Promoted to global

    The best personal assets are promoted to company-wide assets.

  5. 05

    Rolled out company-wide

    Other employees use the promoted assets the same way.

Deployment

Two ways to adopt: subscription (SaaS) or on-premise

Companies with strict security requirements, such as finance and the public sector, install it on-premise.

SaaS

Subscription

Use Qurify on a monthly subscription after setup.

  • After about a month of setup, you move to a monthly subscription
  • Base usage is set by company size; only usage above it is added
  • Your data stays where it is; Qurify only connects to it

On-Premise

On-premise

Built for companies with strict network separation and security reviews, such as finance and the public sector.

  • Installed on your own servers or inside a closed network with no external connection
  • If external AI APIs are not allowed, Qurify runs on models hosted on your in-house GPU servers
  • Pricing and base usage are explained in consultation after we understand your installation environment

Your FDE sets up both options in the same order. FDEs are not stationed on site; they keep building agents for the work you want covered.

🔗

Connect scattered materials

Documents, email, spreadsheets, PDFs, and business databases stay where they are and get connected. One question searches them together, without moving the data.

🧩

Answers with evidence

Every answer shows which document passage and which data it relied on, so staff can open the source and check it themselves.

🎯

Clear verification scope

It separates what the data confirms from what it cannot, and tells you which data is missing for verification.

Key Features

A data-friendly experience,built into Qurify

Explore Qurify's key features

Database Compatibility

See data from many systems on one screen

MCP Support

Connect and extend MCP (Model Context Protocol) servers yourself for high-precision analysis tailored to your business context

Personal Customization

Set up an environment that fits you through prompt input and managing examples and descriptions

Database Relationship View

See database relationships as an ERD (Entity Relationship Diagram) and pick the data to reference in your conversation instantly

Work examples

The first screen starts fromthe questions teams keep asking

Example questions by industry, drawn from customer work. Customer names and figures are published only with approval.

Repetitive customer list work, now down to one question

Finds behavior patterns in customer data to select marketing targets, keeping the selection criteria and query evidence on record.

Finance in detail

Find customer IDs for customers whose home address includes 'the region' and who haven't used any 'hypermarket' merchant in the last 2 months.

Finance

How it answers

A question becomes an answer in three steps

Scattered material is connected, tied to the words your teams use, and every answer carries its evidence. That ontology — structured and unstructured held in one structure — is what Qurify is built on.

  1. 01

    Data connection

    Business databases and documents, email, spreadsheets and PDFs are connected where they already live. Structured sources such as PostgreSQL, Snowflake and Databricks sit alongside unstructured material.

    Connectors

  2. 02

    Ontology mapping

    Tables, columns and document clauses are tied to the words your teams actually use, so a question phrased with a department name or a statutory clause still lands on the right data.

    Business terms aligned

  3. 03

    Answer and verification

    NL2SQL and hybrid RAG produce the answer, with the query and document clause it came from attached as evidence. Quality is checked continuously against an answer set your experts reviewed.

    Evidence attached

The language model is chosen to fit your environment

On closed networks with no external connection, a language model is installed inside your own servers and answers are produced there. Where network separation is not required, commercial models are used directly. Either way, the data connection and evidence verification structure stays the same.

This describes only the logical flow we can share publicly. Actual infrastructure, network structure and security controls are covered in a separate document after consultation.

TAG + RAG Architecture

How evidence gets attached to an answer

How Qurify combines figure lookups and document search in a single answer

Structured data (databases)

NL2SQL Engine

Automatically converts natural language questions into SQL and queries your databases directly. A data connection structure linking tables to business terms lets it generate JOIN and aggregation queries. Every generated SQL statement is shown transparently so users can verify results.

Unstructured data (documents)

Hybrid RAG Engine

Combines vector search, full-text search, and graph search to find the best answers in your documents. Because it performs keyword matching and semantic search together, it handles everything from technical documents full of jargon to general reports — and every answer cites its exact source passages.

Supported databases — PostgreSQL · MySQL · MariaDB · MSSQL · Databricks · Snowflake · Amazon Redshift

🧠

Documents and data in one answer

Database queries (TAG) and document search (RAG) work together, combining figures and document context into a single answer.

⚡

Maximum Maintenance Efficiency

Zero-Tuning learns metadata and turns it into templates, so the model does not need to be fine-tuned again every time the data changes.

🛡️

Verified vs. unverified, shown separately

The data behind each answer is shown alongside it, and parts that cannot be confirmed for lack of data are flagged. Staff make the final call with the evidence in front of them.

Security & Compliance

Enterprise-Grade Security

Security architecture that meets the compliance requirements of regulated industries — finance, public sector, healthcare — comes standard.

On-Premise Deployment

Installs on your own servers or private cloud, supporting closed-network operation where data never leaves your premises. Meets compliance requirements for regulated industries such as finance, public sector, and healthcare.

AES-256 Encryption

Both data at rest and data in transit are encrypted with the AES-256 standard. This applies to all sensitive information, including database connection details, user credentials, and search indexes.

RBAC Access Control

Fine-grained control of data access by role (admin, editor, viewer) and by collection. SSO/LDAP integration lets you mirror the organizational structure of your existing HR systems.

PII Masking (via MCP)

Automatically detects personally identifiable information (national ID numbers, phone numbers, emails, etc.) and masks it in AI answers. Masking policies are managed centrally through MCP, with permission-based control over access to original values.

Audit Trail

Every user query, AI response, and data access event is logged with timestamps. Use it for internal audits, compliance reporting, and anomaly detection, with log retention configurable to your policies.

Frequently Asked Questions

Q.How is Qurify different from BI tools like Tableau or Power BI?

BI tools like Tableau and Power BI are optimized for visualizing predefined metrics on dashboards designed in advance. Qurify, by contrast, lets you query and analyze data instantly with natural language — no upfront design required. When a new question arises that isn't on any dashboard, business users find the answer themselves instead of filing a request with IT. Qurify also searches unstructured data (documents, manuals, reports) alongside structured databases, delivering analysis that combines the numbers with their context. It complements rather than replaces BI, covering the ad-hoc analysis and document-driven insights that BI tools can't reach.

Q.How is Qurify different from the AI features in our ERP?

Many ERP products now ship with AI features, but most can only answer questions about the data on the currently open screen. For example, to trace why operating profit increased while viewing the income statement, you'd have to manually open the revenue-by-customer screen, margin-by-product screen, and journal detail screens one by one. Qurify connects data across tables and screens, along with related documents, by business terms, so a single natural language question performs cross-analysis and drill-down. It doesn't replace your ERP — it adds an intelligence layer on top, so all core ERP functions stay exactly as they are.

Q.Is Qurify embedded in the ERP, or is it a separate system?

Today, Qurify is delivered as an independent web interface separate from your ERP. It connects to the ERP database to query data but isn't embedded inside ERP screens. This is a deliberate design: as an independent system it isn't locked to any particular ERP, and it can connect multiple systems simultaneously (ERP + CRM + document storage) for cross-analysis. Based on PoCs and production experience, we are also exploring embedding Qurify inside ERP screens, with the ultimate goal of bringing natural language analysis into whatever environment users know best.

Q.How does it proceed?

Inquiry, then understanding the work and the data, then about a month of setup, then operation. You choose between subscription (SaaS) and on-premise. Tell us one task you want solved and where the data lives and we reply within 2 business days. We learn the questions your teams keep asking, where the data lives, and your closed-network and security requirements, then set up. After setup you run it as a subscription or on-premise, and your FDE keeps adding agents for the work you want covered. Deliverables and criteria for each stage are agreed before we start.

Q.Which databases are supported?

Qurify's NL2SQL engine supports major relational databases including PostgreSQL, MySQL, MariaDB, and MSSQL, as well as cloud data warehouses such as Databricks, Snowflake, and Amazon Redshift. The hybrid RAG engine handles diverse document formats including PDF, Word, Excel, PowerPoint, and HWP, ingesting data via file upload or storage integration. Supported databases and formats are continuously expanding, and specialized data sources can be connected through custom MCP connectors.

Q.What happens when the AI gives a wrong answer?

Qurify has a multi-layered system for preventing and correcting errors. First, every answer includes its sources (original document location or the SQL query), so users can verify results directly. Second, the LLM Judge evaluation system scores each answer's accuracy, evidence fidelity, and completeness in real time — low-confidence answers are flagged with a warning and administrators are notified. Third, user feedback (thumbs up/down) continuously improves the data connection structure and prompts. Fourth, an admin dashboard tracks accuracy trends by query and analyzes recurring error patterns for proactive fixes. This closed-loop structure means answer quality improves the more the system is used.

Q.Where does the data live?

On your servers or in your cloud, where it already is. We connect to your ERP, business databases, and document stores without moving the data to us. We also build and operate on closed networks with no external connection; one system runs inside a government office building today. Where security policy restricts external API calls, we run an open-source LLM on your own GPU servers.

Q.How is security guaranteed?

Qurify provides enterprise-grade security. All data is encrypted with AES-256, both at rest and in transit. Role-based access control (RBAC) finely regulates which collections and data ranges each user, department, or rank can access. Personally identifiable information (PII) is automatically detected and masked before AI answers are generated, with masking policies managed centrally via MCP. All queries, responses, and data access are recorded in an audit trail for internal audits and compliance reporting. SSO/LDAP integration applies your existing authentication as-is, and on-premise deployment supports fully closed-network operation.

Q.Can it integrate with our internal systems (ERP, CRM, groupware)?

Yes. Qurify's MCP (Model Context Protocol) based architecture integrates with a wide range of internal systems in a standardized way — major ERP/CRM platforms like SAP, Oracle ERP, and Salesforce, plus groupware, internal wikis, and file servers. Data sources are added simply by configuring an MCP connector, no custom API development needed, minimizing integration time and cost. REST APIs and webhooks are also supported for flexible integration with systems that don't support MCP. We design the integration scope and approach around your environment during consultation.

Q.Does Qurify connect data without moving it into one place?

Yes. Qurify connects to your databases where they are and queries the data it needs at question time. Documents such as PDF, HWP, Word, and Excel are collected by upload or storage integration and then searched. Each answer shows the document location and SQL behind it, and separates what the data confirms from what it does not, including which data is missing for verification. Rather than connecting all company data at once, we start with core business data and expand in stages, verifying with your team along the way.

Q.Does Qurify only query data, or can it support business decisions?

At Qurify's center are evidence-based answers and their verification, and it can be extended to support decisions within business procedures. It works in four steps: Interpret → Verify → Process → Approve. AI reads and organizes unstructured inputs such as emails and PDFs; checks like registered vendor or contract price match run against connected data, with unconfirmed items flagged. Journal entries and notifications go through workflows the customer defines, and high-risk items above a threshold stop at a human approval gate (HITL, Human-in-the-Loop). AI organizes the evidence to support the decision; staff make the final call.

Related pages

AX that starts with your own data.Let's decide together where to start

About a month of setup, then run it as a subscription or on-premise.