This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
NLQueries
Plain-English questions to SQL, validated before it runs
NLQueries turns plain-English questions into SQL, checks it against your real schema, runs it read-only and shows the SQL with the answer. It learns from your query history, reads your docs too, and plugs into Claude Desktop or Cursor over MCP. Self-hosted.
Hi Product Hunt 👋 I'm Pankaj, and I built NLQueries.
The problem. Text-to-SQL demos look great until they meet a real database. The model guesses a column that doesn't exist, joins on the wrong key, or writes something that only fails once it's running against production. And the people asking questions can't tell a good query from a bad one.
What NLQueries does differently:
SQL is validated before it runs. Every generated query is parsed and checked against your live schema before it reaches the database, then run read-only with a timeout. Use ask to preview the SQL without touching the database, or query to run it. You always see the exact SQL.
It learns from your real query history. The knowledge base isn't just a schema dump. It's built from the queries your team already runs, so it learns the joins and the naming you actually use.
Databases and documents in one answer. Ingest PDFs, Word, Excel, Notion or Confluence, and ask a question that spans both.
It's a tool, not another chat window. There's a full MCP server, so Claude Desktop, Cursor and other MCP clients can query your database as a native tool, with token authentication and per-tool grants for network clients.
It's self-hosted. Your database credentials stay with you, and you choose the LLM: Anthropic, OpenAI, Amazon Bedrock, DeepSeek, or others through LiteLLM. It connects to PostgreSQL, MySQL, Snowflake, BigQuery, Redshift, SQL Server and Azure SQL, DuckDB and SQLite, plus anything with a SQLAlchemy URL.
On the licence, since someone will ask: Core is under the Business Source License 1.1. The source is public and you can run it in production. The one thing you can't do is sell it to others as a hosted service. Each version converts to Apache 2.0 four years after release, and the whole project on June 4, 2030.
No comment highlights available yet. Please check back later!
About NLQueries on Product Hunt
“Plain-English questions to SQL, validated before it runs”
NLQueries was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #121 on the daily leaderboard. NLQueries turns plain-English questions into SQL, checks it against your real schema, runs it read-only and shows the SQL with the answer. It learns from your query history, reads your docs too, and plugs into Claude Desktop or Cursor over MCP. Self-hosted.
NLQueries was featured in Open Source (69.1k followers), Developer Tools (523.2k followers), Artificial Intelligence (483.9k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 286.6k products, making this a competitive space to launch in.
Who hunted NLQueries?
NLQueries was hunted by Pankaj Goswami. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how NLQueries stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hi Product Hunt 👋 I'm Pankaj, and I built NLQueries.
The problem. Text-to-SQL demos look great until they meet a real database. The model guesses a column that doesn't exist, joins on the wrong key, or writes something that only fails once it's running against production. And the people asking questions can't tell a good query from a bad one.
What NLQueries does differently:
SQL is validated before it runs. Every generated query is parsed and checked against your live schema before it reaches the database, then run read-only with a timeout. Use ask to preview the SQL without touching the database, or query to run it. You always see the exact SQL.
It learns from your real query history. The knowledge base isn't just a schema dump. It's built from the queries your team already runs, so it learns the joins and the naming you actually use.
Databases and documents in one answer. Ingest PDFs, Word, Excel, Notion or Confluence, and ask a question that spans both.
It's a tool, not another chat window. There's a full MCP server, so Claude Desktop, Cursor and other MCP clients can query your database as a native tool, with token authentication and per-tool grants for network clients.
It's self-hosted. Your database credentials stay with you, and you choose the LLM: Anthropic, OpenAI, Amazon Bedrock, DeepSeek, or others through LiteLLM. It connects to PostgreSQL, MySQL, Snowflake, BigQuery, Redshift, SQL Server and Azure SQL, DuckDB and SQLite, plus anything with a SQLAlchemy URL.
On the licence, since someone will ask: Core is under the Business Source License 1.1. The source is public and you can run it in production. The one thing you can't do is sell it to others as a hosted service. Each version converts to Apache 2.0 four years after release, and the whole project on June 4, 2030.
Try it:
Or run the whole stack with Docker. The quickstart is at https://nlqueries.com/docs/getting-started, and the source is at https://github.com/nlqueries/nlqueries.
I'd love to hear where it gets a question wrong. That's the most useful feedback there is. I'm here all day to answer anything.