Skip to main content
You’ve built an environment with tools and scenarios. Deploy it to the platform and you can run evals at scale—hundreds of parallel runs across models, all traced, all generating training data.

​
hud deploy

The simplest path. One command builds and deploys your environment directly to HUD: 
hud deploy
This:
  1. Packages your build context (respects .dockerignore)
  2. Uploads to HUD’s build service
  3. Builds remotely via AWS CodeBuild
  4. Streams logs in real-time
  5. Links this directory to the deployed environment
Once complete, your environment appears on the platform:
Deployed environment on the platform
See your environment’s tools, scenarios, and builds at hud.ai/environments. For full details on managing environments through the platform UI, see Platform Environments.

​
Rebuilding

Run hud deploy again in the same directory. HUD reads .hud/deploy.json to find your existing environment and builds a new version: 
hud deploy  # v0.1.0
# make changes...
hud deploy  # v0.1.1

​
Configuration

Three flags for different purposes:
FlagWhenUse For
--env / -eRuntimeAPI keys, config
--build-argBuild timeRepo URLs, build modes
--secretBuild time (not stored in image)Private repo tokens
# Runtime env vars (encrypted, injected when container runs)
hud deploy -e API_KEY=secret

# Build args (for Dockerfile ARG directives)
hud deploy --build-arg REPO_URL=https://github.com/org/repo

# Build secrets (for private repos, not baked into image)
hud deploy --secret id=GITHUB_TOKEN,env=GITHUB_TOKEN
See hud deploy reference for full details.
Environment name is determined by (in order): --name flag, [tool.hud].name in pyproject.toml, or the directory name.
# pyproject.toml
[tool.hud]
name = "My Browser Environment"

​
GitHub Auto-Deploy

For teams and CI/CD, connect a GitHub repository. HUD rebuilds automatically when you push:
  1. Go to hud.ai → New → Environment
  2. Click Connect GitHub and install the HUD GitHub App
  3. Select your repository and branch
  4. Push changes—rebuilds happen automatically
Connecting a GitHub repository
This is better for long-term projects because:
  • CI/CD integration: Rebuilds on every push to your branch
  • Team collaboration: Anyone with repo access can trigger deploys
  • Version history: See which commit each build came from
  • Rollback: Deploy previous commits if needed

​
Switching Between Methods

Started with hud deploy but want GitHub integration later? Just connect the same repo on the platform. HUD links them by environment ID. Going the other way? Use hud link to connect a local directory to an existing platform environment: 
hud link --id existing-environment-id

​
Comparison

Featurehud deployGitHub Integration
SetupOne commandConnect repo on platform
RebuildsManual (hud deploy)Automatic on push
Best forSolo dev, quick iterationTeams, CI/CD
Env vars / Build args / SecretsCLI flagsPlatform settings
Both methods result in the same deployed environment. Choose based on your workflow.

​
What’s Next

Tasks & Training

Create tasks and train models

Platform Environments

Full platform environment guide