Welcome
AI Orchestrator — Documentation
Reference content for the docs site at docs.hivedeploy.in. Every doc fits one of four Diátaxis types.
Start here
Doc · When to read
QuickstartFirst 10 minutes — sign up, connect a cloud, deploy a Postgres.Concepts — AgentsUnderstand what specialist agents are and how they work.Concepts — GatesUnderstand the deployment flow (Gate 1 → Gate 6).Concepts — Self-healingWhat happens after apply: health verification, the bounded auto-repair ladder, the template flywheel.
How-to guides (task-oriented)
Doc · Goal
Connect AWSConnect a customer AWS account via cross-account IAM roleConnect GCPConnect a customer GCP project via Workload Identity FederationConnect AzureConnect a customer Azure subscription via service principalInvite teammatesAdd members to your org, set roles, transfer ownershipApprovals workflowRequire admin approval before risky deployments runNotificationsIn-app + email notification settingsBilling & plansPlan limits, upgrade flow, usage tracking
Reference (information-oriented)
Doc · What’s in it
Explanation (understanding-oriented)
Doc · What you’ll understand
Troubleshooting
Doc · Symptom
Cloud connect — 403 errorsProbe fails after Connect — common causesGCP deploymentsCloud Run /healthz 404s, quota walls, 409 residue, empty log panels — from our published campaign dossiersAWS deploymentsALB 5xx during boot, AZ capacity, JVM OOM, EKS metrics, EIP/VPC quotas — from our published campaign dossiersDeployment stuck at Gate NA deployment session won’t advanceCommon errorsSearchable list of error messages and fixes
Conventions used in these docs
- Code blocks with language tags get syntax highlighting in the
rendered docs (
bash,yaml,python,tsx, etc.) - Inline
codefor env var names, file paths, function names > Note:callouts for important info> Watch out:callouts for common mistakes- Headings use Title Case; the doc title is
# Page Title(single H1) - Every page declares its Diátaxis type in the header (Tutorial / How-to / Reference / Explanation)
- Examples use real values from the platform (real region IDs, real
agent names) — not
<placeholder>syntax unless absolutely necessary
What’s intentionally NOT here
- Internal architecture documentation — that lives in
docs/superpowers/specs/anddocs/superpowers/plans/in the monorepo. Customer-facing docs should never expose internal feature-flag names or implementation details. - Marketing pages — the docs site is for users who already signed up. Pre-signup content lives on the landing page.
- Sales / pricing details — those change too often; link to the pricing page rather than mirroring.
Maintenance
- When a feature ships, add or update the relevant doc in this folder in the same PR. Code without docs is half-done.
- When a customer hits a confusing error and contacts support, add it
to
troubleshooting/common-errors.mdso the next customer self-serves. - When a competitor’s customer asks “do you do X?”, add an explanation doc covering it — half the time that becomes the deciding factor on the trial.