Quickstart

From an empty account to a running release in three steps. This walkthrough uses the chat dock; every step maps to a single MCP tool call, shown alongside.

Before you begin

• A git repository High can reach (public, or connected through a git provider).
• At least one machine to run on — a cloud account, a VPS, or a Pi. High enrolls it as an outpost.
• The web console open, or an MCP client connected.

1 · Create a project

Tell High where your code lives. It clones the repo, detects the stack, and scaffolds a first stage called dev.

# in the console chat dock
create a project called acme from
github.com/acme/api

{
  "tool": "create_project",
  "arguments": {
    "name": "acme",
    "git": "github.com/acme/api"
  }
}

✓ project acme created
stage dev scaffolded · detected: node 20
next → enroll an outpost to run it on

2 · Enroll an outpost

An outpost is any machine running the High agent. Enroll one and it joins your private overlay, ready to accept placements.

enroll my raspberry pi as an outpost

{
  "tool": "provision_node",
  "arguments": { "name": "rpi-home", "backend": "raw" }
}

# run this on the machine, once
curl -fsSL https://acme.high.systems/install.sh | sh -s -- \
  --token ent_9f3c1a…

✓ rpi-home joined the overlay · backend: raw

3 · Bring it up

Now render a release — your build, the default config, onto dev — and let the engine reconcile it.

bring acme/api/dev up

{
  "tool": "deploy_release",
  "arguments": {
    "project": "acme", "stage": "dev"
  }
}

Deploying r-204 to acme/api/dev — rolling out.
  → build b-118 · sha256:9f3c1a
  → api 3/3 ready

✓ acme/api/dev is up

Next steps

• Core concepts — the object model behind every command here.
• Configs — env, resources, scaling, and secret refs.
• Routes & ingress — put your service on a domain.