Why Sameina exists

I'll start from the beginning, because I think an idea without its story is worth little.

Before Sameina, I worked in DevOps and kept running into the same pattern: backends accessing wildly different databases — the same data duplicated across systems that had no idea of each other. The fix was almost always the same: yet another external service to stitch the databases together after the fact. And once AI entered the picture, that usually meant one more separate service just to make that possible.

It felt wrong that this should be the normal state of things. The actual work of getting a coherent picture always had to happen on top, never built in from the start.

At the same time, something else had been on my mind for a while: how to structure data so it can adapt to a company's reality without becoming arbitrary or chaotic.

These two threads — practical frustration in the field, and a genuine interest in data architecture — eventually converged. The core idea: bring fragmented systems together without forcing anyone to rebuild their entire architecture. You can rebuild if you want to. But you shouldn't be forced to.

There's also something more personal driving me. I'm autistic myself, and that shapes how I work and what matters to me. Building an open, honest working culture is part of what I want to pursue with this project long-term.