In Outerbase
You already run a production Postgres / MySQL / Snowflake / BigQuery you can't migrate.
Comparison
nlqdb vs Outerbase
Pick Outerbase if you already run a production database and want an AI-assisted admin UI — spreadsheet edits, EZQL natural-language queries, dashboards — sitting on top of it. Pick nlqdb if you want the database itself provisioned, schema evolved via English, and one HTML element rendering answers in your own app.
The same goal, two ways.
> today's failed background jobs grouped by service in the last 24 hours
In your HTML
<nlq-data goal="today's failed background jobs grouped by service in the last 24 hours"></nlq-data>The ops query a backend engineer runs from an internal dashboard — Outerbase renders it through a spreadsheet view on your existing DB; nlqdb mints the DB and answers the English goal in one element.
What's different
Four dimensions that decide it
| Dimension | nlqdb | Outerbase | Note |
|---|---|---|---|
| Owns the database (provisions + migrates) | |||
| Natural-language → SQL | |||
| Auto-migration via NL ('add a column for tags') | Outerbase's editor edits rows + runs queries; schema-evolve via NL is not part of EZQL. | ||
| Destructive-op diff preview before apply | Outerbase's spreadsheet editor confirms row edits inline; the NL-side diff preview is unique to nlqdb. |
Show 7 more rows
| Dimension | nlqdb | Outerbase | Note |
|---|---|---|---|
| MCP server (agent-callable) | Outerbase has no public MCP server today; nlqdb ships `nlqdb_query`, `nlqdb_list_databases`, `nlqdb_describe` — `nlqdb_query` materialises Postgres on first reference. | ||
| HTML embed element (in-product render) | Outerbase ships embeddable charts + an API; nlqdb's `<nlq-data>` is a vanilla web component for arbitrary HTML. | ||
| Spreadsheet-style row editor / admin browse UI | |||
| Dashboards + data catalog UI | |||
| Multi-engine support beyond Postgres | Outerbase: Postgres / MySQL / SQLite / MongoDB / ClickHouse / Snowflake / BigQuery / Redshift / MSSQL. nlqdb: Postgres in Phase 1; ClickHouse on the workload-analyser path. | ||
| HIPAA + SOC 2 Type 2 compliance | Outerbase's Enterprise tier carries both certifications; lower tiers don't surface them. nlqdb is pre-alpha and carries neither. | ||
| Unlimited free-tier natural-language queries | Outerbase's Free tier ships documented per-month usage caps; nlqdb's free chain (Groq → Gemini) is rate-limited per principal, not per question/month. |
shipped · partial · not shipped
When to choose nlqdb
- You want destructive operations and schema changes diff-previewed before they apply, even when an English request triggered them.
- You want to embed the answer inside your own product via one HTML element, not link out to a hosted admin UI.
- You're spinning up a new feature or service that needs its own database — nlqdb provisions Postgres on the first query.
- An AI agent needs to provision its own database via MCP — `nlqdb_query` materialises Postgres on first reference, the on-ramp Outerbase doesn't ship.
When to choose Outerbase
- You already run a production Postgres / MySQL / Snowflake / BigQuery you can't migrate.
- You want a spreadsheet-style editor + dashboards + data catalog UI — admin-tool shape, not a chat box.
- Your engine isn't Postgres today (MySQL, MongoDB, Snowflake, BigQuery, ClickHouse, Redshift, MSSQL) — Outerbase ships across all of them now; nlqdb is Postgres-first (ClickHouse Phase 2).
- HIPAA or SOC 2 Type 2 certification is a hard requirement today — Outerbase's Enterprise tier carries both; nlqdb is pre-alpha and carries neither yet.
Questions buyers ask
- Outerbase was acquired by Cloudflare in 2025 — is nlqdb still relevant?
- Different shape, same infra: both run on Cloudflare Workers, but Outerbase remains the admin-UI-on-your-existing-DB product, while nlqdb owns the database and ships an `<nlq-data>` element + MCP server for in-product render and agent provisioning. The acquisition signals demand for the category; it doesn't collapse Outerbase and nlqdb onto the same answer.
- Can I point Outerbase at an nlqdb database, or nlqdb at an Outerbase-managed DB?
- Not today. nlqdb's API speaks `/v1/ask` (English) and `/v1/run` (raw SQL with allow-list); Outerbase expects a connection string to a database it doesn't own. Bring-your-own-Postgres is on nlqdb's roadmap but isn't shipped — for an existing production DB today, Outerbase is the right shape.
- How does nlqdb's NL→SQL compare to Outerbase's EZQL?
- Both translate English into SQL; the differentiator isn't the translation, it's what surrounds it. nlqdb prompts directly from the live schema fingerprint plus a recent-tables hint and surfaces the compiled SQL under a `Cmd+/` trace toggle. nlqdb also publishes BIRD Mini-Dev + Spider 2.0-lite accuracy to `docs/features/quality-eval/`; Outerbase doesn't publish a single canonical benchmark.
- Does nlqdb support MySQL, Snowflake, or BigQuery like Outerbase does?
- Not today. nlqdb is Postgres-first in Phase 1; ClickHouse lands on the workload-analyser path. If your stack is MySQL / Snowflake / BigQuery / Redshift / MSSQL / MongoDB, Outerbase covers it natively and nlqdb does not.
- Can my AI agent provision an Outerbase-managed DB the way it provisions an nlqdb database?
- Outerbase is admin-UI shaped — it doesn't expose a provisioning primitive an autonomous agent can call. nlqdb's MCP server (`mcp.nlqdb.com`) exposes `nlqdb_query`, `nlqdb_list_databases`, and `nlqdb_describe` — `nlqdb_query` materialises Postgres on first reference (no separate create-DB verb) — so a Claude / Cursor / Cline agent stands up its own data layer end-to-end.
- Is nlqdb HIPAA or SOC 2 compliant like Outerbase?
- No. nlqdb is pre-alpha; neither certification is in place yet. If you're shipping a regulated product today, Outerbase's Enterprise tier (HIPAA + SOC 2 Type 2) 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 →