Posts
Shop

Core Thesis

A home.arpa domain behind every modem.

HOMESERVER exists to make professional-grade infrastructure personally owned and locally controlled. Instead of renting core services from surveillance platforms, users run their own stack on hardware they control.

Why Now

What used to require racks now runs on compact, efficient, low-power hardware. The cost and power barriers have dropped enough that enterprise-style capability can live on normal home and small-business networks.

What We Deliver

  • One box, one local domain, many services
  • Core network control: firewall, DNS, DHCP, VPN
  • Core self-hosted stack: media, files, passwords, Git, books, feeds, docs
  • Full ownership model: no telemetry, no remote vendor control, no subscription trap
  • Open software foundation with root access and extensibility

Operating Principles

  • Owned: You own the hardware and deployed software.
  • Controlled: You decide what runs, how it runs, and where data lives.
  • Capable: The system is built as real infrastructure, not a toy appliance.
  • Transparent: Code and practices are open to inspection.

Maintenance and Continuity

We maintain active distributions with updates, security, and compatibility work.

If legal constraints force a distribution change, we execute a structured handoff:

  • freeze and document the legacy stack,
  • publish transferable maintenance procedures,
  • transition stewardship so operators can maintain users who stay on that older distribution,
  • continue mainline development in the new repo path without abandoning existing deployments.

Strategic Direction

  1. Finish and harden the home server platform.
  2. Add local AI capabilities tied to the home server.
  3. Deliver HOMERCHY as the receiver interface for the home.arpa ecosystem.
  4. Expand into business server offerings for on-prem environments.

End State

Networking done right: privately owned, personally controlled, professionally capable.

The internet should be curated by the user, not by ad-tech platforms. Your machine fetches what you choose, and you consume from infrastructure you own.