Mathesar – an intutive spreadsheet-like interface to Postgres data

How does this compare to retool? I've been using that to build UIs directly on top of Postgres, and it's been nice to be able to design the screens a little; eg inserting new rows linked to a currently selected row by primary key. Curious if you're targeting primarily a spreadsheet-like view, or if the interface can be customized. How does the spreadsheet view work across multiple linked table? Can you present the tabular info in non tabular ways (e.g. a row details or editor view)

Your website says you're a non-profit. Do you have any monetization plans down the line, otherwise how are you planning to maintain funding?

How do you differentiate from, say, dbeaver, or any similar database management software? What's the main reason to get Mathesar instead of DBeaver?

I tried to propose this to our team, But the option that it installs some schemas was a blocker. I do like using this tool on local pgdump.

Any plans to test and support this on Windows Server, since there is nothing directly tied to Linux from what I can tell.

Ah. Thermians, from the Klaatu Nebula. Or was it Dalmations?

Any comments on Outerbase?

That poped up on HN too a few weeks ago.

Thank you! And yeah, I understand your gripe. The tagline is meant to convey the general idea of "editing data in a table UI without a lot of clicks or keystrokes" in the fewest number in words; it does sacrifice precision (although that's why it's "spreadsheet-like" and not just "spreadsheet"). Do you have any ideas for language we could use instead?

Never give up, never surrender!

This is one of the things we're actively considering working on soon! It's mentioned in the "What's next?" section of our beta release announcement: https://mathesar.org/blog/2025/01/29/release-0-2-0

Thanks! We do not have a SQL editor in the UI yet, but it's one of the things we're actively considering working on soon, it's mentioned in the "What's next?" section of our beta release announcement: https://mathesar.org/blog/2025/01/29/release-0-2-0

I'm not sure if this would fit your use case, but you can also use a separate SQL editor alongside Mathesar, we always reflect the latest state of your DB.

NocoDB is a universal database GUI that supports multiple backends, while Mathesar is Postgres-only but deeply integrated with its native features, like using Postgres roles and privileges for access control. NocoDB also adds its own UI-level abstractions on top of database objects, whereas Mathesar directly reflects the database structure. That said, NocoDB has features Mathesar doesn’t yet support, like kanban and calendar views, forms, and more Airtable-like data types.

Baserow is more of an open-source Airtable alternative and doesn’t connect to existing databases at all—unlike Mathesar and NocoDB. It has many of the same UI-driven features as NocoDB, such as different types of views and forms, but it doesn’t function as a database interface the way Mathesar does.

Mathesar, however, has a visual query builder that allows joins and query creation directly from the UI, as well as some data modeling tools, like moving columns between tables and merging duplicate data—neither NocoDB nor Baserow offer these. Mathesar is also 100% open source, while both NocoDB and Baserow follow an open-core model with paid features.

We do want Mathesar to be competitive as an Airtable alternative over time. You can already create a database from scratch (we’re not just a GUI for existing databases), but we’d likely need more data types, views, and integrations before it can match Airtable across a broad set of use cases.

And Postgres is definitely amazingly versatile! That's one of the reasons we were comfortable focusing on it as the only supported DB backend for now.

Ultorg is awesome! Eirik (Ultorg's founder) and I compare notes every once in a while. :)

Yep, Mathesar is GPLv3, not AGPL, so there’s no issue running it alongside proprietary services. Companies can absolutely use Mathesar as a standalone service in their stack without open-sourcing their other components. Another example of this is WordPress, which is also GPL, and has a thriving hosting ecosystem.

GPLv3 only applies if you modify and distribute Mathesar itself, it doesn’t extend to services that simply interact with it. If a company makes changes to Mathesar and distributes that modified version, then those modifications would need to be open-sourced under GPLv3. But using Mathesar as a microservice in an enterprise stack? No problem.

We’d love to see companies upstream fixes and improvements, of course!

As a side note, we _are_ considering adding support for other database backends through Postgres foreign data wrappers: https://wiki.postgresql.org/wiki/Foreign_data_wrappers. If this is something you'd be interested in, please feel free to open an issue on our repo.

Yes, you can try Visual DB: https://visualdb.com

Mathesar doesn’t cache any database state, it always reflects the live structure of the database. If you run migrations through SQLAlchemy or Django, Mathesar will just show the database as it is before and after the migration, no extra steps needed.

You can also modify the data model directly in Mathesar, but if you’re using an ORM-managed database, you’ll need to update the ORM layer yourself to reflect any schema changes. If your ORM expects strict control over the schema, it’s a good idea to configure our permissions to prevent users from making data model changes in Mathesar's UI. Otherwise, it should coexist just fine.