Skip to main content

Why CI/CD evaluation?

Every model, prompt, or agent change should prove it still meets your quality bar. Integrating evaluation into CI/CD lets you:
  • Validate every change against versioned rubrics and metrics
  • Catch regressions before they reach users
  • Keep an audit trail of scores tied to git commits
  • Block merge or deploy when quality gates fail
Akhara supports this with the hosted API and SDK: create evaluations with ci_mode, wait on automated scoring, check gates, and land results in app.akhara.ai.

Architecture overview

1. Suite config

evaluations/regression_gate.yaml

2. Evaluation script

scripts/run_evaluation.py

3. GitHub Actions

.github/workflows/model-evaluation.yml

4. GitLab CI

.gitlab-ci.yml
Bootstrap a domain rubric before locking the suite with adaptive rubric generation. See Open-source tooling.

Best practices

For high-stakes or regulated deployments, require completed human review (not only automated gates) before final production promotion.

After deploy

Next steps

Open-source tooling

Local suites, adaptive rubrics, dashboard source

Safety gating

Stricter gates for policy-sensitive agents