In regulated environments, infrastructure usually stays out of sight — until something goes wrong, or until someone asks you to explain it during an audit.

Then the simple questions matter:

• Who accessed this data?
• Can that action be traced?
• Is behaviour consistent across environments?
• Where is the data actually stored?

If those answers aren't clear, the system becomes a risk.

"Build systems that are easy to explain and reliable when it matters most."

— Abdul Karim, Co-founder & Software Architect

At Complere, I'm building on the same responsibilities I had at Scilife as Software Architect and Infra Lead. The scope has grown, but the work still comes down to the same thing: build systems that behave predictably, stay understandable, and hold up when someone looks closely.

At Scilife, I worked on systems that had to scale globally while still meeting regulatory expectations. In a regulated SaaS setup, architecture and infrastructure go hand in hand. Architecture decisions shape what infrastructure has to support, and infrastructure choices shape what can be audited and traced.

A big part of that work was making sure performance and reliability held up under load. The systems carried strict SLA commitments across regions and environments, with critical workflows expected to stay responsive under load. In regulated systems, that's more than an uptime number. It reflects the quality of the architecture, the discipline of the operations, and how consistently the system behaves under pressure.

Over the past decade I've worked on platforms that grew from early adoption to thousands of users — part of a journey from 1 client to 200+ and from 10 users to 20,000+. That experience taught me what reliable systems need as they scale: predictable behaviour, strong controls, and discipline across sandbox, validation, and production environments.

My work has focused on multi-tenant architecture, tenant isolation, access control, audit trails, and data residency. The aim has stayed the same: build systems that are easy to explain and reliable when it matters most.

I come from the same small-village roots as the rest of the founding team. That background shaped how we build — stay grounded, focus on substance, stay consistent, and build something that lasts.