Skip to content
Product · Data

Answers grounded in your internal documents and operational data

Internal documents connect through the Knowledge Base, operational data through data analysis, and terms unique to your organization through the glossary. Each answer comes with the documents it referenced, the databases it queried, and the SQL it ran, so you can check what the result is based on.

Internal documents → Knowledge Base KB
Operational databases → data analysis SQL
Every answer cites its documents and SQL CITE
DATA
Natural language question → SQL execution → table, chart, and source table

Three challenges in putting internal data to work with AI

Getting to the data takes too long

Business users ask in natural language, and AI generates SQL, queries the database, and returns the results as tables and charts. The SQL behind each query is shown alongside.

Your organization's terms don't make it into answers

Register internal terms like "VIP customer" or "net sales" with their definitions and synonyms in the glossary, and they apply consistently to answers and SQL generation.

HWP files and scanned documents are hard to process consistently

Supports 14+ document formats including HWP and HWPX, and lets you apply the right extraction or OCR engine for each format and document type.

Grounding answers in documents and databases

Knowledge Base

  • Formats: PDF, Word, PowerPoint, Excel, CSV, HWP, HWPX, Markdown, HTML, XML, EPUB, email (EML/MSG)​, TXT, JSON, and 50+ code file types.
  • Per-extension extraction engines: Choose an engine for each extension — for example, Azure Document Intelligence for PDFs and the built-in extractor for Excel. Scanned documents and images are handled with LLM Vision. An extension with no engine assigned is rejected on upload rather than silently falling back to another engine.
  • Search: Hybrid search combining keyword and vector search with reranking, and semantic chunking.
  • Library: Organize the Knowledge Base as a folder tree, and set the search scope and a "when to search this folder" description per folder for agents.
  • Bulk processing: Upload entire folders, duplicate-file detection, automatic replacement of same-named files, and retries for failed files. Processing progress appears in the notification center and stays visible even if you switch screens.

Data analysis — natural language → SQL

  • 8 database engines: PostgreSQL · MySQL / MariaDB · Microsoft SQL Server · Oracle · Snowflake · Databricks · Google BigQuery · Azure Synapse.
  • Connection test: A connection-test button checks table lists before you save. BigQuery uses Google Cloud default credentials with no key file, and Oracle supports read-only accounts and queries across other schemas.
  • Answers: question → SQL written and run → table, chart, summary. Every SQL statement executed and its results are passed into the answer step so filters and aggregation logic are explained precisely.
  • Multiple connected databases: When several databases are attached to an agent, the answer and the SQL-execution card show which database was chosen, why, and what was queried.
  • Question–SQL example memory: Builds up verified question–SQL examples per database to improve accuracy. Only SQL confirmed to support the answer is saved automatically, and admins can also register or edit examples directly.
  • Table relationship inference and ERD: Infers table relationships from foreign keys and column-naming conventions to build a join graph, with an ERD panel showing fact, dimension, and bridge table roles.
  • SQL editor: Write and run SQL directly on screen, and save it to a file.
  • Write-query approval: INSERT, UPDATE, and DELETE require a preview and approval before they take effect, and each database decides whether writes are allowed at all. Every execution, approval, and rejection is recorded in the SQL execution log.
  • AI dashboard: Build a panel in natural language and the SQL is generated and validated; afterward it refreshes using the saved SQL.

Glossary

  • Register internal terms and definitions, and they carry through into agent answers.
  • Preview and bulk-register terms from Excel, CSV, or Markdown files. AI converts different formats into glossary entries, and a standard template file is also available to download.
  • Pulls term candidates from database values for you to review and register.
  • Category management and a history of term changes.

Knowledge Graph

  • Links business terms from the glossary, tables/columns/relationships from your databases, and Knowledge Base documents into a single graph.
  • Extracts entities and relationships from documents and maps terms to column conditions — for example, "VIP customer" → tier = 'VIP'.
  • Connect the Knowledge Graph to an agent and it automatically gains tools for resolving terms, finding related tables, and exploring neighboring nodes.
  • Explore the graph on screen, filtering and searching by node type.

Knowledge Base, data analysis, and glossary screens

Example product screen · Answers grounded in the Knowledge Base 0:10

An internal policy question is answered from source passages, with the document and page cited.

Manage every connected database from one screen. Alongside engine badges, schema extraction, and access permissions, each database builds a memory of verified question–SQL examples that sharpens the SQL behind later answers.
Even databases without foreign keys get their join relationships inferred from naming conventions.

Related integrations

The Knowledge Base and glossary are included from the Standard tier; data analysis and the AI dashboard from the Professional tier; the Knowledge Graph is included in the Enterprise tier. → Pricing · licensing

Related updates

1.5.0 2026-09

Data analysis Only verified question–SQL examples are saved automatically

1.4.0 2026-08

Data analysis Selection rationale for agents with multiple connected databases

1.3.0 2026-07

Knowledge Base Knowledge Base library

All release notes →

See a demo scenario built on your own documents and databases

We set up a demo environment based on your deployment method, integration scope, and governance requirements.