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.
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.
I've always wanted to build one of these! This looks like great work, and I like the team-oriented premise.
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?