Explore: SQL saved as Charts and Dashboards · Genosyn

Explore queries Postgres, MySQL and ClickHouse.

Explore is BI without a second deployment. Write SQL against a database Connection your company already configured, watch the rows come back in the preview, and save the query as a named Chart with one of six visualizations. Pin that Chart to a 12-column Dashboard and "what was MRR last month" costs one click, for a Member or an AI Employee.

Install GenosynGuide Read the Explore docsDocs

Genosyn running a Founder & General Manager use case in Explore.

MRR by month

postgres · 8 rows

MRR

$48,220

+8.4% vs last month

select month,sum(mrr)
from subscriptions
group by 1
order by 1;

Chart refreshed June closed at $48,220, up 8.4%.

Six chart types render as SVG.

BI on the database Connections you already have: SQL saved as Charts, pinned to a 12-column Dashboard, runnable by any AI Employee.

01: Postgres, MySQL, and ClickHouse Connections you already have

Charts run against the Integration Connections you already configured, so there are no separate BI credentials to hold. Configs stay encrypted and are decrypted per run, with a fresh client for every query.

02: One save turns the SQL into a Chart

Write SQL in the editor with inline errors and a live result preview, then save it as a named Chart. Every run stops at a 30-second timeout and a 5,000-row cap.

03: Six visualizations render as inline SVG

Table, scalar, bar, line, area, and pie, each configured in a side panel and previewed live against your current result set. Everything renders as inline SVG, with no chart-library dependency.

04: Pin Charts to a 12-column drag-and-drop grid

Pin Charts as cards on a drag-and-drop 12-column grid with per-card resize. A Chart's title can be overridden per context: MRR on the finance board, Revenue (MTD) on the home one.

05: Every AI Employee starts at read on a Chart

Charts and Dashboards default to read for every AI Employee, authors get write on what they create, and humans grant, revoke, or promote from the Share menu.

06: A SELECT-only database user is the actual guard

The executor doesn't pretend to enforce read-only. Connect a SELECT-only database role, as the docs tell you to, and even a write-granted employee can't UPDATE your production data.

Questions · 5 answered

Which databases does Explore support?

Postgres, MySQL, and ClickHouse today. Snowflake, BigQuery, and Redshift connectors are on the roadmap.

Do I need to set up separate credentials for BI?

No. Explore reuses your existing Integration Connections — set one up under Settings → Integrations and it appears in Explore's Connection picker. Credentials stay encrypted on the Connection row and are decrypted per run.

Can AI Employees run and build charts?

Yes. Every employee defaults to read access on every Chart and Dashboard — list, get, run — and gets write on ones it authors. Humans grant or revoke per Chart or Dashboard from the Share menu.

What are the query limits?

Every execution — ad-hoc from the editor, a saved Chart, or an AI Employee's run — goes through the same executor with a 30-second wall-clock timeout and a 5,000-row cap; larger result sets are truncated server-side.

Is Explore read-only against my database?

Read-only enforcement is deliberately not baked into the executor. Connect with a separate SELECT-only database user, and no query — human or AI — can write to your production data.

Tomorrow one thing is finished before 09:30.

Install Genosyn, register an AI Model, write one role, and put it on a schedule. The company grows from there.

Install on your own hardwareGuide Read every line on GitHubSource(opens in a new tab)