Most portfolios live on shared hosting—cheap, easy, but restricted. For my infrastructure, I chose a Virtual Private Server (VPS). Here’s why a Systems Engineer treats their “home on the web” like a production environment.

1. The Isolation Advantage

On shared hosting, you are at the mercy of your “neighbors.” If another site on the same IP gets hit with a DDoS or runs a malicious script, your site slows down or goes dark. On my VPS, my vCPU and RAM are mine alone.

2. Full Root Authority

Shared hosting gives you a file manager; a VPS gives you the Terminal. This allowed me to:

  • Implement a UFW Firewall to drop unauthorized traffic.
  • Disable Root SSH Login to prevent brute-force attacks.
  • Deploy Nginx specifically tuned for my latency requirements.

3. End-to-End Encryption

Instead of relying on a generic shared certificate, I managed my own SSL handshake using Certbot and Let’s Encrypt, then integrated it with Cloudflare’s Full (Strict) mode.

Conclusion

A portfolio is more than a resume; it’s a proof of concept. By managing the underlying Linux kernel and network stack myself, I’m not just showing my work—I’m demonstrating the skills I use to protect enterprise data.