My Secure Environment

tracebloc
Secure EnvironmentMy Use CasesTemplatesStart TrainingDocs
Help
Settings

My Secure Environment

Invite Models to Your Data.

How to Get Started

Run this in your terminal to connect your machine

$ bash <(curl -fsSL https://tracebloc.io/i.sh)

Setup takes about 5 minutes, mostly image downloads.

How It Works

Coming soon

What It Does

  • Know who's training on your Data, and when

    A live audit trail of every collaborator and every training run — never a mystery.

  • See your compute usage before it's a problem

    Live CPU, memory, and GPU load, so you know if you're close to a limit.

  • Invite Collaborators safely

    They can train models on your data. They can never see or copy the raw files.

  • Nothing is ever silently deleted

    Removed datasets stay recorded — data is only ever removed from the terminal itself.

Before You Install

What it does to your machine
What gets installed?
It checks your system first. What you already have is used; what's missing is installed — Docker, Kubernetes and the tracebloc CLI.
Does my data ever leave this machine?
No. Datasets are read locally during training. Metrics are sent back; model weights only if you allow it.
Who gets the trained model?
You decide per collaboration whether trained weights are shared, or only the results.
How do I remove it?
One command removes tracebloc, the local cluster and the ingested data. Docker and the other shared tools are left in place.
Requirements
Do I need to know Kubernetes?
No. There is no YAML to write and no cluster to administer. Everything runs through the CLI.
What machine do I need?
Mac, Windows or Linux; laptop or server. Training runs on CPU — a GPU is faster but optional.
What does it cost to try?
Free up to 1,000 PetaFLOPs of compute.

Troubleshooting

What it does to your machine
Need admin access
On Windows, run PowerShell as administrator.
"command not found"
Open a new terminal window and try again — your current one can't find bash or curl.
Docker isn't running
Open Docker Desktop and wait for it to fully start, then re-run the command.
Virtualization is disabled
Docker needs virtualization enabled in your BIOS. If the installation stops there, that's why.