Your own Docker image
ML models, simulations, pipelines, or a custom program. Package one repeatable run and report the metric you want to improve.
Get started
Bring a Docker image, choose the settings to explore, and tell us what to improve. HyperOptimizer runs the search in the cloud.
01 Choose your workload
Keep your language and libraries. Pick the guide that matches your program.
How Docker integration works02 Check one local run
Before starting a search, run your container locally with one set of settings. It needs to do three things.
Read the full checklistEach configured flag changes the intended input in your program.
Include the dependencies and data it needs. No interactive prompts.
Report the actual result as hpo.metrics.<name>=<number>.
docker run --rm my-workload:latest \
--hpo-learning-rate=0.01hpo.metrics.validation_loss=0.14Example values only. Use your own image and measured result; the metric name must match your experiment objective.
03 Launch your search
Work from your terminal or use the dashboard. Both run on HyperOptimizer’s cloud and keep your settings, metrics, and logs together.
Install the HPO CLI and open your workload repository. You’ll need an account, a project, and Docker with Buildx for local builds.
Log in, then initialize a configuration for your project.
Set your image build, parameter ranges, objective, and run limits.
With build settings, the CLI builds and publishes your image, then starts the cloud experiment.
Currently installed from source; requires a compatible API and dashboard. The installation guide covers availability and setup.
hpo login
hpo init
# Edit hpo.toml for your workload
hpo fmt
hpo validate
hpo optimizeBuild settings · Parameters · Objectives · Run limits
Explore the configurationThe build is local. The experiment runs in our cloud.
Create a project, then choose a published image. Set up your experiment in the dashboard or import an existing hpo.toml.
Make it available in your workspace registry before you launch.
Choose parameter ranges and which metrics to maximize or minimize.
Check your machine size, run limits, and available compute.
Review your configuration, then launch.
Import settings, or export them to keep with your code. Local build instructions remain metadata; dashboard launches need a published image.
Import and export guide