We're not a big company.
We're two people who really love databases.
Stacknesia started with a simple frustration — every time we faced a tricky database problem at work, the resources online were either too generic, too outdated, or just plain wrong. We kept solving the same problems from scratch, and we knew other engineers were too.
So we decided to write it all down. The real stuff — the migrations that almost went wrong, the HA setups that took three attempts, the monitoring configs that actually work in production. Not the sanitized version. The honest one.
We're both still working full-time as database engineers, which means everything here comes straight from what we're dealing with today — not what we dealt with five years ago.
Meet the team
"I've migrated databases that were older than my career. Every scar taught me something — and I'd rather you skip the scar part."
"Managing 100+ databases teaches you one thing: everything will break eventually. The question is whether you're ready when it does."
How Stacknesia came to be
We met at the same company — a data consulting firm where we both worked as database consultants. Day after day, we were solving similar problems for different clients across banking, finance, telco, and insurance. It didn't take long before we realized we were thinking about the same things.
"We didn't build Stacknesia because we had all the answers. We built it because we kept searching for answers and coming up empty — so we decided to become the resource we wished we had."
Long term? We want to build something bigger — a proper database and infrastructure consultancy. But right now, we're starting where every good thing starts: by being genuinely useful to the people around us.
If you're a DBA, a data engineer, a developer who suddenly became responsible for a database, or someone trying to build their career in this space — this place is for you.