Portable Ansible upstream
dbbot ships a built-in portable-ansible runtime built through make_ansible_portable. Use it when you want the upstream packaging path or want to reuse the portable build outside dbbot.
MYSQL OPS, PRODUCTIZED
dbbot focuses on the MySQL ecosystem and brings deployment, replication, backup, restore, monitoring, and downstream analytics access into one execution surface. Today the priority is to solidify deterministic workflows; next comes the evolution toward skills and AI agents.
git clone https://github.com/fanderchan/dbbot

Ecosystem Notes
dbbot ships a built-in portable-ansible runtime built through make_ansible_portable. Use it when you want the upstream packaging path or want to reuse the portable build outside dbbot.
If you do not want to use Linux, or you want MySQL on a Windows dev machine without Docker, this portable option is the alternative. Compared with the default Oracle ZIP workflow, it supports mixed multi-instance deployment on the same host.
mysqlrouter_exporter is now a standalone project for MySQL Router metrics. It keeps the same config and service shape used by dbbot, while adding an independent release path and direct host-side deployment option.
What ships now
dbbot first narrows the parts of the MySQL ecosystem that most easily drift out of control, aligning variables, procedures, artifacts, and validation.
Covers common delivery paths such as standalone, primary-replica, MHA, and MGR, reducing drift caused by environment differences and manual work.
It is not only about being able to back up. It is also about restoring successfully and validating the outcome, turning critical steps into deterministic workflows.
Builds a consistent integration surface around Prometheus, Grafana, Alertmanager, and exporters, reducing repeated assembly work.
Brings MySQL downstream analytics into the same toolchain, covering cluster deployment, backup and restore, and common operations.
Roadmap
Solidify deterministic workflows such as deployment, replication, clustering, backup, restore, and monitoring so scripts, variables, documentation, and validation all stay aligned.
Break high-frequency actions into composable skills, such as deploying instances, wiring exporters, validating restores, and checking backups.
Add a natural-language entry point on top of those skills so an AI agent can understand intent, generate a plan, confirm with humans, and then call dbbot to execute.
Official homepage
dbbot is not about piling on more scripts. It is about giving database operations a steadier, more composable execution plane that fits automation and human collaboration.