From SQL result to finished report

Turn your query results into a report someone else can read

Point Ottermind at the database you already query. Ask in plain language and get a traceable HTML report, a slide deck, or a weekly analysis that keeps running - with the SQL it ran shown next to every number.

Connect a database

First step

Connect the database before you ask anything

Analysis runs against a source you save once. Here is exactly what Ottermind asks for, what it is allowed to do with it, and where the query actually runs.

Settings - Data sources
A picture of the real form inside Ottermind. Nothing on this page accepts credentials - you enter them once in the signed-in product, where they are encrypted at rest.

Engines you can connect

PostgreSQL family

PostgreSQL, CockroachDB, Redshift

MySQL family

MySQL, MariaDB, TiDB, OceanBase

Warehouses

ClickHouse, Snowflake

Enterprise

SQL Server, Oracle

Local and embedded

SQLite, DuckDB

  • A read-only database user is enough. Analysis only issues SELECT and WITH, so you never have to hand over write access.
  • A database that only listens on a private network is reached through your own bound Ottermind desktop - no public endpoint, no tunnel to open.
  • Credentials are encrypted at rest and passed only to the executing device, never into the model's context or a file.

No database at hand? A local SQLite or DuckDB file works as a source, and so do spreadsheets, CSVs and documents - useful for trying the workflow before you involve a production database.

Coming from Chat2DB?

Chat2DB gets the query right. Ottermind turns it into the deliverable.

Chat2DB is a local-first SQL workspace - 40+ engines, schema browsing, editing, execution. It is where you make sure the number is correct. Ottermind picks up at the next step: when that number has to become a report your team reads, a deck for Monday, or an analysis that runs again next week across more than one source. Same databases, same team.

Chat2DB - open-source SQL workspace
  • Keep querying where you query. Ottermind connects to the same PostgreSQL, MySQL, ClickHouse or Snowflake instance - it does not replace your SQL client.
  • Hand over the part a database client was never meant to do: writing it up, charting it, turning it into slides, and running it again next week.
  • Databases on a private network stay reachable through your own bound Ottermind desktop, so they never need a public endpoint.

Three steps, then it is yours to send

No modelling layer to configure and no semantic layer to maintain. Connect the database, describe the question, keep the artifact.

Step 1

Connect the database once

Add PostgreSQL, MySQL, SQL Server, Oracle, ClickHouse, Snowflake, SQLite or DuckDB under Settings - Data sources. Credentials are stored encrypted and are never passed through the conversation.

Step 2

Ask in plain language

Describe the question, not the schema. Ottermind inspects the tables it needs, writes the SQL, and runs it inside a read-only transaction with a bounded execution budget.

Step 3

Get something you can send

A self-contained HTML report, a slide deck, or a spreadsheet - with every figure traceable to the query that produced it.

Which tool for which job

Both are built by the same team. They are not built for the same job.

SQL client (Chat2DB)Ottermind
Unit of workOne queryOne deliverable
Who it is forDevelopers and DBAsAnalysts, operators, founders
You end up withA result set, a chart, a dashboardA report, a deck, a written conclusion
Engine coverage40+ engines over JDBC8 engine families, cloud or your own desktop
Across sourcesInside one databaseSeveral databases, plus files and documents
Time spanThis query, right nowA question you re-run every week

Engine coverage is where a dedicated SQL client wins, and we would rather say so than pretend otherwise: if you need Hive, DB2, Elasticsearch or Trino, query it in Chat2DB.

What you actually walk away with

The point is not the chat transcript. It is the artifact at the end of it.

Report01

A self-contained HTML report

Headings, accessible tables, legible charts, units and metric definitions - in a single file with no external scripts or trackers, linked back to the query behind it.

Deck02

Slides for Monday morning

The same analysis as a visual deck: the trend, the breakdown, the two things that actually moved, and what you are recommending.

Recurring03

The weekly that runs itself

Run the same analysis again on a schedule and get told what changed since last time, instead of rebuilding the query from memory.

Cross-source04

Beyond one database

Join what the database says with a spreadsheet, a PDF contract or a document in your drive, for the times the answer is not all in SQL.

What it will and will not do to your data

An agent with database credentials should be boring and predictable. These are the limits it runs under.

Read-only by default

Analysis runs SELECT and WITH only. Write statements are rejected, including ones smuggled into a query argument.

Writes are gated and explicit

Single-table inserts, updates and deletes require the source's explicit operation permission plus your confirmation on the prepared change. Supported on PostgreSQL, MySQL, MariaDB and SQLite.

The SQL stays visible

Every figure can be traced to the statement that produced it. A result page is a page, not the whole dataset, and the report is required to say so.

Credentials stay out of the conversation

Passwords are stored encrypted and handed to the executing device, never placed into the chat context or written to a file.

Questions, answered

Is this a replacement for Chat2DB?+

No. Chat2DB is a SQL workspace: connect, browse, edit, run, and be certain the number is right. Ottermind is what happens after that - writing the analysis up, turning it into a deck, and re-running it next week. Most people who use both keep querying in Chat2DB.

Which databases are supported?+

PostgreSQL, CockroachDB and Redshift; MySQL, MariaDB, TiDB and OceanBase; SQL Server; Oracle; ClickHouse; Snowflake; SQLite and DuckDB. If your engine is not on that list, a dedicated SQL client with JDBC coverage is the better tool for it.

Can it reach a database on our private network?+

Yes, through the Ottermind desktop app bound to your account. The desktop executes the query locally, so a database that only listens inside your network does not need a public endpoint. Cloud execution is used only for sources that are reachable from the internet.

Can it modify my data?+

Not during analysis. Queries are restricted to SELECT and WITH inside a read-only transaction. Changing rows is a separate, permissioned path: the source has to grant write operations, the change is prepared first, and you confirm that specific change before anything is committed.

Do I need to write SQL?+

No. Describe the question in plain language and Ottermind inspects the schema and writes the SQL. It still shows you the statement it ran, which is the part that matters when someone asks where a number came from.

What does the report look like?+

A single self-contained HTML file: headings, tables, charts drawn as SVG, stated units and metric definitions. It loads no external scripts, fonts or images, so it behaves the same when you send it to somebody else.

Can it build a PowerPoint from database data?+

Yes. The same analysis can be delivered as a visual slide deck rather than a report, which is usually what a quarterly review or a board update actually needs.

What if the data is not in a database?+

Spreadsheets, CSVs, PDFs and documents work as sources too, and can be combined with a database in the same analysis. A local SQLite or DuckDB file counts as a database source.

How do I know the numbers are trustworthy?+

Aggregates are computed in SQL rather than read off a page of sample rows, time windows and metric definitions are stated, and sampling or missing data has to be disclosed in the deliverable. Paging through results re-runs the query, so a re-opened page reflects the source as it is now, not a frozen snapshot.

How much does it cost?+

Data analysis is part of the Ottermind workspace rather than a separate product. See the pricing page for current plans.

Bring the question, not the schema

Connect a database and ask for the analysis you would otherwise spend the afternoon assembling by hand.