We Didn't Wait Until We Were Ready

Where It Started

I didn't grow up in a technical family. But my mother was always the one willing to explore new technology, and she encouraged us to do the same. That made all the difference.

Our first computer was a Pentium III ,mostly used for watching movies and playing games. I got my first feature phone at a very young age and immediately started messing with it. Setting SIM locks, forgetting the passwords, then trying everything I could think of to reset it. I explored every function the manufacturer had ever designed into the thing, whether it was meant to be found or not.

Somewhere in all of that, I fell in love with tech.

Curiosity Became an Obsession

When I got my first smartphone, that curiosity found a much bigger playground.

I spent hours exploring every corner of it . From developer options to changing the boot logo. With that knowledge, and access to pretty much every device around me, I became the troubleshooting guy at school and at home.

And then, for some reason I still can't fully explain, I started reading user agreements. Top to bottom. Every time.

It was my first IT teacher who introduced me to scripting and programming, and that changed everything. Up until then, I had been exploring, troubleshooting, and tweaking configs just to have more control. But once I understood how to program, I understood how to create. That depth of knowledge gave me a real understanding of how things worked under the hood , and there was no going back.

Reading through user agreements made me more and more aware of what we hand over without thinking, and that awareness turned into an obsession with privacy. I remember getting so paranoid that I pushed my friends to switch to privacy-first apps , an experiment that didn't last long, because I hadn't yet understood the trade-off between security and usability. Privacy without functionality is just friction, and friction doesn't stick.

Even my own sister mocked me for it. "This guy's scared someone's going to hack him," she'd say, and everyone would laugh.

I kept saying the same thing back: "You never understand the value of your privacy until you've lost it."

Turns out I was right more often than I wanted to be. People started coming to me when they got hacked or scammed.

Finding a Purpose

The recognition I got as the tech guy, the troubleshooting guy, the privacy guy , gave me a real sense of purpose, and I built a lot of my identity around it.

That path eventually led me into offensive security, then malware analysis, then defensive security. Today I sit somewhere in the middle of all of it, Digital Forensics , the space where you piece together what actually happened after everything else has already gone wrong.

Finding the Right People

After my A/Ls, I went on to pursue a Computer Science degree at Kotelawela Defence University. For the first time, I met people who thought the way I did , just as curious, just as obsessed.

From first year, we knew we wanted to build something of our own. We didn't want to wait until we graduated to start. So we told ourselves we'd start in second year instead , once we felt ready.

But then we hit a point where it became obvious, if we waited until we felt ready, that moment would never come.

So we started. And I'm proud to say we made the right call.

The First Chapter

A couple of months later, we found ourselves building systems, shipping software, taking calls from clients in the middle of lectures, and running out to fix bugs the moment something broke.

It wasn't always comfortable. It wasn't always organized. We definitely didn't have it all figured out.

But that was never really the point.

We wanted to build. We wanted to learn. And most of all, we wanted to start before we felt ready.

That one decision became the beginning of something much bigger than we expected.

Development is where we're building our foundation right now. But the instinct that pulled me toward forensics hasn't gone anywhere. It's still how I think about every system we build. Not just how it works, but how it could break, and what we'd need to know if it did. Security is a chapter I still intend to write.

This is the story of how we started.

And we're still writing the next chapter.