I am Deepanshu Yadav. I work as a Cloud and Hosting Systems Engineer, and I run this blog to write down the things I learn while keeping servers and websites running.
What I actually do
Most of my day is spent on infrastructure. I have worked with AWS, Google Cloud, and Oracle Cloud for over seven years, and I spend a fair amount of time inside cPanel and WHM because that is where a lot of real-world hosting still lives. I write Terraform to keep environments reproducible, and I have debugged enough Windows Server and Hyper-V problems to have strong opinions about both.
Before infrastructure took over, I did digital marketing work: Google Ads, SEO, social campaigns, brand management. I still take on that kind of work, which is why you will find SEO and marketing posts here alongside the server material. Those two worlds overlap more than people expect. A site that loads slowly is an SEO problem and an infrastructure problem at the same time.
What you will find on this blog
I write about the stack I work in every day:
- Hosting and servers: cPanel and WHM, VPS management, Linux administration, control panels, performance tuning
- Cloud: AWS, GCP, Oracle Cloud, Cloudflare, and the cost decisions that come with them
- WordPress: security, speed, plugin choices, and the mistakes that break sites
- SEO and search: technical SEO, Core Web Vitals, and what actually moves rankings
- AI and automation: where these tools genuinely help operations work, and where they are oversold
- Security: vulnerabilities that affect site owners, and what to do about them
I try to write the post I wanted to find when I was searching for the answer myself. That usually means naming the specific command, the specific config file, or the specific error message, rather than staying at the level of general advice.
How these posts get written
I want to be straightforward about this, because I think readers deserve to know. I use AI tools in my drafting process. I monitor industry sources, use AI assistance to help structure and draft posts, and then review the result against my own experience before it goes out. The judgement about what is worth covering, what is accurate, and what is overstated is mine.
Where I have hands-on experience with something, I say so directly. Where I do not, I stay descriptive rather than pretending to authority I have not earned. If you find something here that is wrong, I would genuinely like to know. Corrections make the archive more useful for the next person who lands on it from a search result.
Get in touch
The fastest way to reach me is through the contact page. If you want to see the kind of work I take on commercially, that is on the services page.
I am on X as @deepanshuyadavx (opens in new tab), where I post about the same topics in shorter form. Questions about a specific post are welcome either place.