Inconvo is live · free · last verified 5 Nov 2026 · viability monitor
Inconvo
An open-source toolkit for building chat-with-data agents that query your production database in plain language, now preserved as the Inconvo codebase after
Treat Inconvo as a reference implementation, not a maintained dependency. The semantic layer, pre-execution query validation, and row-level security are the patterns every safe multi-tenant data agent needs, and the docs walk through them with a real CLI (npx inconvo@latest dev), Node.js SDK, and MCP server deployment under OAuth. But the 2026-07-08 announcement that Inconvo is joining Attio ended active development of the standalone service: no vendor release cadence, no security patches, and no support commitment. Fork it and read it if you're building your own agent; if you need something maintained, look at TextQL or Vanna instead.
Verdict generatedVerified 9d ago · liveness 69/100 · cite: rightaichoice.com/tools/inconvo
- Developers wanting a reference implementation of a safe, multi-tenant chat-with-data agent
- SaaS teams with a maintainer who can fork and self-host natural language querying
- Engineers evaluating semantic-layer and query-validation patterns before building their own
- Teams that need row-level security and tenant scoping in an open-source data agent
- Non-technical users who need a no-code setup or managed hosting
- Production deployments without someone owning the forked codebase
- Buyers looking for an actively developed product with a roadmap and support contract
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Inconvo if you need a maintained product with a vendor support contract and a release cadence — since the July 2026 Attio acquisition the standalone service is no longer actively developed, so you would have to fork and own the code.
There is no licence fee for the open-source codebase, but someone on your team has to own the forked repository, which is real engineering time against a paid product's maintenance contract.
Inconvo's open-source codebase is free to fork and self-host, which makes it cheaper than commercial chat-with-data platforms on licence cost alone — but you pay for it in maintainer time. Compare it against maintained alternatives such as TextQL or Vanna when the ongoing engineering hours matter more than the licence fee.
In short
Inconvo — An open-source toolkit for building chat-with-data agents that query your production database in plain language, now preserved as the Inconvo codebase after. Best for Developers wanting a reference implementation of a safe, multi-tenant chat-with-data agent, SaaS teams with a maintainer who can fork and self-host natural language querying, Engineers evaluating semantic-layer and query-validation patterns before building their own. Free to use.
What is Inconvo?
Inconvo — An open-source toolkit for building chat-with-data agents that query your production database in plain language, now preserved as the Inconvo codebase after. Best for Developers wanting a reference implementation of a safe, multi-tenant chat-with-data agent, SaaS teams with a maintainer who can fork and self-host natural language querying, Engineers evaluating semantic-layer and query-validation patterns before building their own. Free to use.
Inconvo is an open-source toolkit for building data agents that answer questions by querying your production database in plain language, rather than letting a model write freehand SQL. Instead of trusting the model, Inconvo routes each request through a semantic layer where you define computed columns, table prompts, and agent rules, then validates every query before it executes. Multi-tenancy with tenant scoping and row-level security keeps one customer's rows away from another's, and user-context configuration scopes answers to the individual asking. The kit ships conversation state for multi-turn follow-ups, response streaming (response.created, response.progress, response.completed), agent traces and observability, usage analytics on messages and schema introspection, and a feedback API you can create and update conversations against. A CLI (npx inconvo@latest dev) and a Node.js SDK cover local development, with integration paths through Assistant-UI, the Vercel AI SDK, and MCP servers with OAuth. Database coverage spans PostgreSQL, MySQL, Microsoft SQL Server, Amazon Redshift (beta), BigQuery, and Supabase. The context that matters if you're evaluating it today: Inconvo announced on 2026-07-08 that it is joining Attio, the agentic CRM, and the standalone service is no longer actively developed. The open-source codebase remains available to fork and self-host, but adopting it now means owning the code.
Key features
- Open-source codebase on GitHub for self-hosting and forking
- Semantic layer with computed columns, table prompts, and agent rules
- Query validation before execution to block unsafe or invalid queries
- Multi-tenancy with tenant scoping and row-level security
- User context configuration for per-user data scoping
- Conversation state management for multi-turn interactions
- Response streaming (response.created, response.progress, response.completed)
- Agent traces and observability dashboard
- Usage analytics on messages and schema introspection
- Conversation feedback API (create and update feedback)
- MCP server deployment with OAuth support and tenant creation/deletion
- Integrations with Assistant-UI and the Vercel AI SDK
- Dataset file upload, list, and delete endpoints
- Database connectivity: PostgreSQL, MySQL, Microsoft SQL Server, Amazon Redshift (beta), BigQuery, Supabase
- CLI (npx inconvo@latest dev) and Node.js SDK for local development and embedding
Behind the verdict
Inconvo solves a real problem: the docs are blunt that data agents generating unsafe or invalid queries, managing permissions across evolving systems, and offering limited production visibility are the recurring failures, and those failures don't disappear just because the codebase is open. Where Inconvo is genuinely useful is the architecture. The semantic layer — computed columns, table prompts, agent rules — is the part most teams get wrong, because they hand a raw schema to a model and hope. Here every query is validated before execution, multi-tenancy is enforced with tenant scoping and row-level security rather than a WHERE clause someone forgot, and user-context configuration scopes results per person. The operational surface is broader than you'd expect for a toolkit: conversation state for follow-ups, three streaming events (response.created, response.progress, response.completed), agent traces, message and schema-introspection analytics, and create/update feedback endpoints. Development is covered by a CLI and a Node.js SDK, and the MCP server path lets an AI assistant query your warehouse under OAuth. Database coverage is PostgreSQL, MySQL, Microsoft SQL Server, Amazon Redshift (beta), BigQuery, and Supabase. The weaknesses are structural, not technical. The 2026-07-08 Attio announcement means the standalone service is no longer actively developed, so the release cadence, security patches, and support commitment are yours now. Amazon Redshift support is marked beta. There is no documented visual builder — setup runs through the CLI and SDK, so a non-developer cannot stand this up. And the quality of the answers you get depends almost entirely on how well you configure the semantic layer for your own schema; the toolkit does not do that thinking for you. Where it fits: engineers who want a working reference for semantic-layer and query-validation patterns before building their own, and SaaS teams with a maintainer willing to fork and self-host. Where it doesn't: production deployments with no one owning the fork, or buyers who need a roadmap and a support contract.
Limitations
- Inconvo announced on 2026-07-08 that it is joining Attio, and the standalone platform is no longer actively developed, though the open-source codebase remains available to fork and self-host.
- That means there is no ongoing vendor release cadence behind the standalone product, so security patches and upgrades become your responsibility.
- Building and maintaining data agents is genuinely hard engineering: the docs are explicit that agents generating unsafe or invalid queries, managing permissions across evolving systems, fragile integrations as schemas change, and limited production visibility are the recurring problems Inconvo was built to handle, and those problems do not disappear just because you own the code.
- Amazon Redshift support is marked beta.
- Getting trustworthy answers depends on how well you configure the semantic layer, computed columns, and rules for your own schema.
- There is no documented visual builder for non-developers; setup runs through the CLI and SDK.
as of 2026-10-11
Researching Inconvo? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Inconvo still active?
Inconvo is live · free · last verified 5 Nov 2026 · viability monitor.
Viability score
How well maintained and how widely used is Inconvo? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What's new in Inconvo
Checked 6 days agoAcross the latest 1 update: 1 news mention.
What do users say about Inconvo?
What people actually say about Inconvo — is it worth it?
Our community sentiment research written Aug 16, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about Inconvo — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 5 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Inconvo 13 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed limitations, hidden costs, features, description, use cases, who should skip it, setup time, pricing fit, switching out, switching in, our verdict, summary
- — changed pricing tiers, description, our verdict, features, who should skip it
- — changed pricing tiers
- — changed who should skip it, summary, features, hidden costs, our verdict, limitations, description, switching in, setup time, pricing fit, switching out, use cases, who it suits
- — changed domain expiry
- — changed summary, description, SSL certificate
Showing the 6 most recent of 13 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Inconvo cost in 2026?
Inconvo: Free to use. Pricing last verified 5 Nov 2026.
Plans compared
Every published Inconvo tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Open source | Free | — | Developers and SaaS teams with a maintainer who can fork, self-host, and own the codebase, since there is no vendor support or maintenance commitment behind it.Adds: Starting tier: the full Inconvo codebase at $0, including the semantic layer, query validation, multi-tenancy, CLI, Node.js SDK, and MCP server deployment. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Inconvo's pricing actually pencils out — and where peers do it cheaper.
Inconvo's open-source codebase is free to fork and self-host, which makes it cheaper than commercial chat-with-data platforms on licence cost alone — but you pay for it in maintainer time. Compare it against maintained alternatives such as TextQL or Vanna when the ongoing engineering hours matter more than the licence fee.
Has Inconvo's pricing changed?
No plan price for Inconvo has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Inconvo?
Pick Inconvo if you are Developers wanting a reference implementation of a safe, multi-tenant chat-with-data agent, SaaS teams with a maintainer who can fork and self-host natural language querying, Engineers evaluating semantic-layer and query-validation patterns before building their own, Teams that need row-level security and tenant scoping in an open-source data agent.
Look elsewhere if you are Non-technical users who need a no-code setup or managed hosting, Production deployments without someone owning the forked codebase, Buyers looking for an actively developed product with a roadmap and support contract.
Skip it if Skip Inconvo if you need a maintained product with a vendor support contract and a release cadence — since the July 2026 Attio acquisition the standalone service is no longer actively developed, so you would have to fork and own the code.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Inconvo actually fits — and what changes day-one when you adopt it.
Clone the repository, run npx inconvo@latest dev against a PostgreSQL replica, then model the tenant table with tenant scoping and row-level security so each customer only sees their own rows.
Outcome: A working natural-language query agent in local development that validates every query before execution and respects tenant boundaries by default.
Wire the Node.js SDK into the app, pass user-context configuration for per-person scoping, and stream answers with response.created, response.progress, and response.completed while Assistant-UI or the Vercel AI SDK renders the conversation.
Outcome: Customers ask questions about their own data in plain language and get scoped, validated answers streamed into the existing UI.
Deploy the MCP server with OAuth support, create a tenant per team, and let internal AI assistants query BigQuery or Microsoft SQL Server through the agent.
Outcome: Teams query the warehouse from their assistant without direct database credentials, with agent traces and usage analytics covering every request.
Use cases
- Embed a natural language query interface in your SaaS product for customer-facing analytics.
- Let support teams ask questions about customer data without writing SQL.
- Serve multi-tenant data access with row-level security so each organisation sees only its own rows.
- Scope answers per end user with user context rather than a single shared database view.
- Monitor query performance and agent decisions with built-in observability and agent traces.
- Deploy a data agent via MCP so AI assistants can query your warehouse under OAuth.
- Use the codebase as a reference for semantic-layer and query-validation patterns before building your own.
- Fork the repository and adapt the query-validation and permissioning logic to your own schema.
Setup time & first value
How long it actually takes to get something useful out of Inconvo — broken out by persona, not the marketing-page minute.
For a developer already comfortable with a Node.js stack, the docs claim you can start querying production data with agents in under five minutes via the CLI — realistically an afternoon once you have connected a database and sketched the first semantic model. Getting answers you trust takes longer: modelling computed columns, table prompts, and rules for your schema is where the real
Switching to or from Inconvo
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From hand-rolled text-to-SQL: replace the freehand SQL generation step with Inconvo's semantic layer and pre-execution query validation, reusing your existing database credentials.
- →From a commercial chat-with-data platform: export your schema rules into Inconvo's semantic model, then fork the codebase so the permissioning and validation logic lives in your own repository.
- ↗From Inconvo to a maintained alternative such as TextQL or Vanna: port your semantic-layer definitions and agent rules, and rebuild query validation against the successor's model.
- ↗From Inconvo to in-house: use the forked repository as the specification for your own agent, keeping the semantic layer and validation logic you already configured.
Integrations
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Inconvo”, and we withheld 6: 6 could not be judged, because “Inconvo” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Inconvo.
Official links
What are the best Inconvo alternatives?
The closest alternatives to Inconvo we list are SQLBot, DB-GPT and Chat2DB. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| SQLBot | Free | Free | — |
| DB-GPT | Free | Free | — |
| Chat2DB | Freemium | Pricing not published | — |
Alternatives to Inconvo
View all
Tools that pair well with Inconvo
Common stack mates teams adopt alongside Inconvo, with the specific reason each pairing earns its keep.
SQLBot
SQLBot turns plain-language questions into SQL, answers and charts over your own MySQL or PostgreSQL database — open source and self-hosted.
DB-GPT
Open-source agentic AI data assistant that writes SQL, runs code in a sandbox, and chats with your self-hosted databases
Chat2DB
Chat2DB turns plain English into runnable SQL across 40+ databases — with AI text-to-SQL that keeps your rows on your own machine.
Inconvo vs its closest rival
Inconvo's closest head-to-head is with Screenplayiq.
Our Inconvo vs Screenplayiq verdict written Jul 3, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Head-to-head comparisons
Inconvo vs Screenplayiq
Verdict being re-reviewed against current pricing and data.
Inconvo vs Versatile
These are not competitors and you should never be choosing between them. Versatile is a physical crane-monitoring system sold to steel erectors — hardware gets installed on your tower or crawler crane, and the software passively reports picks, sequences and delays. Inconvo is a free, self-hosted open-source codebase for developers building natural-language database agents, and as of July 2026 it's joining Attio, so the repo stays up but the company's focus is moving. Buy Versatile if you run crane-heavy steel erection; fork Inconvo only if you have an engineer and want a reference implementation of query validation and multi-tenancy.
GeneratedInconvo vs Geologicai
Verdict being re-reviewed against current pricing and data.
Frequently asked questions
Best-of guides
For makers of Inconvo
- Get a Verified Listing for Inconvo ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Inconvo? Help shape our editorial sentiment research.