The latest articles on DEV Community by Nchiminyi — Founder, Kriosa (@kriosa). https://dev.to/kriosa https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4010602%2F41284738-5a4f-4116-8b26-36ca4722c94f.png https://dev.to/kriosa en Nchiminyi — Founder, Kriosa Wed, 01 Jul 2026 09:01:58 +0000 https://dev.to/kriosa/why-i-built-a-security-tool-for-php-developers-in-africa-423b https://dev.to/kriosa/why-i-built-a-security-tool-for-php-developers-in-africa-423b <p>I'm Nchiminyi, a PHP/Laravel developer from Cameroon.<br> A few months ago I watched a developer I know spend 3 days trying to figure out why his client's Laravel site got hacked. No tools. No logs that made sense. No affordable WAF built for his context.<br> That bothered me enough to build something.<br> I spent the last few months building a security middleware for PHP apps. The part I'm most proud of is not the threat detection — it's that it explains exactly why a request was blocked, not just that it was blocked. Most WAFs are a black box. This one isn't.<br> Still early days. <br> If you build PHP or Laravel apps, I'd love to know — what's your current security setup? Do you even have one?</p> php laravel security webdev