Natural Language SQL vs SQLAI.ai

Natural Language SQL turns plain-English questions about databases into SQL, validates and runs the query, then streams back results. It connects to PostgreSQL and MySQL, including multiple databases of the same type in parallel. Hybrid retrieval combines BM25 and sentence-transformer vectors to select schema context for a question. Users can review and edit generated SQL before execution, while the interface shows progress through query stages. Results can be sorted, paginated at 50 rows per page, downloaded as CSV or JSON, or copied as tab-separated text. SELECT queries receive a default limit, explicit result counts are capped at 1,000 rows, and execution times out after 30 seconds by default. INSERT, UPDATE and DELETE are allowed by default, with warning banners; the project recommends a read-only database user to block writes. Ollama runs locally by default, keeping questions, schema and generated SQL on the user’s machine. OpenAI, Gemini and Groq are optional cloud providers and receive the question, relevant schema portion and SQL context. The project is free under GPL-3.0. Its recommended Docker setup needs Docker 20.10 or later with Compose v2 and about 10 GB of free disk space.

SQLAI.ai is a web and API toolbox for generating and working with SQL and NoSQL queries. Its text-to-SQL generator turns plain-language requests in many languages into queries; other tools optimize, validate, format, explain, and convert them. The SQL optimizer offers index-aware rewrites and explains performance changes. Database rules, schema autosuggest, a VS Code-style editor, side-by-side diff view, and large-schema support provide additional query tools. Its directory lists 28 database engines, including MySQL, PostgreSQL, SQL Server, Oracle PL/SQL, and MongoDB; some support live connections and others schema-only workflows. Users can run natural-language queries against connected databases, and the site recommends read-only connections for improved security. The company says it stores schemas rather than actual database data and encrypts credentials routed through a proxy. The public API uses an access token in a request header; API requests cost 3 credits per query or 5 for very large schemas. Hobby costs $4 a month and includes 50 queries per month; a 7-day trial is listed, but no free plan.