users
♢ idINT
nameVARCHAR(255)
created_atDATETIME
A local workspace for curious minds
Follow real records and their connections. Compare what matters, bring in your data and turn questions into SQL, all in one local workspace.
Runs locally with Docker. Stays on your machine.
Meet your workspace
Switch views, choose a table and follow a record. This little store is yours to explore.
Scroll sideways to see the full schema or table.
♢ idINT
nameVARCHAR(255)
created_atDATETIME
♢ idINT
user_idINT
created_atDATETIME
♢ idINT
order_idINT
product_idINT
quantityINT
priceDECIMAL(10,2)
♢ idINT
nameVARCHAR(255)
priceDECIMAL(10,2)
created_atDATETIME
Illustrative workspace · sample data
From curiosity to clarity
Explore your schema. Keep your SQL. Make room to experiment.
Start with a record and follow its real connections on a flexible canvas.
Write, run, and save SQL.
Create named SQL restore points.
A place for every part of your work
Start with a record. Follow its connections. Keep the details you need beside you, without writing SQL.
Choose a database in the top bar. Open Database → Explore, open Sources, then choose a table and search for a record.
Select a record and expand a connection, or use a suggested question to show linked records. Select a line to inspect matching fields, values and source SQL.
Drag cards, pan and zoom, or choose Orbit or Flow to arrange the canvas. Pin cards, filter tables, hide cards and undo presentation changes.
Explore only reads records. Moving or hiding a card never edits or deletes its source. Connections follow declared foreign keys; the map loads only the records you request.
The rows and the bigger picture. Find a value, inspect a field, understand how your tables fit together.
Use Records to browse, search and edit MariaDB rows. Schema shows table details, columns, keys and a diagram of table relationships. Explore follows individual records within that structure.
Keep one record in view while you follow the next. Make space for a closer comparison.
Choose Open in window to keep records side by side in draggable windows. In the top Tools menu, open Second screen: pin up to four records on the Comparison desk, or let the Relationship radar follow your selection. Two windows on one monitor work too.
Each window keeps its original source. Comparison pins last until the companion window closes or reloads.
A quieter top bar. The tools you need, together in one place.
The database selector sets your workspace context. Tools groups the selection pointer, second screen, local AI, refresh, context export, database creation/import, language and your account. Settings holds appearance and layout preferences.
Turn on the selection pointer to inspect a control or data item without activating it. Shift-click combines selections; More explains the selection.
Database → Tools is for import, export and backups. The top Tools menu contains workspace-wide controls.
From a spreadsheet to something you can explore. Preview first, then choose where your data belongs.
For MariaDB, choose Open database → Import files for CSV, TXT/TSV, Excel (.xlsx), JSON or ZIP archives containing these files. Preview the file, choose a sheet and destination, then confirm the database. SQL import offers preflight and post-import checks; official phpMyAdmin remains available for larger SQL files and database administration.
Importing can change data. A file import does not create relationships automatically. Create a restore point before changes you may need to reverse.
Turn a question into a query. Save your research and keep a restore point before the next experiment.
Research lets you build a read query visually or write, run and save SQL yourself. Use Database → Tools → Backups to create, download and restore MariaDB restore points. Restore replaces that database; an import or SQL script has no universal undo.
A little help, on your terms. Optional local AI and source-based project search, right beside your work.
Explore works without AI, which is off by default. If you configure local Ollama, the assistant can explain schema context and propose SQL for Research. Project code search shows local files and source lines, even with AI off. Model answers never execute SQL automatically.
A few practical things, before you make it your own.
Yes. Enable the optional PostgreSQL connection to browse records, search, inspect Schema and use Explore. With its separate writer connection you can add, edit and delete records. Free SQL, imports, restore points, AI and phpMyAdmin currently belong to MariaDB.
PostgreSQL setupThe first account becomes the installation owner. Later registrations need approval in Account → Access requests. Approved accounts share that installation’s database access.
Database records, saved research, restore points and accounts stay in Docker volumes. Language, appearance and dashboard layout stay in your browser. Explore maps, comparison pins and AI conversations are temporary; reloading starts a new session for them.
On your machine. On your terms.
Try Govern. Share an idea. Help shape what comes next.
MariaDB · Optional PostgreSQL · Docker Compose · Optional local AI
Each installation has its own accounts. Your account opens this workspace; your databases stay in your Docker installation.
Create an account