Your AI. Your machine. Your rules.

I didn't set out to build enterprise AI infrastructure. I was modding a GTA server.

When I wanted to write my own anticheat, I didn't trust someone else's code with something I couldn't verify. So I started from first principles: audit everything. Cryptographic hashes on every action. If the hash doesn't match, it didn't come from my system. A tamper-evident chain of everything that happened, provable and exportable.

Then I came across the EU AI Act. I realised that what I'd built out of instinct was something compliance-aware enterprises were being legally asked to produce and couldn't easily get. That sent me into the regulation properly, then into Thailand's PDPA, because that's my home market and my family is here. The architecture in SOSA DevOps was built deliberately around both frameworks.

My background is teaching. Years in Bangkok covering English, IELTS, and standardised test prep from SAT to TOEFL. What I brought to software is what teaching gave me: structure, patience, and a refusal to ship anything I can't stand behind and explain clearly.

I grew up across four countries. My family's circumstances meant school in Laos, then the Philippines at ISM from Grade 1 through 12, with summers back in Udon Thani and Christmases in Australia. Moving around that much gives you languages, perspective, and a clear sense that where you're from shouldn't determine what tools you have access to.

The family I grew up around in the Thai countryside doesn't have enterprise budgets. Neither do most of the hospitals, clinics, legal firms, and small teams around the world handling sensitive data every day. They shouldn't be one breach away from disaster simply because the right infrastructure was priced out of reach.

That's what this is built for.

If you're building in a regulated environment and want to talk through what this could look like for your team, you can reach me at [email protected]