Hallo world, I built Pabawi for people and teams running "classic" infrastructure: bare metal and VMs who use Puppet, Bolt, Ansible, SSH, PuppetDB, Hiera, Proxmox, AWS EC2 or AzureVMs. Not everything is Kubernetes, and not every useful operations workflow wants to become a pile of YAML and dashboards. Pabawi gives those environments a single web UI for the daily work: - browse inventory from multiple sources - inspect facts, PuppetDB reports, catalogs, and Hiera data - run whitelisted commands, Bolt tasks, package actions, and Puppet runs - manage VM lifecycle across Proxmox, AWS, and Azure - keep execution history, audit data, RBAC, and node journals in one place - expose read-only infrastructure context to AI agents through an embedded MCP server The goal is simple: make classic infrastructure visible, operable, and scriptable without hiding the underlying tools from people who actually know how they work. I’d love feedback from sysadmins, Puppet users, DevOps teams, homelab people, and anyone managing mixed infrastructure. What workflow would you expect this to cover first: safer command execution, Puppet visibility, provisioning, or AI-assisted infrastructure lookup?

Pabawi

Web UI for Puppet, Ansible, SSH and VMs

Web UI for Puppet, Ansible, SSH and VMs