Skip to content
All work
Case study · 02

Playfair

Ask your data in plain language. Get the chart, the number and the SQL behind it.

Try the live demoNo signup · sample data
Status
In development
Category
Data & analytics
Platform
Web app
Role
Product, design & engineering
Year
2026

Named after William Playfair, who invented the line and bar chart in 1786.

Connect a database, a spreadsheet or a CSV, ask a question, and get an answer you can trust, pinned to live dashboards your team will actually read.

The problem[01]

Most teams have the data but not the answers. Founders wait on analysts and operators live in spreadsheets. Tools that let you “chat with your data” return confident numbers that nobody can check.

Our approach[02]

Playfair shows its work. Every answer comes with the interpretation it used, the SQL it ran, the rows behind the number and a confidence level. If ambiguity would change the answer, the agent asks. If it wouldn't, the agent states its assumption.

Walkthrough

The 60-second demo

The path a first-time visitor takes through the live demo, from the first click to the moment it clicks.

Follow along in the demo
  1. [01]

    Open the demo workspace, with a sample e-commerce database already connected.

  2. [02]

    Ask “Monthly revenue this year” and get a line chart, the headline number and the SQL.

  3. [03]

    Ask which products have the highest return rate, with a minimum of 50 orders, and get a bar chart and a table.

  4. [04]

    Ask “Why did revenue drop in April?” The agent breaks it down by region and category and shows its evidence.

  5. [05]

    Pin all three to a dashboard and share a read-only link.

Features

What it does

We can build data products: safe text-to-SQL, tasteful charts, and dashboards that don't look like admin panels.

[01]

Connect anything

Postgres, MySQL, Google Sheets or CSV and XLSX uploads, with schema introspection, type inference and a semantic layer.

[02]

Show the SQL

Generated SQL with syntax highlighting, a plain-language explanation, and editing for analysts. Diffs when it changes.

[03]

Read-only by design

Read-only transactions, statement timeouts, row caps and a cost guard for heavy scans. Your data is never written to.

[04]

Right chart by default

Time series get a line, comparisons get bars and single values get a KPI tile. Easy to override, no chart junk.

[05]

Why analysis

Ask why a number moved. The agent ranks the drivers across every dimension it can see and shows the evidence charts.

[06]

Dashboards to read

Pin any answer in one click, filter globally, share read-only links and schedule reports to email or Slack.

UX principles

How it behaves

  • Show the work. Every number links to its SQL and its rows.

  • Ask before guessing. Clarify when ambiguity changes the answer; otherwise guess and say so.

  • Never break silently. Stale, drifted and failed states are always explicit and repairable.

V1 targets

  • <3mTo a first answer
  • 0Writes to your database
  • 100%Answers with their SQL
Built with

The stack

The same typed, server-first stack as every Asrar product. The model does the reasoning, and the product does everything around it.

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • PostgreSQL
  • Prisma
  • Claude

Your next idea deserves to ship this season.

Tell us what you're building. We'll come back with questions, a plan and an honest estimate. No templates and no shortcuts, just software that does its job.