The Persistent State Layer Ansible Has Been Missing
Ansible's stateless architecture means critical infrastructure data exists only during playbook execution.
Impact: 1,200+ hours/year wasted per mid-size team re-gathering identical information
Audit teams require proof of patch levels, configuration baselines, and change history. Ansible provides none of this out-of-the-box.
Impact: $750K+ average audit costs; failed compliance leading to contract losses
Every playbook re-executes fact gathering. Multiple teams gather duplicate data. No central source of truth exists.
Impact: 30-40% of automation runtime wasted; increased infrastructure load
PuppetDB requires Puppet infrastructure. Osquery is security-focused. Chef Automate requires ecosystem lock-in.
Impact: High development costs for custom solutions with no standardization
Callback plugins and gather playbooks seamlessly capture facts during normal Ansible operations—zero workflow changes required.
Intelligent schema normalizes diverse fact formats into queryable structures with hybrid relational + JSONB storage.
Time-series tracking of every configuration change with point-in-time restoration and drift detection capabilities.
SQL-based queries across entire fleet: "Show all RHEL7 hosts with OpenSSL < 3.0.14" in seconds, not hours.
Modern FastAPI interface for programmatic access, integrations, and custom tooling development.
Pre-built Grafana dashboards for fleet visibility, compliance monitoring, and executive reporting.
Built with Python (FastAPI) and PostgreSQL/TimescaleDB - runs anywhere modern Linux and containers are available
Small fleet (< 500 nodes):
Scales up with PostgreSQL/TimescaleDB for larger fleets
If you can run a recent RHEL, Ubuntu, Debian, or SUSE server, or deploy a Docker container, you can run AnsibleDB2.
# Add repository and install
curl -fsSL https://repo.ansibledb2.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/ansibledb2.gpg
echo "deb [signed-by=/usr/share/keyrings/ansibledb2.gpg] https://repo.ansibledb2.com/ubuntu $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/ansibledb2.list
sudo apt update && sudo apt install ansibledb-server
# Configure and start
sudo ansibledb-server setup
sudo systemctl enable --now ansibledb-server# Download and start
curl -O https://raw.githubusercontent.com/ansibledb2/ansibledb/main/docker-compose.yml
docker-compose up -d
# Verify installation
docker-compose ps
curl http://localhost:8080/healthProblem today: Security teams must run ad-hoc Ansible plays (or worse, log into servers manually) to prove patch levels. This burns hours during audits.
With AnsibleDB2: One query instantly shows which hosts run a vulnerable package (e.g. OpenSSL < 3.0.14). Historical snapshots provide "point-in-time" evidence for auditors without touching production systems.
Impact: Saves days during audits, reduces consultant costs, lowers compliance risk fines.
Problem today: Ops teams waste cycles maintaining static inventories or gathering fresh facts before patching.
With AnsibleDB2: Dynamic inventory lets Ops instantly select "all OEL8 systems in prod with agent < 3.4.5." No need for fleet-wide fact gathering before every patch cycle.
Impact: Cuts patch prep time by 50%+, reduces downtime windows, fewer missed targets.
Problem today: When a service fails, SREs scramble to see "what changed" across hosts. This means manual diffs, log digging, or new playbook runs.
With AnsibleDB2: Historical snapshots allow quick diffs ("nginx was running last week, now stopped on these 5 nodes"). Alerts on drift (e.g. agent disabled unexpectedly).
Impact: Hours saved in incident response, faster MTTR (mean time to recovery), less downtime cost.
Problem today: Developers depend on Ops for questions like "which servers are running our app with agent v2.0?" causing delays.
With AnsibleDB2: Developers query the API/UI directly or use inventory plugins in their playbooks. Can roll out app agents to only "hosts with Python ≥ 3.9 and OS = Ubuntu 22.04."
Impact: Faster deployments, reduced dependency on Ops, accelerates feature delivery.
Problem today: Leadership lacks visibility into how many systems are EOL (e.g. RHEL7), leading to surprise migration costs and risks.
With AnsibleDB2: Dashboards show OS lifecycle status and highlight unsupported hosts. Data supports budgeting for refresh cycles and cloud migration planning.
Impact: Avoids compliance fines, prevents over-spending on extended vendor support, enables proactive migration budgeting.
Problem today: Large companies often have mixed fleets (AWS, Azure, GCP, on-prem). Tags, regions, and metadata are inconsistent, making it hard to track workloads. Finance teams struggle to map spend to actual business units.
With AnsibleDB2: Collects and normalizes cloud metadata (instance IDs, regions, tags, account IDs) alongside OS and agent data. Query across clouds: "Show all Ubuntu hosts in AWS us-east-1 with agent < v2.0" or "List all Azure VMs missing backup agent."
Impact: Improved cost allocation and chargeback accuracy. Unified compliance checks across hybrid infrastructure. Fewer surprises in cloud spend and faster migration readiness.
Hover over each platform to see detailed version support and capabilities
Enterprise & Open Source
Server & Desktop
Major Vendors
AWS, Azure, GCP
Modern Workloads
Future Roadmap
95% platform coverage across enterprise environments
Join thousands of teams using AnsibleDB2 for persistent state management