Skip to main content
A running secure environment in about 10 minutes, with one command. Deploying on a specific environment instead (EKS, AKS, bare-metal, OpenShift)? See Deployment environments.
No Docker or Kubernetes knowledge needed. The installer sets up the whole container stack for you — on macOS and Linux it even installs Docker if it’s missing. You just need a machine.

​
Before you start

The minimum is enough to keep your secure environment online. Training needs more: even the smallest experiment (4 GiB) only fits beside the platform’s own services in an 11 GB Docker budget. On macOS and Windows, Docker runs in a VM with its own memory limit, which is often 8 GB by default. On macOS, raise it in Docker Desktop → Settings → Resources → Memory. On Windows (WSL 2), set memory= under [wsl2] in %UserProfile%\.wslconfig, then run wsl --shutdown. The installer checks before it starts: below the minimum it stops on Linux, and on macOS and Windows it warns and tells you how much memory to give Docker.
1

Run the installer

What to expect: about 5 minutes. It checks your machine, installs Docker (if missing), the tracebloc CLI and a local Kubernetes cluster, then registers this machine with your account. Safe to re-run anytime.
Every install script is open source. Download, inspect, then run:
Source: github.com/tracebloc/client. Release binaries are cosign-signed, so you can verify their signature before trusting them.
2

Sign in and name this machine

Partway through, the installer prints a link and a short code. Open the link on any device (this computer or your phone), sign in the way you already do — password, Google, or GitHub — and approve the code. The code is valid for 10 minutes; if it lapses, the installer offers a fresh one.Then it asks you to name your secure environment — the name shown on your dashboard. To skip the prompt, set TRACEBLOC_CLIENT_NAME before the install command.The installer registers this machine on your account itself. You don’t need to create anything on the clients page first.
3

Verify it's connected

Open a new terminal (so the tracebloc command is on your PATH), then run:
tracebloc client status --wait waits until it’s online. Your secure environment also shows Online on your clients page.
What changed on your machine — Docker (if it was missing), a local cluster named tracebloc, kubectl, k3d and helm, the tracebloc CLI (plus a PATH line in your shell profile, if needed), and ~/.tracebloc. The installer also switches kubectl’s current context to k3d-tracebloc; if you work with other clusters, switch back with kubectl config use-context <your-context>.To remove tracebloc from this machine, run tracebloc delete — see Uninstall.

​
Locked-down environment?

If your security policy forbids piping scripts from the internet, skip the one-liner and deploy with Helm instead — same result, full control over every step.

​
What’s next

Stage a dataset

Ingest data so contributors can build models against it.

Create a use case

Define a task and invite contributors.