Ask your production database in plain English

Type a question. It compiles to SQL, runs against a read replica, and comes back as a chart in about three seconds.

  • 3.4s medianto first chart
  • Read replicanever writes
  • 1,284 tablesindexed nightly
Monthly recurring revenueLAST 30D
WK 1WK 2WK 3WK 4
Signups by sourceLAST 7D
Tables in the live schema1,284+12.4%
Median time to answer3.4s+3.1%
Governed definitions612+24.6%
Cohort retentionWK 1-7
Checkout conversionLAST 30D
WK 1WK 2WK 3WK 4
Saved querySQL
01select plan_tier, net_retention02from billing.account_month03where status = active04and net_retention >= 0.6005group by 1, 206order by 2 desc07limit 500
Questions per dayLAST 7D
Monthly recurring revenueLAST 30D
WK 1WK 2WK 3WK 4
Signups by sourceLAST 7D
Tables in the live schema1,284+12.4%
Median time to answer3.4s+3.1%
Governed definitions612+24.6%
Cohort retentionWK 1-7
Checkout conversionLAST 30D
WK 1WK 2WK 3WK 4
Saved querySQL
01select plan_tier, net_retention02from billing.account_month03where status = active04and net_retention >= 0.6005group by 1, 206order by 2 desc07limit 500
Questions per dayLAST 7D
Monthly recurring revenueLAST 30D
WK 1WK 2WK 3WK 4
Signups by sourceLAST 7D
Tables in the live schema1,284+12.4%
Median time to answer3.4s+3.1%
Governed definitions612+24.6%
Cohort retentionWK 1-7
Checkout conversionLAST 30D
WK 1WK 2WK 3WK 4
Saved querySQL
01select plan_tier, net_retention02from billing.account_month03where status = active04and net_retention >= 0.6005group by 1, 206order by 2 desc07limit 500
Questions per dayLAST 7D
FernlightStonebrookCoastwisePinegroveHallowayMarbrookFernlightStonebrookCoastwisePinegroveHallowayMarbrookFernlightStonebrookCoastwisePinegroveHallowayMarbrookFernlightStonebrookCoastwisePinegroveHallowayMarbrookFernlightStonebrookCoastwisePinegroveHallowayMarbrookFernlightStonebrookCoastwisePinegroveHallowayMarbrook

Data teams who stopped filing a ticket to get a number.

The Monday numbers used to take an analyst until Wednesday. Finance pulls them before standup now.
Dana WhitfieldHead of Data, Fernlight
Fernlight
It writes the same SQL I would have written, and it shows me the query before it runs a thing.
Marcus ReidAnalytics Lead, Stonebrook
Stonebrook

One sentence, one dashboard

Every answer arrives as a chart you can pin, rename and put on a wall - not as a result set somebody has to explain.

Revenue by planLAST 30D
WK 1WK 2WK 3WK 4
Tables in the live schema1,284+12.4%
Weekly retentionWK 1-7
Refunds by reasonLAST 7D
Trial to paidLAST 30D
WK 1WK 2WK 3WK 4
Answers matched to source96.2%+0.8%
Median time to answer3.4s+3.1%
Support load by dayLAST 7D
Active accountsLAST 30D
WK 1WK 2WK 3WK 4
Refund rate

asked every Monday by the support leads

Signups by source

the growth standup opens with this one

Failed payments

checked twice a day by billing ops

Warehouse spend

finance watches the cost per query

Active accounts

board deck, first slide, every quarter

Cart abandonment

merchandising reruns it after each release

Queue depth

on-call checks it before every deploy

Seat utilisation

renewals pull it ninety days out

Refund rate

asked every Monday by the support leads

Signups by source

the growth standup opens with this one

Failed payments

checked twice a day by billing ops

Warehouse spend

finance watches the cost per query

Active accounts

board deck, first slide, every quarter

Cart abandonment

merchandising reruns it after each release

Queue depth

on-call checks it before every deploy

Seat utilisation

renewals pull it ninety days out

Ask the way you talk

No dialect to learn: the questions your team already asks each other, typed straight into the bar.

Refund rate

asked every Monday by the support leads

Signups by source

the growth standup opens with this one

Failed payments

checked twice a day by billing ops

Warehouse spend

finance watches the cost per query

Active accounts

board deck, first slide, every quarter

Cart abandonment

merchandising reruns it after each release

Queue depth

on-call checks it before every deploy

