YAML Over SDK
Valohai is built on a simple principle: your ML code should not be entangled with your MLOps platform.
Many tools ask you to decorate functions, subclass Tracker objects, or wrap training loops in platform-specific APIs. We don't.
Why We Avoid SDK Integration
Valohai treats valohai.yaml as the single source of truth for your ML workflows. This architectural choice brings immediate benefits:
No vendor lock-in — Your ML code stays agnostic, portable, and unmodified
Zero hidden orchestration — What you see in YAML is what runs
No tight coupling — Platform configuration lives separately from business logic
Benefits of YAML-First Architecture
Portability Without Pain
Delete Valohai tomorrow and your code still runs. No refactoring, no API removal, no broken imports.
Git-Native Configuration
Your entire pipeline configuration lives in version control:
Track changes with standard Git workflows
Review pipelines in pull requests
Roll back configurations instantly
Team-Friendly Reviews
Platform engineers can audit pipelines without understanding your ML framework. Data scientists can focus on algorithms without learning orchestration APIs.
The Philosophy in Practice
When you run an execution, Valohai:
Reads your
valohai.yamlconfigurationProvisions the compute environment
Injects parameters command line arguments or through JSON/YAML files
Runs your code exactly as written
Your training script doesn't need to know it's running on Valohai. That's the point.
Last updated
Was this helpful?
