Reuse your Connections
Charts run against the Integration Connections you already configured — no separate BI credentials. Configs stay encrypted and are decrypted per run, with a fresh client per query.
Explore is self-serve BI without another deployment: save SQL queries against the database Connections your company already has as named Charts, choose a visualization, and pin the results onto Dashboards the whole team reads at a glance. “What was MRR last month?” becomes a question any teammate — or any AI employee — can answer by running the Chart instead of improvising SQL.
Charts run against the Integration Connections you already configured — no separate BI credentials. Configs stay encrypted and are decrypted per run, with a fresh client per query.
Write SQL in the editor with inline errors and a live result preview, then save it as a named Chart. Every execution runs under a 30-second timeout and a 5,000-row cap.
Table, scalar, bar, line, area, and pie — with a live preview of each against your current result set, configured in a side panel. All rendered as inline SVG, no chart-library dependency.
Pin Charts as cards on a drag-and-drop 12-column grid with per-card resize, and override a Chart's title per context — MRR on the finance board, Revenue (MTD) on the home one.
Charts and Dashboards default to read for every AI employee; authors get write on what they create. Humans grant, revoke, or promote from the Share menu.
The executor doesn't pretend to enforce read-only — the docs tell you to connect a SELECT-only database role, so even a write-granted employee can't UPDATE your production data.
AI employees use Explore through ten built-in tools — list, get, and run Charts; create and update them; assemble Dashboards — under the same execution envelope humans get.
Asked for a number, an employee lists the company's Charts, finds the right one, and runs it — reusing the SQL a human already blessed instead of guessing at schema.
With write grants an employee can create Charts and Dashboards the team sees — the same way it already authors Notes and Base records.
Every AI query goes through the same executor: 30-second wall-clock timeout, 5,000-row cap, credentials decrypted per run and never exposed to the model.
Postgres, MySQL, and ClickHouse today. Snowflake, BigQuery, and Redshift connectors are on the roadmap.
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.
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.
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.
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.
Persistent AI teammates with a written constitution, markdown playbooks, and cron-scheduled work — every execution captured as a readable Run.
Learn moreSlack-style channels and DMs where AI employees are real members — @mention one and it joins, replies, and reports back from its Routines.
Learn moreA Linear-style task manager where any todo can be assigned to a human or an AI employee — with an in-review flow that closes the trust gap.
Learn moreMulti-table workspaces with typed fields, saved views, comments, and attachments — and 21 built-in tools for granted AI employees.
Learn moreOne command pulls the image and starts Genosyn on localhost:8471. Write their soul. Schedule their first routine.