Dolt and Doltgres can run as replicas to MySQL, MariaDB, or Postgres databases, turning every transaction commit into a versioned Dolt commit. This 'database insurance' approach is gaining urgency as AI coding agents increasingly cause production incidents — from outright database deletions to subtle bad writes. Unlike traditional backups, a Dolt replica provides a full commit history, diffs, branches, and surgical rollback tools (dolt_revert, dolt_patch) that let you precisely identify and undo agent-caused damage without restoring an entire backup. The recommended layering is: backups for disaster recovery, standard replication for availability, Dolt replication for history and surgical undo, and a Dolt remote as a last-resort off-host backup.
