I'm building DB Pro, a cross-platform database management app that lets you browse, query, and manage SQLite, PostgreSQL, MySQL, Redis, MongoDB, and more from a single native interface. It's been growing steadily with a community of ~1,400 subscribers on YouTube and paying users.

What I'm most excited about right now is DB Pro Studio: a collaborative web-based version I'm building on top of it.

The idea is simple: databases are a team activity, but every DB tool treats them as a single-player experience. Studio adds either a self-hosted or managed hosted data browser, real-time collaboration, dashboards, visual workflow automation, and enterprise features like audit logging and role-based access. Think "database command center" where your whole team can inspect, query, and build on your data together.

The desktop app acts as the execution engine (your data never leaves your infrastructure), while Studio provides the shared dashboard layer.

I've also consistently posted devlogs on YT throughout the journey, which has helped build a community of ~1,400 subscribers who've shaped the product along the way.

Site: https://dbpro.app YouTube: https://youtube.com/@dbproapp

Would love feedback from anyone who's felt the pain of sharing database context across a team.

▲

bityard 6 hours ago | parent | next [-]

It's fascinating to me that people are still making money on RDBMS UIs in 2026. Maybe there's hope for my markdown notes app after all?

	▲	upmostly 6 hours ago \| parent [-]
		Developers are pretty willing to pay for tools that save them daily friction, even in crowded spaces. I find that the trick is finding the wedge that makes yours feel essential rather than nice-to-have. At the end of the day, people pay to save time. Doesn't matter if it's been done to death.

▲

Cyclone_ 7 hours ago | parent | prev | next [-]

I like the way you have the detailed roadmap of features for each version. It's nice for the user to feel connected to development like that.

	▲	upmostly 6 hours ago \| parent \| next [-]
		I find that when people can see what's coming, they're more invested in the product and more likely to share feedback that actually shapes the direction. The devlogs on YouTube serve the same purpose. It's a two-way street.
	▲	yakkomajuri 5 hours ago \| parent \| prev [-]
		If you want to go a step further the PostHog roadmap items are all GitHub issues that users can upvote which gives a great sense of who wants what in the community. https://posthog.com/roadmap (disclaimer: I used to work at PostHog)

▲

steve_adams_86 7 hours ago | parent | prev | next [-]

I've always wanted to build one of these! This looks like great work, and I like the team-oriented premise.

	▲	upmostly 7 hours ago \| parent [-]
		Thanks Steve! The team angle came from mine and my co-founder's own frustration. We kept copy-pasting query snippets and results of queries into Slack/Teams to our engineering team but also Sales/Marketing etc. Figured there had to be a better way. If you ever want to give it a spin, I'd love to hear your thoughts.

▲

yakkomajuri 5 hours ago | parent | prev [-]

I've honestly been looking for this -- a modern slick db management app, both for local dbs and remote (just for me though, no collaboration). Existing tools are solid but they feel outdated.

Downloaded and onboarding was nice. A couple of things:

- The initial schema for my local Postgres table was showing public but there were a bunch of tables showing that clearly were not tables in my public schema. Changing the schema to something else and back worked.

- Limiting the free version on number of tabs feels... annoying. I appreciate that a lot of stuff out there doesn't even have a free version but the software automatically opened with a few tabs (or I accidentally clicked on it?) and then as soon as I clicked on my first table I was paywalled. I feel like I'll accidentally open more tabs (even though I really just wanna work on one at a time) and get frustrated, which is more likely to drive me away than to pay at this point.

Note btw that ofc you have to make money and this is a product that I feel I'd be willing to pay for but I got frustrated within 2mins of using it so it wasn't like oh I've felt the value let me pay, it was more like I haven't even gotten to value yet.

Great work anyway and I'll keep trying and provide feedback as it comes! Thanks for building this