The questions buyers actually ask before replacing a dbt or YAML semantic layer.
What is an enterprise semantic layer?
A semantic layer is a governed model of your business that sits between your warehouse and the tools that query it. It defines what each table, column and metric means in business language, so every answer is computed from the same definitions rather than re-derived by each analyst or language model.
How is this different from dbt or a YAML-based semantic layer?
dbt and similar tools describe the semantic model in code: YAML files, a repository, a CI pipeline and a build step. Data Convo models the same concepts visually on an entity-relationship canvas and stores them as JSON attached to your live connection. There is no repository to maintain and no build to wait for: you connect a warehouse, define joins, metrics and definitions in the browser, and publish.
Does Data Convo send our warehouse data to a third party?
No. Data Convo is deployed self-hosted via Docker inside your own environment and connects to your warehouse directly. You bring your own language model key (BYOK) and choose the provider, so the only outbound traffic is the schema context and the question you asked, sent to the provider you selected.
How does table-level security work for teams?
Administrators grant access per table and per column for member accounts. The permission list is applied before any query is generated, so a restricted table is never included in the prompt or the generated SQL for that member. Role and column restrictions are enforced server-side, not hidden in the interface.
What happens when the underlying data changes unexpectedly?
Anomaly Studio baselines each monitored column and flags deviations at roughly three standard deviations: null spikes, sudden volume changes and type mismatches. Alerts route to email or a Slack webhook as soon as a metric drifts, so a broken pipeline surfaces before it reaches a dashboard.
Can I ask questions about a chart I am already looking at?
Yes. The Interactive Dashboarding Studio renders results as charts and KPI cards, and you can keep chatting about the visual that is on screen. Follow-up questions run against the same dataset, so you can pivot, filter or drill in without writing SQL.