Install & Run¶
Install AutonomyOps ADK and bring up your first stack. This section is organized by operator intent: choose the path that matches what you’re actually doing.
Audience |
Path |
Where it lands |
|---|---|---|
Single-host operator running ADK locally with CE artifacts |
CE First Stack |
This page (install) + the CE First Stack tutorials below |
Partner/customer deploying under a controlled-deployment agreement |
Controlled First Stack |
Published in the SaaS tier site (see note below) |
Robotics operator bringing up the demo robotics stack locally with CE artifacts |
Robotics CE First Stack |
|
Just evaluating, want to see ADK in 2 minutes |
(not here) |
Why these are separate. The CE path runs on Community Edition
distribution artifacts under the ADK CE Distribution Artifact License
(see LICENSE-CE-ARTIFACTS.md at the repo root) — local / single-node
/ limited-internal-operations posture. The Controlled path is the
partner/customer deployment governed by a separate Commercial
Agreement: orchestrator + fleet topology, staged rollout, audit and
compliance workflows, supportable production. “Controlled” denotes
managed, governed, auditable deployment with operational controls —
not a pricing tier.
Install¶
The canonical install one-liner:
curl -fsSL https://get.autonomyops.ai/install.sh | bash
This places the autonomy binary on PATH (default /usr/local/bin) and,
in the same step, fetches the matching quickstart bundle to
~/.autonomyops/quickstart/. The bundle ships the demo docker-compose.yml,
the demo_up.sh bring-up helper, example configs, and QUICKSTART.md — the
inputs an installed operator needs to bring the demo stack up without a
repo checkout.
Bundle fetch is default-on but fail-soft: if the bundle is missing
for the resolved release tag, or unzip is not installed, the binary
install still succeeds and the script exits 0 with a single warning.
To opt out (binary only, no bundle):
AUTONOMY_INSTALL_QUICKSTART=0 curl -fsSL https://get.autonomyops.ai/install.sh | bash
To install only the binary and fetch the bundle manually later (for
example, on a host without unzip at install time):
# 1. Install just the binary
AUTONOMY_INSTALL_QUICKSTART=0 curl -fsSL https://get.autonomyops.ai/install.sh | bash
# 2. Fetch the bundle later, against the version you installed.
# `autonomy version` prints six labelled lines; the version tag is on
# the line whose first field is "version", so anchor the awk match on
# that field instead of taking the last field of the whole output
# (which would be the platform).
VERSION="$(autonomy version | awk '$1 == "version" { print $NF }')"
curl -fsSL -o /tmp/adk_quickstart.zip \
"https://github.com/autonomyops/adk/releases/download/${VERSION}/adk_quickstart_${VERSION}.zip"
mkdir -p ~/.autonomyops/quickstart
unzip -q -o /tmp/adk_quickstart.zip -d ~/.autonomyops/quickstart
After install, bring up the demo stack:
bash ~/.autonomyops/quickstart/demo/scripts/demo_up.sh
What an installed operator can do without a repo checkout is documented in the Demo Runbook under “Operator paths”.
Installed: the extracted quickstart bundle ships the numbered demo
scripts (01_build.sh, 02_push_attach_sign.sh,
03_verify_and_run.sh), the policy sources under demo/policies/,
the cosign key generator under demo/keys/generate.sh, the lock
fixture under demo/locks/, and the demo Python agent under
demo/agent_py/. Installed operators run the same end-to-end flow as
in-repo operators do via make demo-* — the paths above are
bundle-relative, not repo-relative.
CE First Stack¶
Local / single-node CE-artifact path. Bring up the demo stack, run the included Python agent, and walk through the three CE concept tutorials.
Robotics CE First Stack¶
Robotics demo flow on local CE artifacts. The Controlled robotics deployment path is on the roadmap and will land alongside the controlled fleet-orchestrator surface; until then this page is CE-only.
Robotics CE First Stack
Hosted-control-plane onboarding is published in the SaaS tier: see the SaaS tier site.