CLI

Install the Kracht CLI.

One command on macOS or Linux. Every download is checksummed before it runs, and the macOS build is signed and notarized by Apple.

renter · kracht

$ kracht launch --gpu 1 --region eu-west --ssh

Rented 8fa2c1d0 on H100 80GB (eu-west) at 2.890000 EUR/hr

Billing has started. Stop it with: kracht stop 8fa2c1d0

Waiting for it to finish provisioning...

root@kracht:~#

provider · install.sh

$ curl -fsSL cp.kracht.ai/install.sh | sudo bash \

-s -- --enrollment-token <token>

install the node agent

$ sudo systemctl status kracht-node-agent

Active: active (running)

Homebrew, on macOS

Three lines. The first one is not optional and is easy to miss.

brew trust kracht-ai/tap
brew tap Kracht-AI/tap
brew install --cask kracht

Homebrew refuses to load a cask from a tap it has not been told to trust, and reports that refusal as Invalid cask. The message names the cask, so it reads like a problem with our recipe. It is not. Run brew trust first and the tap installs normally.

Shell, on macOS or Linux

Works on macOS, and on Linux for x86_64 and arm64. The script checks the download against the published checksum and refuses to install if they differ.

curl -fsSL https://kracht.ai/install | sh

--version <tag>: Install a specific release instead of the current one.
--dir ~/.local/bin: Install somewhere else. The default is /usr/local/bin, which needs sudo on most machines.

Pass them after a double dash, like curl -fsSL https://kracht.ai/install | sh -s -- --dir ~/.local/bin.

Windows

There is no installer for Windows yet. The builds exist and you can download one directly: x86_64 and arm64 archives are published alongside every release.

Archives live at dl.kracht.ai/<tag>/kracht_<version>_windows_x86_64.zip, and dl.kracht.ai/latest returns the current tag. The archive contains a single binary. Put it somewhere on your PATH.

curl -fsSL https://dl.kracht.ai/latest
https://dl.kracht.ai/<tag>/kracht_<version>_windows_x86_64.zip
https://dl.kracht.ai/<tag>/kracht_<version>_windows_arm64.zip

What you can check.

Checksums, on every build

A checksums file is published next to the archives and both install paths verify against it before anything lands on your machine. The shell installer prints checksum ok when it matches and stops when it does not.

Signed and notarized on macOS

The macOS binary is signed with an Apple Developer ID and notarized by Apple, so Gatekeeper opens it without the warning an unsigned download gets. It is a universal binary, so one download covers Apple silicon and Intel.

What it does, and does not.

does: login, whoami: sign in with an API key and see who you are and your balance
does: launch, ls, stop: rent a card, list your rentals, stop paying
does: connect, ssh: the route in, and a shell once it is ready
does: checksums verified before anything lands; the macOS build notarized
does not: no Windows installer yet; the archives are downloadable above
does not: no Python SDK yet; the REST API under /v1 is the programmatic surface
does not: no reservations, because none exist: a launch is matched or refused

Every command.

kracht(1)kracht · commands

Name

kracht - rent a GPU by the second from the command line

Synopsis

kracht <command> [flags]

Commands

$ kracht login: Save your API key
$ kracht launch --gpu 1 --region eu-west --ssh: Rent a card and open a shell
$ kracht ls: What you are running
$ nvidia-smi: Check the GPU
$ kracht stop <instance>: Stop, and stop paying

Confirm it worked.

This prints the version you installed.

kracht version

If your shell cannot find it, the install directory is not on your PATH. The installer says so when it finishes, and names the directory it used.

Next: the documentation covers launching a GPU and connecting to it. Providers listing a machine want the provider setup instead, which installs a different program.