NLQueries Reviews and Details

Questions & Answers

1. What makes NLQueries unique?

   NLQueries is an open-source, self-hosted Natural Language to SQL (NL2SQL) engine that validates every generated query against the live database schema before it runs. While most text-to-SQL tools act as black-box wrappers around an LLM, NLQueries guarantees deterministic safety, transparency, and context accuracy through five distinct capabilities:
   - Pre-execution AST validation: Generated SQL is parsed and checked column-by-column against your live database schema using sqlglot before execution. Users can preview and validate SQL via nlqueries ask without touching the database, or execute it safely in read-only mode via nlqueries query. - Self-updating YAML knowledge base: Rather than relying solely on static schema introspection, NLQueries learns from actual query history—capturing how teams define business metrics, which tables are trusted, and which joins are valid—storing this context in a human-readable, version-controllable YAML file.
   - Unified database + document querying: A multi-agent orchestrator routes questions across structured SQL databases and unstructured documents (PDF, Word, Excel, Notion, and Confluence) simultaneously, returning one coherent answer with exact SQL and document citations.
   - Native MCP server instead of another chat silo: It ships with a full Model Context Protocol (MCP) interface, allowing developers and analysts to query their data warehouse directly inside Claude Desktop, Cursor, or any MCP-compatible assistant.
   - Sub-50ms semantic caching: Questions with 0.97 or higher cosine similarity to previously validated queries bypass both the LLM and database round-trip, cutting token costs and latency.

2. Why should a person choose NLQueries over its competitors?

   Most competing AI data tools fail in production because they hallucinate column names, use the wrong department's join logic, or require sending sensitive enterprise schemas to a third-party SaaS cloud. You should choose NLQueries over competitors (such as Vanna AI, Defog, Chat2DB, or cloud BI chat add-ons) because:

   • Zero data exfiltration & zero telemetry: NLQueries is 100% self-hosted in your own cloud (AWS, Azure, GCP, or Docker) using your own LLM API keys. Your schemas, queries, and documents never leave your environment, and nlqueries-core sends zero telemetry.
     
   • Auditable, board-ready accuracy: Every answer includes the exact SQL query that produced it alongside source citations. In the Enterprise edition, every action is written to an immutable audit log with table-, column-, and row-level access controls.
     
   • A complete open-source engine (pip install nlqueries-core): Unlike "open-core" competitors that cripple their free tier into a toy demo, NLQueries Core ships the full engine—CLI, Python library, MCP server, 8+ dedicated database connectors, and 5 document connectors—with no account or license key required.
     
   • Coverage observability: Built-in commands like nlqueries kb-stats show exactly which tables and columns are well-documented in your knowledge base and which ones need enrichment before business users query them.

3. How would you describe the primary audience of NLQueries?

   The primary audience spans technical builders who need a programmable, hallucination-free NL2SQL engine and enterprise leaders who require strict data governance:

   • Data Engineers & Data Architects: Teams looking to expose governed, self-serve data access across PostgreSQL, Snowflake, BigQuery, Redshift, DuckDB, or SQL Server without manually writing every ad-hoc SQL report.
     
   • AI Engineers & Application Developers: Builders using nlqueries-core as a Python library (MultiAgentOrchestrator) or MCP server to give AI agents, Cursor, and Claude Desktop safe, read-only access to production databases.
     
   • Analytics Leaders & BI Teams: Analysts who want to bridge the gap between warehouse metrics and business policy documents (Notion, Confluence, PDFs) while maintaining a transparent, editable YAML semantic layer.
     
   • Security-Conscious Enterprise CTOs & CISOs: Organizations in regulated industries that cannot upload proprietary schemas or financial records to third-party SaaS AI tools and require self-hosted deployment with read-only guardrails and audit logs.

4. What's the story behind NLQueries?

   NLQueries was founded by Pankaj Goswami (Founder & Director of Theorence Labs Private Limited), drawing on over two decades of experience building enterprise data platforms, semantic layers, and generative AI systems at organizations like Amazon and Wipro.

   The idea was born from a simple realization dubbed "The second after the SQL": while any modern LLM can generate a SQL query in one second, almost none of the real-world difficulty of enterprise data lives in that second. In a real company, the difficulty lies in the twelve different tables that all plausibly mean "customer," the join that is right for Finance but wrong for Sales, the undocumented varchar column whose creator left years ago, and the fact that when a number lands in a board deck, someone has to defend exactly how it was calculated.

   Existing AI tools skipped this unglamorous reality, producing plausible-looking numbers that could not be verified. Theorence Labs created NLQueries to build the opposite: a self-hosted, deterministic system that learns how a team actually works, validates every query via AST before execution, shows its exact work, and keeps all data strictly inside the customer's own infrastructure.

5. Which are the primary technologies used for building NLQueries?

   NLQueries is built on a modern, modular Python and data engineering stack designed for low latency and strict schema safety:

   • Core Language & Runtime: Python (distributed via PyPI as nlqueries-core with both a first-class CLI and Python SDK).
     
   • SQL Parsing & AST Validation: sqlglot for deterministic SQL parsing, column-by-column schema verification, and dialect transpilation.
     
   • LLM Orchestration & Model Routing: Multi-Agent Orchestrator with LiteLLM integration, supporting Anthropic (Claude), OpenAI, and local/private model providers via bring-your-own-key (BYOK).
     
   • Agent Protocol: Model Context Protocol (MCP) server implementation for native tool-calling in Claude Desktop, Cursor, and custom AI agents.
     
   • Database Drivers & Storage Layer: Dedicated connectors for PostgreSQL, MySQL, Snowflake, BigQuery, Amazon Redshift, SQL Server / Azure SQL, DuckDB, and SQLite, plus SQLAlchemy for Oracle, MariaDB, and custom SQL engines.
     
   • Knowledge Base & Caching: YAML-based self-learning semantic knowledge store paired with a vector Semantic Cache (cosine similarity >= 0.97) and document ingestion pipelines for PDF, DOCX, XLSX, Notion, and Confluence.
     
   • Deployment Infrastructure: Docker / Docker Compose and cloud-native self-hosted deployment templates for AWS, Azure, and GCP

6. Who are some of the biggest customers of NLQueries?

   Self-Hosted & Privacy-First Adoption: Because NLQueries Core (pip install nlqueries-core) requires no account, no license key, and collects zero telemetry, it is adopted organically by independent data engineering teams, fintech and quantitative analysts, and AI software engineers running self-hosted workloads across PostgreSQL, DuckDB, Snowflake, and BigQuery.

   Enterprise Design Partners & Regulated Teams: NLQueries Enterprise serves mid-market and enterprise data, finance, and operations teams across cloud and on-premises environments (AWS, Azure, and GCP) that require strict data residency, RBAC/row-level security, and immutable audit logs without exposing proprietary data to external SaaS vendors.