Training and release gates
Train from a config file. Each run is checked against release thresholds, gaps between groups, and the model already in production. Deploy as a batch job or behind an endpoint.
A release path for machine learning models, with approval gates and drift alerts built in.
Download the PDFA short PDF to share with your team. It covers what is in the package, how it works, and a worked example.
Your download has started.
We also emailed the link to . It works for 7 days.
Download didn't start? Get the PDF
Want to try it on your own data? Talk to us.
A model tests well. Then nobody can say which version is live, whether the input data has shifted, or how to roll back. Retraining happens when someone remembers.
Train from a config file. Each run is checked against release thresholds, gaps between groups, and the model already in production. Deploy as a batch job or behind an endpoint.
Versions move from candidate to production with an approver who neither trained nor registered the model. One command restores the last archived version. The registry can be swapped for MLflow or Azure ML.
Windowed features defined once, relative to an as-of time, so training sets are point-in-time correct. A check catches data leakage.
Population stability index against the training profile, plus missing values, new categories, freshness, accuracy, and cost. Every run writes an Evaluation Card for the AI inventory.
Fit the pipeline and write a run folder with the model, metrics by group, a data profile, the config, and the code version.
Every threshold met, gaps between groups inside their limits, and no meaningful drop compared with the production model.
The run becomes the next candidate version, with its gate result attached.
Production needs a passing gate and an approver who is neither the trainer nor the registrant.
One command brings back the last archived version. Every change is logged.
Scheduled checks compare live data with training data and alert when a limit is crossed.
A churn model is trained, gated, and promoted by a separate approver. Then the data shifts under it.
Monitoring flags all three shifts and exits with an alert, so a scheduled job can open a ticket or start retraining.
Ask about the MLOps Templates
Dex answers from our own pages and links to where it found the answer.
Show us how it runs today. We will map the route to production, rollback included.