Question 1

Does Convalesce apply fixes on its own?

Accepted Answer

No. The most it does is open a pull request against your repository, with the evidence attached. You review it and you merge it.

Question 2

What does Convalesce need access to?

Accepted Answer

Read access to your run metadata and your tables. Convalesce reads the shape of your data all the time: schemas, types, row counts, lineage. While it investigates a failure it may also run small read-only queries to confirm a cause. Those are capped, personal columns are masked, the rows are never stored, and what comes back is sent to the AI model. You can switch reading off for any connection. Access to your code is a separate step you choose, by installing the GitHub app on the repositories you pick.

Question 3

Does our data leave our environment?

Accepted Answer

Only the incident bundle does, and only what the investigation needs. It covers the failed run and nothing else. It is not a copy of your warehouse.

Question 4

How long does setup take?

Accepted Answer

Sign in with GitHub or Google, answer three short questions, and connect the tools you want. Convalesce starts building context on the next failed run.

Question 5

Which tools are supported?

Accepted Answer

The integrations listed above are live today, and more are on the way. The docs have a setup guide for each. If you run something that isn't there, tell us what.

Connect the tools you already run.

Orchestration and processing

Warehouses, lakes and databases

Streaming and ingestion

Catalogues, code and dashboards