In Hex
You're an analyst or data team exploring a warehouse in a collaborative notebook.
Comparison
nlqdb vs Hex
Pick Hex if you're an analyst or data team that wants a collaborative SQL + Python notebook over your existing warehouse, with AI-written code, charts, and published data apps. Pick nlqdb if you're building a product or agent that needs English-to-SQL over a database it provisions — embeddable, API-first, with every write diff-previewed.
The same goal, two ways.
> monthly active users by signup cohort for the last 6 months
In your HTML
<nlq-data goal="monthly active users by signup cohort for the last 6 months"></nlq-data>A grouped, time-bucketed query nlqdb answers as SQL over the database your app owns — the live data layer your product queries, not a notebook an analyst publishes.
What's different
Four dimensions that decide it
| Dimension | nlqdb | Hex | Note |
|---|---|---|---|
| Owns the database (provisions + migrates) | Hex connects to your existing warehouse; it doesn't provision or own a database your app writes to. | ||
| Natural-language data questions | Both take English — Hex's Magic / Notebook Agent writes SQL & Python in a notebook, nlqdb compiles SQL against a Postgres it owns. | ||
| Embeddable answer element + SDK + API | Hex embeds published dashboards/apps (Enterprise); nlqdb ships `<nlq-data>`, an SDK, and an HTTP API to query a database your product owns. | ||
| MCP server (agent-callable) | Both expose MCP: Hex's Threads answers from a notebook/warehouse in Slack/Claude/Cursor; nlqdb's `nlqdb_query` materialises Postgres on first reference. |
Show 6 more rows
| Dimension | nlqdb | Hex | Note |
|---|---|---|---|
| Charts, dashboards + published data apps | Hex builds charts, dashboards, and interactive published apps; nlqdb returns typed result rows you render in your own UI. | ||
| Python / R notebook cells | Hex is a mixed SQL + Python + R notebook; nlqdb's output contract is SQL plus rows, not a notebook runtime. | ||
| Real-time multi-user collaboration | Hex is Google-Docs-style collaborative editing; nlqdb is a backend data layer, not a shared editing surface. | ||
| Auto-migration via NL ('add a column for tags') | |||
| Destructive-op diff preview before apply | Hex queries and analyses; it doesn't manage your schema. nlqdb previews writes and DDL before applying. | ||
| Connects to many existing warehouses | Hex reads Snowflake/BigQuery/Databricks/Postgres and more; nlqdb provisions and queries its own Postgres rather than connecting to many warehouses. |
shipped · partial · not shipped
When to choose nlqdb
- You're embedding data answers in your product or agent, not exploring in a notebook.
- An AI agent must provision and query its own database, callable over MCP.
- You ship one HTML element or an API, not a notebook a human drives.
- Writes and schema changes should be diff-previewed before they apply.
When to choose Hex
- You're an analyst or data team exploring a warehouse in a collaborative notebook.
- You want SQL + Python + charts in one document, published as an interactive app.
- You connect existing warehouses (Snowflake, BigQuery, Databricks), not provision a new database.
- Real-time multi-user collaboration on the analysis is core to your workflow.
Questions buyers ask
- Can I use Hex and nlqdb together?
- Yes — they serve different stages. Hex is where an analyst or data team explores a warehouse and publishes a report or dashboard; nlqdb is the database your product or agent queries in plain English at runtime. Use Hex for collaborative analysis, nlqdb for the data layer your app ships on.
- Does nlqdb build dashboards and notebooks like Hex?
- No. nlqdb returns typed result rows from SQL it compiles; it doesn't ship a notebook runtime, charts, or published dashboards. If a collaborative SQL + Python workspace and interactive data apps are the goal, Hex is the right shape; nlqdb's contract is the data, which you render in your own UI.
- Is nlqdb embeddable in my product like Hex's embedded analytics?
- Differently. Hex's embedded analytics (Enterprise) embeds Hex apps and dashboards into your product. nlqdb ships `<nlq-data>`, an SDK, and an HTTP API that query a Postgres nlqdb provisions and owns — you embed the answer, and your app owns the write path, not just a read-only dashboard.
- Hex connects to my warehouse — why provision a new database with nlqdb?
- Hex reads your existing Snowflake/BigQuery/Databricks/Postgres for analysis. nlqdb owns the database your app writes to: it provisions Postgres, migrates the schema via English, and diff-previews destructive writes. Connecting-to-read and owning-the-write-path are different jobs.
- Does Hex have an MCP server like nlqdb?
- Yes — Hex's Threads work as an MCP/agent surface in Slack, Claude, Cursor, and Codex, answering from a notebook or warehouse. nlqdb's MCP is database-shaped: `nlqdb_query` materialises a Postgres on first reference, so an agent can provision and query its own database, not just read an analyst's notebook.
Try nlqdb in 30 seconds
No sign-in. The anonymous database lasts 72 hours; adopt it with one click if you keep it.
Start with a goal →