// the find
mathesar-foundation/mathesar
An intuitive spreadsheet-like interface that lets users of all technical skill levels view, edit, query, and collaborate on Postgres data directly. 100% open source and self hosted, with native Postgres access control.
Mathesar is a self-hosted web UI for Postgres that lets non-technical users browse, edit, and query data through a spreadsheet-like interface — without writing SQL. It maps directly to real Postgres objects (tables, schemas, foreign keys, roles) rather than adding its own abstraction layer on top. Aimed at teams where developers own the database but non-developers need to work with the data.
Uses native Postgres access control instead of rolling its own permission model — you grant a Postgres role and Mathesar inherits those privileges, which means your existing security boundaries hold. The query builder generates real SQL joins rather than flattening everything into a denormalized view, so the underlying schema stays clean. Business logic lives in Postgres functions (the db/sql directory contains substantial PL/pgSQL), which means it works with any Postgres client, not just Mathesar. Active development with a release history going back through 0.11 versions and commits as recent as yesterday.
Still in public beta, and the presence of a db/deprecated directory with substantial legacy code (full query, transform, and function subsystems) signals the architecture has shifted significantly mid-build — you may hit rough edges from that transition. The stack is Django + Svelte, which is two distinct frameworks to understand when something breaks in the middle. No multi-database federation: each Mathesar install connects to databases one at a time, so if you need a unified view across several Postgres instances you're out of luck. The custom data types (email, URL validated at the DB level) are a nice idea but are Mathesar-specific column types, meaning if you ever remove Mathesar those columns leave behind custom type dependencies in your database.