Sometimes that’ll be a big new feature. Sometimes it’ll be a pile of small improvements that quietly stop annoying you. Both count. This is the first one.

We’re calling it The Debrief.

Audit log that tells you what actually happened

The old audit log showed “Operation executed” for database queries. Which is true, technically. Something was executed. Very helpful. Thanks.

Now it shows you the query. Right there, first thing you see. You shouldn’t have to click three times to find out what someone ran against your production database at 2am.

We also added filters for read, write, DDL, and other. If you want to see only schema changes, you can. If you want to find every write from a specific session, you can. The audit log is supposed to answer questions, and now it does.

Add members to teams when you invite them

Inviting someone and then adding them to their team were two separate steps. So you’d send the invite, forget to do the second part, and wonder why someone showed up in your org with no access to anything useful.

Now you pick their teams during the invite. They join, they’re in the right place, you move on.

The small stuff

There are fixes in this release that don’t deserve their own section. A form that misbehaved. A label that said the wrong thing. A loading state that got stuck. We fixed them because they were wrong, even if they weren’t loud about it.

Thank you, genuinely

Most of what’s in this release came from people who took five minutes to tell us something felt off. That’s not a small thing. You could have closed the tab. You didn’t.

You’re the ones who make us better. We mean that every time we say it.

See you in two weeks.

We’ve been building things together for a long time. Actual LEGO first, then software. Across every company and project since, one thing kept showing up broken: database access security.

Throughout the many organizations and projects we’ve been involved with, security always turned out to be a problem, one way or another. Sometimes it was the budget, sometimes the months of convincing, sometimes the UX tradeoff, and sometimes just a burden the whole org carried quietly.

Support staff with access to every customer’s financial data, engineers who left but somehow still had database access, a “temporary” password living in Confluence or floating around in Slack DMs.

It’s 2026 and this is still the default. Believe it or not, this is the problem many people see as they go on with their day, trying to make something great happen.

Solutions cost you tons in time and money, usually both, need self-hosting and complex long-term investment in maintenance, or are self-brewed and will break sooner rather than later. Could you vibe-code something? Sure, but do you want to do that for something as security-critical as your data? Your customers’ data?

rmBug was built because of this. It gives every person 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 accessing your data.

We launch with MySQL and PostgreSQL today, April 1st. Not a joke.

What we support will grow based on your input, your experience, and your feedback. We’re here, building with you.

Try it at rmbug.com. Tell us what’s missing.

Luka & Mario