In Basedash
You already store data across many sources and want governed BI dashboards over it.
Comparison
nlqdb vs Basedash
Pick Basedash if you want governed BI dashboards and daily AI briefings over data you already store across 750+ sources. Pick nlqdb if you want to own the database itself — provision Postgres, ask in English, write and migrate with diff-previews, and embed the answer inline in your product or agent.
The same goal, two ways.
> monthly active customers grouped by plan, last 6 months
In your HTML
<nlq-data goal="monthly active customers grouped by plan, last 6 months"></nlq-data>The dashboard question a team would open Basedash for — nlqdb mints the Postgres and answers the English goal in one element, no BI seat or connector setup first.
What's different
Four dimensions that decide it
| Dimension | nlqdb | Basedash | Note |
|---|---|---|---|
| Owns the database (provisions + migrates) | Basedash connects to data you already store (Postgres, Snowflake, Salesforce, …); provisioning the database is out of scope by design. | ||
| Natural-language → SQL / charts | |||
| Write / edit data via NL (not read-only) | Basedash is read-only analytics over connected data; nlqdb runs NL-driven writes and schema changes. | ||
| Destructive-op diff preview before apply | Basedash has no NL write path to gate; the per-operation diff preview on an NL-triggered write/DDL is unique to nlqdb. |
Show 6 more rows
| Dimension | nlqdb | Basedash | Note |
|---|---|---|---|
| BI dashboards + reusable-metrics semantic layer | Basedash builds governed dashboards with a semantic layer and daily AI briefings; nlqdb returns answers, not dashboards. | ||
| 750+ data-source connectors | Basedash federates 750+ sources; nlqdb is Postgres-first in Phase 1 (ClickHouse on the workload-analyser path). | ||
| MCP server (agent-callable) | Both ship MCP; Basedash connects an AI client to existing data, while nlqdb's `nlqdb_query` materialises Postgres on first reference. | ||
| Embeddable answer in your own product | Basedash embeds finished charts; nlqdb's `<nlq-data>` is a vanilla web component answering an English goal inline in your layout. | ||
| SOC 2 Type II + SSO + audit logs | Basedash carries SOC 2 Type II with SSO / SCIM / audit logs on Enterprise; nlqdb is pre-alpha and carries none yet. | ||
| Free / anonymous tier (try before sign-in) | Basedash is a 14-day trial then $1,000/mo (≤25 seats); nlqdb has anonymous mode and a free tier on the free LLM chain. |
shipped · partial · not shipped
When to choose nlqdb
- You need the database itself — nlqdb provisions Postgres on the first query.
- You write and migrate data in English, with diff-previews before changes apply.
- You want an answer embedded inline in your product, not a BI dashboard.
- An AI agent must provision and query its own database over MCP, end-to-end.
When to choose Basedash
- You already store data across many sources and want governed BI dashboards over it.
- You need a semantic layer, daily AI briefings, and 750+ connectors today.
- SOC 2 Type II, SSO, and audit logs are hard requirements right now.
- Your team wants polished, shareable charts and reports, not a data-layer primitive.
Questions buyers ask
- Is Basedash a database, or does it connect to one I already have?
- Basedash connects to data you already store — 750+ sources from Postgres and Snowflake to Salesforce and Stripe — and builds governed BI dashboards over it. It does not provision or own a database. nlqdb is the database: `nlqdb_query` materialises Postgres on first reference, so there's no existing warehouse to wire up first.
- Can Basedash write or edit my data, or only read it?
- Basedash is read-only analytics — dashboards, reports, and daily AI briefings over connected data, with no NL write or migration path. nlqdb runs natural-language writes and schema changes (e.g. 'add a column for tags'), and every destructive operation is diff-previewed in plain English before it applies.
- How is nlqdb's embedding different from Basedash embedding charts?
- Basedash embeds finished charts and dashboards into your product. nlqdb embeds an answer primitive: the `<nlq-data>` web component takes an English goal and renders the result inline in your own layout, and the same goal is callable from the SDK, API, or an MCP agent. One ships visualizations; the other ships a queryable data layer.
- Is nlqdb cheaper than Basedash for a small team?
- Basedash starts at $1,000/month for up to 25 seats (plus AI usage) after a 14-day trial, with no permanent free tier. nlqdb has an anonymous mode you can try without signing in and a free tier on the free LLM chain. For a small team that mainly needs to query and embed data, nlqdb removes the per-seat BI bill.
- Is nlqdb SOC 2 compliant like Basedash?
- No. Basedash carries SOC 2 Type II with encryption in transit and at rest, plus SSO, SCIM, and audit logs on Enterprise. nlqdb is pre-alpha and holds no certifications yet. If a documented compliance posture is required today, Basedash is the honest pick; nlqdb's compliance roadmap is downstream of GA.
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 →