Seat utilisation

renewals pull it ninety days out

Refund rate

asked every Monday by the support leads

Signups by source

the growth standup opens with this one

Failed payments

checked twice a day by billing ops

Warehouse spend

finance watches the cost per query

Active accounts

board deck, first slide, every quarter

Cart abandonment

merchandising reruns it after each release

Queue depth

on-call checks it before every deploy

Seat utilisation

renewals pull it ninety days out

One definition, every answer

A metric means one thing here. The definition is versioned and reviewed, and every answer carries the version it used.

Metric definitionSQL
01select plan_tier, net_retention02from billing.account_month03where status = active04and net_retention >= 0.6005group by 1, 206order by 2 desc07limit 500
Net revenue retention6 MONTHS
JANMARMAY

Everything it can read

Point it at the replica you already run. It reads the schema, learns the joins your analysts use, and re-indexes the whole thing every night.

Browse connectors
1,284
Tables in the live schema
3.4s
Median time to answer
Prod replicaLedgerWarehouseAd spendEvent streamTicketsProd replica
TicketsWarehouseAd spendProd replicaLedgerEvent streamAd spend
Event streamAd spendLedgerWarehouseTicketsProd replicaWarehouse
Ad spendProd replicaTicketsEvent streamWarehouseLedgerTickets

Your data stays yours

Read-only by defaultThe connection is a replica role. It cannot write or drop.
Every query loggedWho asked, what ran, what came back. Kept seven years.
Nothing is copied outIt queries in place. No extract, no shadow copy of your rows.
Row rules honouredWhatever the database enforces per role, the answer enforces too.
Nothing trains a modelYour schema and your rows are never used as training data.
Deleted means deletedDrop a connection and its index and history go within the hour.
Audit logLive
  • d.whitfieldasked refund rate by region
  • svc-digestran 6 scheduled questions
  • m.reidopened the retention definition
  • p.ramanexported 8,204 rows to CSV
  • svc-indexre-indexed billing.account_month
  • t.elderdenied: that column is masked
  • s.lindqvistpinned churn by plan to a board
  • d.whitfieldedited net revenue retention
  • svc-alertsfired: refunds above 2.4%
  • m.reidasked why tuesday signups fell
  • j.okaforgranted read on ledger.invoice
  • svc-replicarotated the connection key
  • d.whitfieldasked refund rate by region
  • svc-digestran 6 scheduled questions
  • m.reidopened the retention definition
  • p.ramanexported 8,204 rows to CSV
  • svc-indexre-indexed billing.account_month
  • t.elderdenied: that column is masked
  • s.lindqvistpinned churn by plan to a board
  • d.whitfieldedited net revenue retention
  • svc-alertsfired: refunds above 2.4%
  • m.reidasked why tuesday signups fell
  • j.okaforgranted read on ledger.invoice
  • svc-replicarotated the connection key

Priced by the question

No per-seat maths. Everyone can ask, and you pay for what the warehouse actually runs.

Team$0first 200 questions a month

For one team on one replica, with the SQL always shown.

  • One connected replica
  • Saved questions
  • Community support
Start free
Company$1,200per month, 5,000 questions

For a company where finance, growth and support all ask daily.

  • Unlimited connections
  • Governed definitions
  • Scheduled digests
  • SSO and SCIM
Start a trial
Regulated$4,800per month, 25,000 questions

For estates with row-level rules, key custody and a named reviewer.

  • Single-tenant VPC
  • Bring your own key
  • Named reviewer
Talk to us

What people ask

06

The six that come up on every evaluation call, with the short answer to each.

No. The connection is a read-only replica role and the generated SQL is shown before it runs. If it cannot read a column, it says so rather than guessing around it.

You see the SQL, not just the chart. Correct it once and the correction is saved against that question for everyone who asks it after you.

Your data team. Definitions live in version control and get reviewed like code, and every answer carries the version it used - so two people asking the same question get the same number.

Yes, on the regulated plan: single-tenant, in a VPC you own, with keys in your KMS. Nothing leaves the account except the answer somebody asked for.

The index is rebuilt nightly, so schema size costs nothing at query time. Median time to a first chart is 3.4 seconds across roughly 1,284 tables.

Nothing writes, so the worst case is a bad chart. Every question is logged with its SQL and its result, which makes a wrong answer reproducible.

Ask the first question

Point it at a read replica, type one sentence, and see what comes back.