Should I build on a text-to-SQL API or use iDBQuery?

A text-to-SQL API does one step: it converts a question into a SQL statement. That leaves everything else to you — running the query safely, joining across sources, handling errors, adding citations, building the interface, and governing access. iDBQuery ships all of that as a product.

• Execution included. iDBQuery runs the generated SQL against a live model of your sources and returns the actual answer, not a string to execute yourself.
• Safety and read-only guards. Query execution is sandboxed and read-only by design, so you're not building your own protections against destructive or unsafe queries.
• Citations built in. Every figure traces to its source row automatically — a feature you'd otherwise have to engineer on top of a raw API.
• One model across sources. Databases, spreadsheets, PDFs and APIs are unified, so questions can span systems rather than hitting one schema.
• Deploy anywhere. Cloud, VPC, air-gapped, Desktop or Embedded SDK — including the SDK if you *do* want to embed answering into your own app.

Build directly on a text-to-SQL API if you need low-level control and have engineers to construct and maintain the surrounding system. Choose iDBQuery when you want reliable, cited, cross-source answers for a team today — and note the Embedded SDK covers the case where you want to build a data-answering feature into your product without reinventing the engine.