Show HN: DB Pro – A Modern Desktop Client for Postgres, MySQL, SQLite and LibSQL (dbpro.app)

33 points by upmostly ↗ HN
Hi HN,

Over the past few months I've been building DB Pro with my co-founder. DB Pro is a modern desktop database GUI client designed to make working with Postgres, MySQL, SQLite, libSQL and other engines feel fast, visual, and enjoyable.

Our focus has been on the dev-experience. We wanted to absolutely nail the UX and look and feel as we believe most db clients aren't friendly to work with.

Some features:

Visual change review – See pending inserts/updates/deletes before committing them.

Inline data editing – Edit table rows directly without clunky modal dialogs.

Raw SQL editor – A focused editor for running queries with results in separate tabs.

Full activity logs – Track everything happening in your database for peace of mind.

Visual schema explorer – See tables, columns, keys, and relationships in a diagram.

Tabs & multi-window support – Keep multiple connections and queries open at once.

Custom table tagging – Organise your tables without altering the schema.

Tech stack: Electron, React, tRPC, Drizzle ORM, Postgres/MySQL/libSQL/SQLite support, and native builds for macOS at the moment with Windows, and Linux coming very soon.

We're super passionate about this project and we're actually documenting our journey through devlogs. The latest one is here: https://www.youtube.com/watch?v=-T4GcJuV1rM

Thanks, Jay and Jack

8 comments

[ 4.4 ms ] story [ 36.8 ms ] thread
Question comes to mind; Why is Postgres supported but neon coming soon?
Hi guys,

Great to see something fresh in this space. Good luck!

We are building something fairly similar but haven't launched yet. Competition will make all of us do a better job.

How can I trust this tool not to leak my data to third parties?
It's a no for me. I don't want a subscription. Charge whatever you need, give us 1y of updates, charge next year for an upgrade. Do not pull folks into yet another subscription.
To add a little bit to this and why I am so principled against this. I will subscribe to a service, because a service means ongoing work. If you spent months or years building software, and have finished it, charge people what you believe is fair for the work you did up to now. Charge $50, charge $500, your call, sell to 1M people, your call. You have no running costs, you're just selling an app.

If you were running this on some cloud, maybe had some other extras built in that cost you time and money, then there could be a subscription.

If you want to keep your software updated, and are pushing updates daily, weekly, monthly, etc, I could squint at a subscription, but I would rather you just do critical fixes (bc if your product is broken you do owe paying customers a fix without a charge), and put new features in a new version that you will also sell.

People are selling git clients, calculators, db clients on subscription. it's crazy what the world has come to. We don't work to pay you guys rent.

The second I saw this app I was about to click buy (looking for a table plus alternative), went to pricing, saw subscription and immediately dropped it without even trying the free version.

So glad you posted this comment. Exact thoughts here and you saved me from exploring / wasting time.
looks very unified and modern, thank you for the effort but have 2 question: 1. do you consider a feature as a carrier of dbt and apply to different db 2. is there a way to cross query between db sorry i know this might went too far
Love this! Finally something happening in this space. dbeaver was the best, but it's so so ugly and old. I love Datagrip, but no free version.

Please have good formatting of SQL queries - like Datagrip. Very little open source SQL formatters out there, so might require something custom.

And very much waiting for Snowflake support (incl. OAuth)