ASK THE QUESTION.
READ THE SQL.

Natural language goes in, a query runs over your event data, and the statement stays visible so you can check it.

The question, the statement, the rows.

The model writes the query; the engine runs it over the project's event store.

Input

Questions instead of dashboards

Type what you want to know. Which campaign brought sessions that reached checkout. How retention moved after a release. Which error precedes a drop in conversion. The model writes the query and the engine runs it.

Output

SQL is the contract

You can edit the statement, re-run it, or take it to your own warehouse.

Repeat

Saved answers

Pin an answer to a project and it refreshes on the same query. Useful for a weekly number that nobody should rebuild by hand.

Shareable chats

A chat can be shared by link with a view of the question, the SQL and the result. Access follows project membership.

What leaves the project.

The question text is sent to the model provider to build the query. Your rows stay in the project store, and the statement runs there.

If the statement is wrong you see the wrong rows, and the statement that produced them.