10 comments

  • figassis 13 hours ago ago

    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.

  • metadata a day ago ago

    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.

    • upmostly a day ago ago

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

  • etht3x 11 hours ago ago

    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

  • atmanactive 18 hours ago ago

    How can I trust this tool not to leak my data to third parties?

    • upmostly 14 hours ago ago

      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.

      • atmanactive 9 hours ago ago

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

        • upmostly 9 hours ago ago

          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.

  • spicypixel a day ago ago

    Question comes to mind; Why is Postgres supported but neon coming soon?

    • upmostly a day ago ago

      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.