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.

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.

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.