Is Your CI/CD Pipeline Actually Working?
Satya Singeetham (CTO @ New Horizon Bank) is a world-leading expert on CI/CD Pipelines. In this episode of 1 IDEA, he explains how to build a world-class CI/CD setup in 2026.
Sedai now optimizes AI agents!
Read the newsSedai writes every optimization back to Git automatically, so your infrastructure code stays in sync with your live environment.
Git-as-source-of-truth works well when humans are the only ones making changes. Autonomous systems change that.
Adjustments made directly to a running cluster exist outside your declared state — and get reverted on the next reconciliation.
Translating live changes back into IaC by hand is slow, error-prone, and rarely happens consistently.
Guardrails configured outside code have no version history, no peer review, and no audit trail.
Sedai integrates directly with your IaC and GitOps workflows, so every change it makes is reviewable, auditable, and permanent.
Drift Prevention
After every optimization, Sedai opens a pull request with the exact code changes needed — Terraform variables, Helm values, Kustomize patches. Your declared state stays current automatically.
Deployment Resilience
Sedai's CI/CD overwrite protection detects when a new deployment would revert an optimization and re-applies the correct configuration. Your gains don't disappear at the next push.
Policy in Version Control
Define the guardrails for autonomous optimization in Git. Sedai reads and enforces those boundaries from your repository — reviewed, versioned, and managed like any other policy file.
No Manual Translation
Sedai generates the exact code changes required. Engineers review a PR, not a recommendation. Sedai has already written the optimization; it just needs an approval.
Sedai lets you define CPU, memory, replica, & cost boundaries directly in Git as policy files, with no portal configuration required.
Guardrails are versioned alongside your application code, and they're subject to the same review & approval process.

After Sedai applies a change to your live environment, it automatically opens a PR with the corresponding IaC changes. This can take the form of Terraform .tfvars, Helm values.yaml, or Kustomize patches.
The PRs include a summary of what changed, the "why" behind it, and the projected impacted, reviewable by any engineer without Sedai access.

Sedai monitors for deployment events that would overwrite a previous optimization. When Sedai detects a conflict, it re-applies the correct configuration after the deployment completes — without manual intervention.
For GitOps environments running ArgoCD or Flux, the Live Sync Controller intercepts reconciliation conflicts, before they cause drift.

Sedai's IaC Mapping Agent automatically traces live cluster resources back to their originating IaC source: Terraform module, Helm release, or Kustomize overlap
Sedai maintains mapping continuously as your stack evolves, without manual annotation or tagging.

“What I found with Sedai is that it's very focused on safety. I don't really have to worry about it. It just delivers the optimization, in a very gradual and safe way.”
.webp%3Fv%3D2026-04-14T17%253A50%253A49.084Z&w=3840&q=75&dpl=dpl_5LX6WMhzwBYCXLQ3mMth1wewbAPE)
Robert Berger
Chief Architect // Informed
Terraform
Helm
Kustomize
GitHub
GitLab
Bitbucket
ArgoCD
Flux
Without Sedai