Exploratory
Cloud
An exploratory set of questions about a hosted Omarchy workstation, persistence, synchronization, compute, security, and ownership.
A workstation somewhere else still has to feel like yours.
Omarchy is exploring what a hosted workstation would have to preserve before it deserves the name. A remote machine can change where work runs, but it should not blur who owns the environment, who can inspect it, or what happens to the work left inside it.
That is a question of boundaries, not a shortcut around them.
What must persist when the screen changes?
- What should remain in an environment between sessions, and what should remain only with the person who created it?
- How could synchronization stay understandable when files, configuration, and agent work move between machines?
- What kinds of compute belong in a hosted environment, and how should that choice stay visible to the person using it?
Security and ownership cannot be footnotes.
Any serious exploration has to begin with access, data boundaries, and the ability to understand what is happening to your work. Convenience is useful. Control is the point.
For the current local system, begin with the ISO (external) and the Manual.