I’ve been building an open-source way to add chat-with-data to customer-facing products, so end users can ask questions in natural language and get back real answers from your Supabase DB.
Some teams reach for Supabase MCP for this. It’s powerful (and works well for internal use-cases), but is not recommended for customer-facing use. It’s very hard to make consistently safe + reliable: tenant boundaries, sensitive columns, and business definitions tend to live in prompts and drift over time.
Inconvo takes a different approach: the LLM never writes SQL. It chooses from a constrained, typed set of query operations and proposes parameters; then, deterministic code builds + executes the query so your guardrails are enforced, not just suggested.
It’s open source here on Github: https://github.com/inconvoai/inconvo
Would love to hear what people here think, especially if you’ve thought about shipping customer-facing chat-with-data for your Supabase database.
The user is introducing an open-source solution called Inconvo for adding chat-with-data functionality to customer-facing products using Supabase. Unlike Supabase MCP, which is not recommended for customer-facing use, Inconvo avoids text-to-SQL by using a constrained set of query operations. The user seeks feedback from the community, especially from those considering similar implementations.