Built and currently developing a full-stack web platform for my father’s company that combines multiple businesses: online pharmaceutical product sales, travel agency booking system, printing & design services, ID card printing machine management, CAC certificate processing, and more.
Features include product catalog, booking system, admin dashboard, payment integration, and user management — all powered by clean Python/Flask backend.
This project focused on building and testing a practical AI security assessment lab for evaluating LLM defenses against prompt injection and jailbreak attacks.
I integrated Spikee by Reversec with a locally hosted cybersecurity model running through LM Studio, then added NVIDIA NeMo Guardrails to compare model behavior under three conditions: no guardrails, input filtering, and combined input/output protection.
The work included configuring the local model environment, building a custom FastAPI gateway, integrating NeMo Guardrails, troubleshooting model latency and timeout issues, creating a reusable Spikee target, and analyzing attack results using Spikee’s built-in reporting tools.
The project also explored different adversarial testing approaches, including prompt injection datasets, obfuscation, encoded attacks, Best-of-N testing, synthetic canary leakage tests, and structured benchmark comparisons.
The objective was to measure how much the guardrails reduced successful attacks while keeping the model, dataset, and testing conditions consistent.
This project demonstrates a hands-on approach to LLM red teaming, AI safety testing, prompt-injection assessment, and guardrail validation for organizations deploying generative AI systems.
🚨 What if your business could manage SMS, WhatsApp, Email, users, and messaging gateways from ONE dashboard?
Not 5 different tools.
Not endless switching between platforms.
Not a messy communication workflow.
I built a centralized Business Messaging Platform designed to bring business communication and user management under one roof. 🚀
Instead of building just another admin dashboard, I focused on a real business problem:
Too many communication channels. Too many disconnected tools. Too much manual work.
So I built a system where businesses can:
💬 Manage SMS, WhatsApp & Email communication
👥 Control users, roles & permissions
📧 Create and manage email communication workflows
⚙️ Configure multiple messaging/API gateways
📊 Monitor messaging statistics from one dashboard
🔐 Protect operations with authentication & RBAC
🔌 Connect external services through REST APIs
⚡ Scale the platform as communication volume grows
Under the Hood
Laravel → Secure & scalable backend
React.js → Fast, responsive dashboards
MySQL → Structured data management
REST APIs → Integration-ready architecture
RBAC → Secure user & permission management
API Integrations → Messaging gateways & external services
But the important part isn't the tech stack.
It's what the technology can remove from a business.
Less platform switching.
Less repetitive communication work.
Less fragmented user management.
And one centralized system built around the company's actual workflow.
💡 That’s the kind of software I like building — not just websites, but systems that solve expensive business problems.
If your company is still managing customers, messaging, internal workflows, or integrations across disconnected tools, there may be a much better way to build it.
📩 Need a custom SaaS platform, business dashboard, messaging system, API integration, or automation solution? Let’s build it.
The question I ask before automating anything: "What does this look like on a Tuesday in month four?"
Not the demo. Not launch day. Month four, when the person who championed it has moved on, the data has drifted, and the model has quietly started doing something slightly different.
The automations that survive month four have three things: a human somewhere in the loop, a log a non-engineer can read, and a kill switch that doesn't need me. The PO intake agent I posted last week is built that way on purpose. It registers and notifies, people decide, and every email in and out is logged.
If yours has all three, you're fine. If it has none, I'd love to hear how it's going. I collect these stories.