Mario Đanić

Our @rmbuginc site saw thousands of percent increase in number of visitors today. Should I write a post on the steps we took through the past decade that brought us here?!

[EKSKLUZIVNI INTERVJU] Startup rmBug, koji su osnovali Luka Kladarić i Mario Đanić, hrvatskog dvojca osigurao 400.000 eura investicije! 🚀 Kada izlaze na tržište i koji ih sve izazovi čekaju, otkrivaju u intervjuu: netokracija.com/startup-rmbug-…

Access control lists are a lie we tell ourselves. You gave 47 people access to production. You have no idea what 44 of them are doing with it.

@ollieforsyth Looking forward to the feedback ;)

@mdjanic Joined the waitlist!

Builders What are you building this week? Drop your project down below - let’s help you land some new users! (For the first 20 responses, I'll personally try your product and give you some feedback).

Something I’ve been building for quite a bit is almost ready. If you care about who accesses your database (and you should), keep watching this space.

Your database is the only system in your stack where you can't answer "who looked at customer data last week" with a name. Think about that.

@psrthsharma This … is fantastic.

i built an open-source database proxy that lets you test against real production data — without actually touching production. writes stay local, merged with reads from prod in-flight. your app gets a verifiable environment for testing. 9 database engines. 4 layers of write protection. and of course, mcp support for your ai agents. meet mori

@wickedguro Temporarily remove the trial xD say, trial starts after today xD

@mdjanic haha, impossible, there is a 7 days trial

I wrote an article on how I got from $21k MRR to $60k MRR. But I am on 58.5 now, so probably release it on Monday

@Navneetshahi15 PostgreSQL, it can do everything, and it can do it pretty nicely for 99,99% of use cases and scales out there.

Hi devs 👋 If you had to choose ONLY ONE database for building a startup MVP: 1️⃣ PostgreSQL 2️⃣ MongoDB 3️⃣ Redis 4️⃣ Something else What would you pick — and why? 🤔 Curious to see what most engineers prefer. #buildinpublic #backend #startups #devlife #developer

@sickdotdev rmbug.com - know exactly who’s in your DB - engineers, machines, everyone.

Pitch your startup: • 1 line about it • Add your link Seen by 63201 people last week. Yes, it counts as marketing, go!🚀

Hot take: the best developer experience is when security doesn't require a separate workflow. If your devs need a different tool to access the database securely, you've already lost.

@EcZachly cap.so - pretty decent and open source.

If Atlassian hadn't bought Loom, the last time I interfaced with an Atlassian product was in 2020. I'm proud to say I'm 6 years sober from JIRA tickets. On that note, I have fallen out of love with Loom. What alternatives are you using in 2026?

Access grants don’t age well. You gave 47 people access to production at various points for various reasons. You know who was granted access. You probably don’t know what all of them are doing with it today. That gap is worth closing.

Every compliance framework asks: "Can you prove who accessed sensitive data?" Most companies answer with a spreadsheet and a prayer.

The gap between "who has access to this database" and "who actually accessed this database" is where breaches live.

4/ Lesson three: Trust is everything. If you’re asking people to route database access through your product, you need to earn a level of trust that most software never has to.

3/ Lesson two: Security products that make people’s lives harder don’t get adopted. They get resented, then bypassed, then blamed when something breaks. The best security is the kind people actually use.

1/ Building a security product is strange. You’re selling people protection against a future they don’t want to imagine. Here’s what I’ve learned so far.