ClickHouse + Querri
Querri copies the ClickHouse tables you choose into its Library and lets anyone on the team ask about them without SQL, next to CRM, billing and support data.
Querri only reads from ClickHouse and never changes your records. SOC 2 Type II, HIPAA and ISO 27001:2022 certified, and your data is never used to train a model.
What you can answer
ClickHouse holds the events, but who pays lives in Stripe or the CRM, and joining them inside ClickHouse means loading that data there first. Querri reads both into one project and answers the question in a single step.
ProjectsEvery analyst writing ClickHouse SQL picks their own event filters, so weekly active numbers drift from report to report. Write the definition once in Querri as a fact or rule and every answer uses it.
Facts & rulesSaved ClickHouse queries still need someone to run them and paste the results into a slide. Querri builds the report from the synced tables and sends it on a schedule.
Reports & automationWhat comes over
Querri copies this data into your Library on a schedule, next to every other system you connect, so one question can draw on all of it.
After the first load, each scheduled sync brings in only rows that are new or changed since the last one.
Querri reads from ClickHouse and never creates, edits or deletes anything there. Every answer runs on Querri's own copy.
Querri's own sharing and row-level access decide who sees which rows, in chat, dashboards, Claude, ChatGPT and the API.
How to connect
Say "connect ClickHouse" or pick it from the connector catalog.
Enter the host and port of your ClickHouse service (8443 for ClickHouse Cloud over HTTPS, 8123 for plain HTTP), plus a username and its password in the secure form. Leave the database empty to use that user's default, or name the one to read.
Pick the data you want and how often it refreshes, then approve the first load.
The data lands in your Library, ready for chat, dashboards and scheduled reports.
FAQ
Fill in the host, port, username and password when the Connector Agent opens the ClickHouse form. ClickHouse Cloud uses HTTPS on port 8443; a self-hosted server can use 8443 with TLS or 8123 without. Then choose the database and the tables to bring in.
Any table or view in the ClickHouse database you choose, with its column types. System databases are hidden from the picker. You select tables one at a time, so raw tables you have no use for can stay out of your Library.
You pick per table. Full reloads run daily, weekly or monthly. Incremental syncs run hourly, daily or weekly and fetch only rows with a newer value in the cursor column you name, such as an event timestamp, which suits large tables that mostly grow.
No. Querri connects over ClickHouse's HTTP interface, port 8443 with TLS or 8123 without, so that is the port to open to Querri. Certificate validation is on by default and can be switched off for a self-hosted server with a self-signed certificate.
No. Querri only reads from ClickHouse. It never creates, edits or deletes records there, and every answer runs on Querri's own copy of the data.
Yes. Querri is SOC 2 Type II, HIPAA and ISO 27001:2022 certified, credentials are stored encrypted, and your data is never used to train a model.
Keep exploring
Connect ClickHouse, add the rest of your systems, and get answers your whole team can check.
