Install · H33-Key v0.1

One command. From source.

No pre-built binaries yet. You build the same source we ship. Honest about it.

$ curl -fsSL https://h33.ai/install/install.sh | sh

Requires Rust (the installer will tell you how to get it if it's missing).

What this installer does

Seven steps. Nothing more, nothing faked.

1

Detects OS + architecture. macOS or Linux on arm64 or x86_64.

2

Checks the Rust toolchain. If cargo is missing, prints the rustup install command and exits.

3

Builds h33-key from source. cargo install --git ... --branch h33-key/v0-standalone. ~60-90s first build.

4

Verifies the install. Runs h33-key --version and confirms the binary is reachable.

5

Prints first commands. Working examples for wrap, run (env + stdin), and delegate.

6

States what's wired vs gated. Side-by-side ✓ / ⏳ list so you know exactly what works today.

Honest about what's gated

What this installer does NOT do (yet)

These need the scif-backend runtime substrate. Until then, the installer does not pretend they work.

⏳ Binding a terminal to a Root (TerminalCertificate issuance)
⏳ Registering with the dashboard / Agent-008 wizard
⏳ H33-74 receipt emission per use
⏳ Root / Q-Sign policy binding
⏳ Read Attestation Registry sync on h33-key accept

When the runtime ships, this installer gains --bind <token> and the missing onboarding steps. Today it does what it can honestly do.

Don't pipe curl to sh? Install manually.

Some people don't trust curl | sh. Reasonable. Here's the manual path.

# 1. Read the script first.
$ curl -fsSL https://h33.ai/install/install.sh -o install.sh
$ less install.sh

# 2. Run it when satisfied.
$ sh install.sh

# OR skip the script entirely — just cargo install directly.
$ cargo install --git https://gitlab.com/drata5764111/h33/scif-backend.git \
                --branch h33-key/v0-standalone --bin h33-key h33-key

One command. From source.

What this installer does

What this installer does NOT do (yet)

Don't pipe curl to sh? Install manually.

Next