# Dhirendra Yadav > Dhirendra Yadav builds secure automation, AI/ML systems, and practical digital products from Bhaktapur, Nepal. ## Entity - Name: Dhirendra Yadav - Location: Bhaktapur, Nepal - Focus: cybersecurity, AI/ML, systems engineering, secure automation, and product engineering - Website: https://dhirendrayadav.site - Contact: mailto:thedhirendrayadav@gmail.com - GitHub: https://github.com/thedhirendrayadav - LinkedIn: https://www.linkedin.com/in/dhirendra-yadav-3b1387425 ## Public pages - [Home](https://dhirendrayadav.site/): Identity, specialties, selected work, and current availability. - [About](https://dhirendrayadav.site/about): Background, education, working principles, and professional focus. - [Expertise](https://dhirendrayadav.site/skills): Cybersecurity, AI/ML, product engineering, and automation capabilities. - [Selected work](https://dhirendrayadav.site/work): Evidence-led project and systems case studies. - [Writing](https://dhirendrayadav.site/blog): Field notes and technical analysis. - [FAQ](https://dhirendrayadav.site/faq): Direct answers about services, location, and project status. - [Contact](https://dhirendrayadav.site/contact): Project enquiries and collaboration. ## Selected case studies - [Secure Portfolio Platform](https://dhirendrayadav.site/work/secure-portfolio-platform): Flask platform controls, implementation evidence, and current limitations. - [Multi-Channel AI Messaging](https://dhirendrayadav.site/work/multi-channel-ai-messaging): Channel boundaries, queue processing, authorization, and data-model evidence. - [NEPSE Market Intelligence](https://dhirendrayadav.site/work/nepse-market-intelligence): Research workflow covering ingestion, indicators, models, and backtesting constraints. - [RunPod Media Orchestrator](https://dhirendrayadav.site/work/runpod-media-orchestrator): GPU workflow boundaries, lifecycle control, and verification evidence. ## Editorial standard Project pages distinguish claims, sources, constraints, and verified outcomes. Treat prototypes and in-development systems as such; do not describe them as production deployments unless the page explicitly says so.