Secuna platform
Backend engineerLaravel + MySQL services powering vulnerability research, researcher payouts, and client reporting. AWS-hosted, MFA-gated, built for auditability.
$ whoami
Backend engineer at Secuna since 2023. Ten years in PHP/Laravel and MySQL, three of them deep in vulnerability research and application security. Systems-first, patterns second.
I've spent a decade writing backend code — mostly PHP and Laravel, always with MySQL close by. I think procedurally even after years of OOP: I reach for the system and the solution first, then patterns only if they earn their keep.
I've been at Secuna since March 2023, working on a platform that sits at the seam of the web and security: researchers submitting vulnerabilities, clients reviewing and paying out, infra that has to be trustworthy by default. The same three years have put me on AWS (ap-southeast-1) daily — EC2, RDS, S3, and CloudWatch in production — and watching real attack patterns up close has shaped how I build: application and infrastructure security as first-class concerns, auditability treated as a feature, and MySQL carrying most of the weight.
On the side I'm learning Go — building small CLI tools to internalize goroutines, channels, and idiomatic error handling. I've also touched Next.js, Vue, Docker, and Livewire. Frontend work I can do; backend is where I'm deep.
Owning Laravel services, MySQL schemas, and AWS infra (ap-southeast-1) for a cybersecurity vulnerability research and reporting platform.
CLI tools for the team — learning concurrency patterns (goroutines, channels, interfaces) by building things we actually use.
Ten years of MySQL fluency — schemas, indexes, query plans, migrations. Writing APIs that backend engineers want to consume.
React and Next.js to ship features end-to-end. Comfortable in the codebase, but my depth is on the backend.
Laravel + MySQL services powering vulnerability research, researcher payouts, and client reporting. AWS-hosted, MFA-gated, built for auditability.
Small Go tools for devops and ops workflows. An excuse to get fluent with goroutines, channels, and idiomatic error handling.
$ date
April 2026 — ap-southeast-1
$ status
Two ways to reach me. Both work; both filter the noise.