Hacker Newsnew | past | comments | ask | show | jobs | submit | upmostly's commentslogin

https://dbpro.app

I’m building DB Pro, a modern desktop database client for developers who want a fast, local-first workflow.

I started in October 2025, launched v1 at the end of November, and just crossed $1k MRR.

I also post devlogs of life building and marketing DB Pro and am about to post devlog #4. The latest one is here if anyone’s curious: https://youtu.be/-T4GcJuV1rM

Still very early, but it’s been fun seeing something fairly “boring” resonate once the UX is treated seriously.


Loved the design, looks better then the most tools I've tried. I'm using Prisma + Supabase in one of my side projects and having constant db issues. Can I integrate DB Pro? Will it replace Prisma or what?


So DB Pro is a local desktop database client for managing your databases and data. Prisma ORM it won't replace, but Prisma's browser-based data browser, yes it will absolutely replace that. It's not a replacement for Supabase, it works alongside it, if that answers your question?

I'm planning to extend DB Pro into much more than a database manager though, letting you build dashboards, workflows and workbooks.


I've been trying to connect to Supabase, got help from an agent to but couldn't resolve the issue and connect :/

What’s actually broken

DB Pro:

Enforces strict TLS verification

Uses its own certificate trust bundle

Does not:

read macOS System Keychain reliably

allow custom CA injection

allow “require but don’t verify”

Supabase pooler requires either:

trusting Supabase’s CA, or

allowing non-verified SSL

DB Pro supports neither.

So it fails with:

self signed certificate in certificate chain

This is a product limitation / bug in DB Pro.


Any reason why neon isn't supported even though it speaks the postgresql wire protocol?


It has some behaviour differences (connection handling, pooling, serverless constraints) that I want to support properly rather than “mostly works”. Right now I'm focused on making the core experience rock solid across the most common setups first. My focus has been UX and DevEx and it's working.

Neon support is on the roadmap though, and once I add it, it’ll be first-class rather than a checkbox integration.


For what it’s worth, I think there’s space for such an app for Duckdb databases. It’s growing in popularity and not very widely supported yet.


Hi! When will Windows/Linux be available? I'm growing weary of DB Browser for SQLite.


Windows and Linux are both launching next week (just in time for Xmas!)


Looks cool and congrats on the $1k MRR! Is the app built with electron?


Thanks!

Yep, it’s built with Electron. Performance has been a big focus from day one, and it’s been really performant in all of my testing so far. The goal was a proper desktop-first experience with local performance and direct database access, rather than trying to force it into a web app. Although I do have plans to offer a self-hosted version as well.


semrush shows that your organic visits significantly increased this week. Well done. Great product. Succes!


What did you use to build the frontend? It looks cool!


How do you enforce licensing? Did you build your own solution?


https://dbpro.app

We are working on DB Pro, a modern desktop data workbench for developers and data engineers.

The focus is on going beyond a query editor and building a complete environment for working with data. Visual exploration, inline editing, dashboards, and Jupyter notebook style workbooks for queries, notes, and experiments all in one place.

We launched v1 a few weeks ago and the reaction has been genuinely jaw dropping. Downloads, feedback, feature requests, and some great long form discussions around real world data workflows.

We are documenting the entire journey through a public devlog series. The latest video covers the v1 launch.

https://youtu.be/-T4GcJuV1rM

Honestly, building a desktop app is so refreshing after spending a decade or so building web apps.


Literally exactly as I meant it. I watch a lot of cooking shows, too, so this analogy holds up.


Great catch, I'll add that now!


Thanks Simon! Looking into that now. Big fan. Hope you enjoyed the post.

Edit: This should now be fixed for you.


I was inspired to write this blog post after reading bambax's comment on a HN post back in 2023: https://news.ycombinator.com/item?id=37082941


Thanks for taking the time to share your thoughts. We’ve heard this feedback loud and clear from a lot of people, and we completely understand where you’re coming from.

We’re about to introduce a one time purchase option that includes a full year of updates. No subscription required. This will be available later this coming week.

Really appreciate you checking out the project and pushing us to make the right call for our users. Stay tuned.


Really appreciate you listening, looking forward to taking another look


We just wouldn't do that in a million years.

Our goal is to build the best DB client around, and one aspect of that is building trust. We haven't even added user analytics tracking into the product.


So, if I would connect to a local server on my LAN, my firewall should show zero internet traffic from DB Pro?


Without a doubt, 100%. In fact, you can use it offline if you want. We only make network requests when authorising user accounts. But even then you don't need to create an account. You can just use the free version offline.


Agreed! The more competition, the merrier. Good luck to you guys!


Great question! Postgres is supported right away because it behaves like a standard, direct database connection. But with services like Neon and Supabase, there are extra nuances we want to handle properly.

We want Neon, Supabase, and similar cloud providers to feel like first-class citizens inside DB Pro and not just “another Postgres connection”. Each of them has their own quirks, authentication flows, and connection requirements. For example, Supabase actually needs a paid IPv4 add-on if you want to connect to it in the traditional way, which isn’t obvious to most users.

So instead of lumping them in as generic Postgres connections, we’re building dedicated flows that understand these details and make the whole experience seamless. That’s why they’re marked as “coming soon”. We’re doing them properly.

It all goes back to our UX first philosophy to build the absolute best experience.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: