We've been building things together for a long time. LEGO first, then software.
Across every company and project since, one thing kept showing up: database access security was broken. Not always dramatically. Sometimes it was the budget. Sometimes months of convincing. Sometimes just a quiet burden nobody talked about.
Support staff with access to every customer's financial data. Engineers who left but somehow still had credentials. A "temporary" password living in Confluence or floating around in Slack DMs.
It's 2026 and this is still the default.
Solutions cost time and money, usually both. Or they need self-hosting and years of maintenance. Or they're homebrewed and will break sooner than you'd like. You could vibe-code something, sure. But do you want to do that for something as critical as
your customers' data?
rmBug was built because of this. It gives everyone touching your database their own identity. No shared credentials, no orphaned access, no murder mysteries. Whether you're two founders or two hundred engineers, you shouldn't need an enterprise
contract or a weekend of self-hosting to know who's in your data.
We launch with MySQL and PostgreSQL today, April 1st. Not a joke.
What we support will grow with your feedback. We're here.
Try it at rmbug.com. Tell us what's missing.
Mario & Luka
Engineers are adopting AI agents faster than any other group. They connect these coding agents to github, slack, linear, jira, datadog, sentry, everything. I saw the limiting factor being the database so sought to build a solution.
But obviously there's a lot that can go wrong giving a raw access point into the database. Querybear is the security layer to protect from anything bad happening.
Been using it for months and we have multiple startups using it and loving it. Have had no issues yet!