Provisioning tools
Terraform, Pulumi and cloud APIs create the desired infrastructure state.
Infrastructure Automation
Automation that knows whether
the fix actually worked.
Scripts execute commands. SentienGuard closes the operational loop around them: detect the incident, select the controlled playbook, execute it, verify recovery, roll back or escalate, and preserve the evidence.
Keep your automation tools. Add operational judgment.
Execution tools
Ansible, Rundeck and scripts perform known changes.
SentienGuard
Chooses when remediation is appropriate, gates authority, verifies the result and records proof.
Production authority is earned
- 01
Observe
Read telemetry and propose actions. No production changes.
- 02
Approve
An engineer sees the diagnosis, commands and blast radius before authorizing execution.
- 03
Automate
Promote only proven playbooks. Keep verification, rollback and escalation active.
Infrastructure automation FAQ
Does SentienGuard replace Terraform or Ansible?
No. Terraform and Ansible define and execute infrastructure changes. SentienGuard adds incident detection, diagnosis, playbook selection, verification, rollback and evidence around operational remediation. It can invoke the tools you already trust.
Can infrastructure automation start read-only?
Yes. Observation mode diagnoses incidents and records the action it would propose without changing production. Approval mode adds human-authorized execution. Only proven incident classes need to become autonomous.
What happens when a fix fails?
SentienGuard checks the original failure condition after execution. Failed verification triggers rollback when the playbook supports it, then escalation with the commands, output and before-and-after state attached.
Related: runbook automation · automated remediation · IT operations automation