Tutorials Projects Hardware Topics About

About RPiServer.com

We're a small team of homelab engineers who got tired of outdated tutorials that hadn't been tested on real hardware. So we built the resource we wished existed.

Our mission

RPiServer.com exists to make self-hosting and homelab building accessible to anyone - from first-timers who just got their first Raspberry Pi, to seasoned sysadmins who want a reliable reference they can trust.

Every tutorial on this site is written from direct, hands-on experience. We don't publish a guide until we've completed it ourselves, on actual Raspberry Pi hardware, and verified that it works as described. If something breaks, we update it.

Meet the team

Marcus Webb
Co-Founder · Networking & Security

9 years in network engineering and Linux systems administration. Runs a 12-node homelab powered primarily by Raspberry Pi hardware. Has a particular interest in DNS, VPNs, and network-level security. Certified in CompTIA Network+, Security+, and Linux+.

Sara Lin
Co-Founder · Storage & DevOps

Software engineer with 11 years of experience in backend systems and infrastructure. Builds and maintains self-hosted cloud storage, Docker stacks, and CI/CD pipelines on Raspberry Pi clusters. Former sysadmin at a managed hosting company. Holds AWS Solutions Architect certification.

Raj Krishnan
Contributing Author · Home Automation & IoT

Electrical engineer turned home automation enthusiast. Runs a fully self-hosted smart home stack on three Raspberry Pi units. Specialises in Home Assistant, MQTT, Zigbee, and low-power sensor deployments. Has contributed to several open-source home automation projects.

Our editorial standards

  • All commands are tested on a fresh install before publishing
  • We state which Pi model and OS version was used for each guide
  • We update guides when software versions change significantly
  • We disclose all affiliate and sponsored relationships clearly
  • We do not accept payment to recommend specific products
  • We link to official documentation, not just our own content

Get in touch

Questions, corrections, or collaboration inquiries? We read every email.

Contact us →