Fresh installation / One guided route
Build the runway. Let Kiteyard take flight.
Bring up Headquarters and Agent Manager on a fresh server with the canonical installer, clear safety boundaries, and a verification step after every stage.
Choose your path
The same installation, shaped for two operators.
Both paths derive from the active Kiteyard installer and deployment documentation. Pick the interface that fits how you want to work.
For humans
Review requirements, copy a safe prompt into your coding agent, and understand the decisions it will ask you to make.
Open the guided setup → 02 / Operational runbookFor agents
Follow a staged, machine-readable procedure with exact commands, stop conditions, secret-handling rules, and post-install checks.
Read the agent runbook →A controlled installation
Inspect. Change. Verify.
Kiteyard’s installer generates and protects its own internal credentials. Your operator supplies only the choices that cannot be inferred safely.
Preflight failures stop the run before the host is changed further.
Passwords and tokens are entered directly into protected prompts or files.
OpenAI embeddings, Portainer, and external MCP clients come after a healthy core.
Scope boundary
One core. Optional providers stay separate.
A fresh installation brings up Headquarters, Agent Manager, and PostgreSQL. Portainer remains an optional, separately deployed provider for Agent Manager Environment Management.