Plainbase

Questions for PostgreSQL · Private preview

Your database, in plain English.

Ask a question the way you would ask a colleague. Plainbase writes the SQL against your PostgreSQL schema, runs it read-only, and hands back the rows, a chart and the query itself, so you can check the answer.

See how it works Get Plainbase
  • PostgreSQL
  • Read-only queries
  • Your choice of model
Illustration of Plainbase’s query page with a sample schema and made-up figures.

How it works

Three steps, nothing hidden.

  1. 01

    Connect PostgreSQL

    Enter host, port, database and a user, test the connection, then save it. Passwords are encrypted at rest with AES-256-GCM.

  2. 02

    Ask a question

    In English. Your schema goes to the model as context, so the SQL it drafts uses your real tables and columns.

  3. 03

    Check, then keep it

    Read the rows, the chart and the SQL. Ask a follow-up, export the result, or pin it to a dashboard.

Features

An analyst’s first draft, in seconds.

Plainbase is for founders, marketers and operators who know what they want to ask but not how to write the query. Treat each answer as a draft to check, not a verdict.

01

Ask, then keep asking

The model sees your live schema, keys and relationships. Earlier turns go along with each question, so “now split that by region” just works.

02

The SQL is always one click away

Every answer comes with the query that produced it, how long it took and a short explanation, so you can check the logic and learn from it.

03

Read-only by design

Generated SQL passes a guard that rejects writes, stacked statements and locking clauses, then runs in a READ ONLY transaction with a 30-second timeout.

04

A chart that fits the answer

Bar, line, area, pie, scatter or table, suggested by the model with a fallback heuristic. Export rows as CSV and any chart as PNG.

05

Learn the schema first

Browse tables, columns, keys and approximate row counts. Generate plain-English table descriptions and a list of questions worth asking.

06

Dashboards and history

Pin answers to dashboards, reorder and refresh them, and share a read-only link. Every question, with its SQL, row count and timing, is kept in a searchable history.

Before real data

Use a read-only role and test data for now.

  • Give it the least access it needs

    The guard is a careful pattern scanner, not a full SQL parser. Connect with a PostgreSQL role that can only read the schemas you want to ask about.

  • Shared links are open doors

    Anyone with a dashboard’s share link can view it and rerun its pinned queries against live data, without signing in. There is no per-viewer scope or rate limit yet. Make it private again to revoke the link.

  • TLS is not verified yet

    The connection form’s TLS option encrypts traffic but skips certificate verification. Connection errors can show raw driver messages.

  • Answers need review

    Your schema and questions are sent to the AI provider you configure. Generated SQL can be wrong; accuracy has not been measured.

Get Plainbase

In private preview.

There is no hosted sign-up yet, and the source is shared by invitation. If you have access, run your own instance with its own PostgreSQL store and AI provider key.

Run your own instance 
git clone git@github.com:aylith-labs/plainbase.git
cd plainbase/app && npm install

# Database URL, AI provider key, and two secrets:
#   openssl rand -base64 32   -> AUTH_SECRET
#   openssl rand -hex 32      -> ENCRYPTION_KEY
cp .env.example .env.local

npm run db:push    # create Plainbase's own tables
npm run dev        # http://localhost:5570

Needs repository access. Commands run in your own terminal.

  • Node.js 24

    The app is Next.js 16 with React 19. Register an account on first run.

  • A PostgreSQL database for Plainbase

    Separate from the databases you query. It stores accounts, saved connections, history and dashboards.

  • An AI provider key

    OpenAI by default; Anthropic, Google and OpenRouter work through one setting. Your provider account and costs apply.