Server
An exploratory set of questions about self-hosting, serious workloads, and administration that stays close to the operator.
A server should leave the operator in charge.
Omarchy is exploring what an opinionated server stance could mean for people who run their own services and carry responsibility for the work behind them. The hard part is not putting another control panel in front of a machine. It is deciding which choices deserve a strong default and which must remain plainly yours.
This is a set of questions, not a server product.
What should a focused base make easier to reason about?
- Which self-hosted services and production workloads benefit from an opinionated starting point?
- How can remote administration stay legible when the machine is somewhere else?
- Where can agents help with infrastructure work without hiding the commands, files, or decisions from the operator?
Security and updates are design questions.
Defaults can reduce repetition. They can also conceal a choice that deserves inspection. Any exploration here has to ask what a responsible security posture looks like, which update decisions should be visible, and how an operator can understand a system before changing it.
For the current system, begin with the ISO (external) and the Manual.