Overview
Hostwright is a Mac-native desired-state control plane for Apple container workloads. Start here.
Hostwright is a Mac-native desired-state control plane for Apple container workloads. Today it can initialize and validate a hostwright.yaml manifest, render a non-mutating manifest-level plan, show manifest-level status, and run safe doctor checks. Runtime observation and apply are planned behind one runtime boundary.
It is built for one machine: an Apple silicon Mac running a recent macOS with Apple container installed. It is not a cluster orchestrator, and it does not try to be.
What you get
- A declarative manifest,
hostwright.yaml, for local stacks. - A current non-mutating planning step that does not inspect Apple container.
- A planned reconciler that will converge actual state to declared state and report drift after runtime observation exists.
- A single runtime adapter boundary that all future Apple container behavior must cross.
- A planned safety model where destruction is explicit and cleanup is ownership-aware.
How these docs are organized
These docs follow the same split that larger infrastructure projects use, so each page has one job:
| Section | Answers |
|---|---|
| Concepts | How Hostwright thinks: desired state, the adapter, reconciliation, the Apple container boundary, safety. |
| Reference | Exact surfaces: the CLI, the manifest, compatibility, and limitations. |
| Design | Why the project exists, what it refuses to do, and where the name comes from. |
Where to start
- New here? Read Why Hostwright for the motivation, then Desired state.
- Want the boundaries first? Read Non-goals and Limitations.
- Looking for the shape of the tool? See Getting started and the CLI reference.